For configuring the VNet peering, perform the following steps:
- After the VNets in both subscriptions are prepared, navigate to one of the Virtual network and in the SETTINGS you need to click on Peerings:
- In the Peerings blade, click on +Add:
- In the upcoming blade, you have the opportunity to create a new peering subnet in the existing Subscription and Resource group. In our current scenario, we need to select I know my resource ID to connect a VNet in another subscription:
- Now you need the resource ID. You need to fill in the ID in the context field after the checkbox:
- Now you can do some more settings if you need them for your scenario:
-
- Allow virtual network access: Allows the address space of the peer VNet to be included as part of the Virtual_network. In general the peered networks are linked to each other and become one big network.
- Allow forwarded traffic: Allows traffic not originated from the peered VNet to be accepted or dropped.
- Allow gateway transit: Allows the peer VNet to use your VNet gateway.
- Use remote Gateways: Uses your peer's VNet gateway. The peer VNet must have a gateway configured and a AllowGatewayTransit selected. You cannot use this option if you have a gateway configured.
- After clicking OK, it will take a few minutes until the connection is established. After you have deployed the peering in the first subscription, you should see the status of the connection in the peering blade as Initiated:
- To set the PEERING STATUS of both networks as Connected, you need to repeat the steps mentioned previously in the other subscription too. Afterwards, you change the status in both subscriptions to Connected like shown in the following diagram for DCF-AWE-PR02:
- The same should happen for DCF-AWE-PR01:
Currently VNet peering is still in preview and under development. Microsoft will extend this service in the near future to support VNet peering with Microsoft Azure public services such as Storage or Azure SQL too.