This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 72%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
A company wants to establish network topologies that combine cross premises connectivity with inter virtual network connectivity. Which Azure feature allows them to do this?
Azure Virtual Network Gateway
VNet peering
Correct. VNet peering allows the establishment of network topologies that combine cross premises connectivity with inter virtual network connectivity without using a virtual network gateway.
Azure Resource Manager
I expected the answer to be Azure virtual Network gateway, not vnet peering
This question is related to the following Learning Module
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 70%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hi Adeola Awowale,
Welcome to the Microsoft Q&A forum.
Thank you for bringing this issue to our attention. We will update you as soon as possible.
Hi Adeola Awowale,
This statement is incorrect indeed.
VNet Peering does not support cross-premises connectivity on its own. It is designed for inter-VNet connectivity within Azure and allows Azure resources in one VNet to communicate with resources in another VNet. The right answer should be Virtual Network Gateway .
Hi
Welcome to the Microsoft Q&A forum.
Thanks for bringing this to our attention. We'll keep you updated as soon as possible.
Hi
Thank you for reaching out to us on the Microsoft Q&A forum.
We understand your concern, let's break down the issue.
Azure Virtual Network Gateway is used for connecting Azure to an on-premises network / external locations (E.g: via VPN / ExpressRoute). It doesn’t handle connections between virtual networks within Azure.
VNet Peering, on the other hand, is designed specifically to connect virtual networks to each other inside Azure, even across regions. This makes it the right answer for combining cross-premises and inter-virtual network connectivity.
For example, think of it this way:
Virtual Network Gateway = Connect Azure to the outside world.
VNet Peering = Connect networks within Azure.
That’s why VNet Peering is the correct answer.
Referral link: https://zcusa.951200.xyz/en-us/azure/vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal
Should you find this information helpful, kindly express your acknowledgment by clicking the "Upvote" and "Accept Answer" buttons on the post.
Thank you.
The link provided shows a connection established through VPN Gateways.
Quote from paragraph 1: "This article doesn't apply to virtual network peering. For virtual network peering, see the Virtual Network peering article."
Accross the AZ-500 practice exam questions it is stated repeatedly that virtual network peering can only be established within Azure between networks that are in the same region. When in different regions a VPN connection is required.
However https://zcusa.951200.xyz/en-us/azure/virtual-network/virtual-network-manage-peering?tabs=peering-portal#requirements-and-constraints suggests:
"You can peer virtual networks in the same region, or different regions."
The question contains "cross premises connectivity" - but your answer contains: "VNet Peering = Connect networks within Azure. That’s why VNet Peering is the correct answer."
None of this makes sense.
Hi
welcome to the Microsoft Q&A forum.
Let's break this down step by step to ensure everything is clear, especially regarding the role of VNet Peering vs Virtual Network Gateway to avoid any confusion:
->VNet Peering allows connectivity between virtual networks both within the same region and across different regions. It enables inter-virtual network connectivity and when one of the VNets is connected to on-premises via a VPN gateway can provide cross-premises connectivity.
->Virtual Network Gateway is used primarily for connecting Azure to external networks (Eg: on-premises) and establishing site-to-site connections between VNets / between a VNet and an on-premises network.
In the case described in the question, VNet Peering is the correct answer because it allows connecting networks within Azure and can also route traffic through a VPN gateway for cross-premises connectivity.
Thank you.
Thank you SiddeshTN.
So, is VNet peering something else than virtual network peering?
From: https://zcusa.951200.xyz/en-us/azure/virtual-network/virtual-network-peering-overview
Azure supports the following types of peering:
I also recall a practice exam question (cannot find it back) with two subnets, one in East US and one in East US 3 - how to access resources in the other subnet. I chose virtual network peering, which was not the correct answer because of the different regions.
Before taking the AZ-500 exam - I really would like to understand all this conflicting information.
Hi
Thank you for following up in detail.
Let’s break down the concepts of VNet Peering, Global VNet Peering, and how they differ from other connectivity options like VPN Gateways to clear up any remaining confusion.
-> VNet Peering is used to connect virtual networks in the same region. This is also called Virtual Network Peering in the documentation. If you're connecting VNets within the same region, VNet Peering is the correct choice.
-> Global VNet Peering is used for connecting virtual networks across different regions. This is necessary if your VNets are in different regions, as in the case of East US and East US 3.
When to use a VPN Gateway:
-> If you're trying to connect to an on-premises network or you need a Site-to-Site VPN between VNets (either in the same / different regions) then you would need a VPN Gateway.
-> If you're using VNet Peering or Global VNet Peering, you are not using a VPN Gateway unless you're also connecting one of the VNets to an on-premises network.
Summary:
-> Virtual Network Peering (within the same region) and Global Virtual Network Peering (across different regions) are two types of peering in Azure.
-> For cross-premises connectivity you can use VNet Peering if one of the VNets is connected to an on-premises network via a VPN Gateway.
-> For VNets in different regions, you must use Global VNet Peering.
Thank you.
Hi @SiddeshTN
The issue is not a lack of understanding about what a VNet Gateway or VNet Peering is. The problem lies in the fact that each answer only addresses part of the solution, and only one answer is allowed.
That being said IMO it makes more sense that when the question mentions topology and cross-premises connectivity, the VNet Gateway should be assumed, along with the presence of a peered VNet (e.g., Hub and Spoke or vWAN), rather than the opposite.
I don’t understand why cross-premises connectivity would be considered a given while inter-VNet connectivity is not. Inter-VNet connectivity is a foundational requirement and is easier to set up.
At the end of the day, I think the best approach is to either rephrase the question or allow more than one answer.