The Connection name is auto-generated using both gateway names, but you can change it if you like. Select the Virtual network gateway and the Local network gateway we created. Set the Connection type to Site-to-site (IPsec). In the resource group, click Add one more time. This will define the actual connection between your on-premises Gateway and the Azure Gateway. When the Gateway is provisioned there’s only one thing left to do on the Azure side of the connection, and that is to create a Connection. The creation of the Virtual network gateway can take up to 45 minutes. Go clean the house, go outside, go read some more of my blog posts, anything. Select the virtual network and the public IP Address we created earlier. I choose Basic because this is just a lab environment. Provide a name for the gateway, select a SKU. Search for the Virtual network gateway and click it. Click Create.įinally we can add the Virtual network gateway itself.īack to the resource group we created earlier, and click add again. Should the Dynamic IP change, you’ll have to reconfigure the local gateway as well though. A Static IP is more expensive but I recommend you use a static IP if you’re configuring a production environment. Provide a name for the IP address, define if this is a Dynamic or Static IP. Search for the Public IP Address and click it. In the resource group we created earlier, click add. Next up is the public IP Address that will be used by the gateway. Name the local gateway, enter the external IP address on which you will configure the local gateway, define the local IP Address range(s) to which we will connect. This will define the on-premises gateway to which we will connect. Search for Local Network Gateway, and click it. Return to the resource group and click Add again. I’m doing this because I want to be able to add VMs in this site to my on-premises Active Directory. Click Save to save the custom DNS setting. Define the custom DNS server as the on-premises DNS server. Scroll down to DNS servers and click DNS servers. Click OK to add this subnet after you have entered the subnet you want to use. I prefer to define the Gateway subnet as the very last subnet available in the virtual network’s address space. You can click the Go to resource button to directly go to the new virtual network resource. When the resource is created a useful popup. Name the virtual network, define an address range for the virtual network, name the first subnet, and define an address range for that subnet. Search for Virtual Network and select it.Ĭhoose to create it using the Resource Manager deployment model. Open the new resource group and click Add. Name the group, choose a subscription and location, and click Create.Īll other resources for this purpose will be created in this resource group, this subscription, and this location. Purpose: Extend on-premises network to Azure.Īdd a resource group by clicking Resource groups, and then clicking Add. This guide will basically result in the same setup, but is provided using the Azure Portal, and PowerShell. Quite a mouthfull, but that’s because I posted a guide for Site-to-site VPN ( Building an Azure lab – Implementing S2S (Site-to-Site) VPN) earlier as well, but that guide is based on the classic portal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |