Enable private peering for VMs and cloud services within the Azure virtual network.
IPv4 subnets:
Peering subnet for path 1 (/30)
Peering subnet for path 2 (/30)
IPv6 subnets (optional):
Peering subnet for path 1 (/126)
Peering subnet for path 2 (/126)
VLAN ID for peering
ASN for peering
ExpressRoute ASN = 12076
MD5 Hash (Optional)
Microsoft peering
Enable this peering for Microsoft online services and Azure PaaS services. Ensure separate proxy/edge for ExpressRoute and Internet to avoid asymmetric routing.
IPv4 subnets:
Peering subnet for path 1 (/30) - public IP
Peering subnet for path 2 (/30) - public IP
IPv6 subnets (optional):
Peering subnet for path 1 (/126) - public IP
Peering subnet for path 2 (/126) - public IP
VLAN ID for peering
ASN for peering
Advertised prefixes - public IP prefixes
Customer ASN (optional if different from peering ASN)
Connect to Azure and Microsoft cloud services through Microsoft peering.
ExpressRoute partner circuit provisioning states
ExpressRoute partner circuits have two states:
ServiceProviderProvisioningState: State on the provider's side (NotProvisioned, Provisioning, Provisioned). Must be Provisioned to configure peering.
Status: Microsoft's provisioning state, set to Enabled when the circuit is created.
Possible states of an ExpressRoute circuit
At creation time
Output
ServiceProviderProvisioningState : NotProvisioned
Status : Enabled
During provisioning
Output
ServiceProviderProvisioningState : Provisioning
Status : Enabled
After provisioning
Output
ServiceProviderProvisioningState : Provisioned
Status : Enabled
During deprovisioning
Output
ServiceProviderProvisioningState : NotProvisioned
Status : Enabled
Important
A circuit can't be deleted when the ServiceProviderProvisioningState is Provisioning or Provisioned. The provider must deprovision the circuit first. Microsoft continues billing until the circuit is deleted in Azure.
Routing session configuration state
The BGP provisioning state must be enabled for private or Microsoft peering. Check the BGP session state, especially for Microsoft peering. The advertised public prefixes state must be configured for routing to work.
If the advertised public prefixes state is validation needed, the BGP session isn't enabled.
Important
If the advertised public prefixes state is manual validation, open a support ticket with Microsoft support and provide evidence of IP address ownership and associated ASN.