Microsoft peering

@C.J. Vieleers Thank you for reaching out to Microsoft Support. Answering your question below:

If your ExpressRoute circuit is enabled for Azure Microsoft peering, you can access the public IP address ranges used in Azure over the circuit. Azure Microsoft peering will provide access to services currently hosted on Azure (with geo-restrictions depending on your circuit's SKU). To validate availability for a specific service, you can check the documentation for that service to see if there is a reserved range published for that service. Then, look up the IP ranges of the target service and compare with the ranges listed in the Azure IP Ranges and Service Tags – Public Cloud XML file. Alternatively, you can open a support ticket for the service in question for clarification.

Supported:

Microsoft 365
Power BI - Available via an Azure Regional Community, see here for how to find out the region of your Power BI tenant.
Azure Active Directory
Azure DevOps (Azure Global Services community)
Azure Public IP addresses for IaaS (Virtual Machines, Virtual Network Gateways, Load Balancers, etc.)

Not supported:

CDN
Azure Front Door
Multi-factor Authentication Server (legacy)
Traffic Manager
Logic Apps

As seen above, the list of supported and unsupported services are listed out. Most of the other Azure services are also supported. Check directly with the service that you want to use to verify support. You can also check the Public IP address range for any other 3rd party services hosted on Azure to confirm if that address range is supported to be accessible via MS Peering. Hope this helps.

Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

Remember:

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

Want a reminder to come back and check responses? Here is how to subscribe to a notification.