AZ-700 Question 129
Single answerYour company plans to use a single ExpressRoute circuit to connect from its on-premises data center to Azure Virtual Machines running internal workloads and also to Microsoft 365 services. Which ExpressRoute peering configuration is required to meet both needs?
- A
Azure private peering only
- B
Microsoft peering only
- C
Both Azure private peering and Microsoft peering
- D
ExpressRoute Global Reach
Show answer and explanation
Correct answer: C
Explanation
To access Azure IaaS resources via private IP addresses and Microsoft 365 services on the same ExpressRoute circuit, you must configure both Azure private peering and Microsoft peering. Azure private peering provides connectivity to Azure Virtual Networks, while Microsoft peering provides connectivity to Microsoft SaaS services such as Microsoft 365. Reference: Microsoft Learn documentation on �ExpressRoute circuits and peering�.
- A. Incorrect.
Option 1: Azure private peering only. Incorrect. While Azure private peering enables private connectivity to Azure Virtual Networks (e.g., Virtual Machines), it does not support public endpoint services like Microsoft 365. Microsoft 365 access requires Microsoft peering.
- B. Incorrect.
Option 2: Microsoft peering only. Incorrect. Microsoft peering enables public endpoint access for services like Microsoft 365 but does not support private IP communication to Azure Virtual Networks, which is needed for internal workloads.
- C. Correct.
Option 3: Both Azure private peering and Microsoft peering. Correct. You use Azure private peering to connect to Azure VMs and other private services within your Virtual Networks. You also use Microsoft peering to access Microsoft 365 services over the same ExpressRoute circuit.
- D. Incorrect.
Option 4: ExpressRoute Global Reach. Incorrect. ExpressRoute Global Reach is used to link on-premises networks through Microsoft� network, but it does not replace the need for separate peering configurations to connect to VMs and Microsoft 365.