- May 16, 2022
- April 28, 2022
- March 24, 2022
- February 8, 2022
- December 20, 2021
- December 1, 2021
- November 22, 2021
- November 4, 2021
- October 26, 2021
- September 30, 2021
- September 22, 2021
- September 2, 2021
- August 16, 2021
- August 2, 2021
- July 19, 2021
- July 1, 2021
- June 17, 2021
- June 1, 2021
- April 30, 2021
- April 8, 2021
- March 25, 2021
- March 15, 2021
- February 25, 2021
- February 8, 2021
- January 28, 2021
- January 21, 2021
- January 13, 2021
- 2020 Releases
- Getting Started
- Cross Connects
- Virtual Circuits
- Cloud Connectivity Overview
- Hosted vs. Dedicated Connections
- Amazon Web Services
- Google Cloud Platform
- Microsoft Azure
- IBM Cloud
- Oracle Cloud Infrastructure
- Cloud Router Overview
- Requirements and Feature Support
- Site-to-Site VPN for Cloud Router
- Create and Manage Cloud Routers
- Add Connections
- Manage Connections
- BGP Sessions
- Resources and FAQ
- Marketplace & IX
- Troubleshooting & FAQ
- Technical Reference
- Reseller Admin Portal
Hosted Microsoft ExpressRoute Process Overview
1. Complete the prerequisites.
The Azure VNet allows Azure resources and services to communicate with each other.
The requirements cover redundancy, routing, NAT, QoS, and network security. Do not create the ExpressRoute yet.
Provisioning a port only takes a few minutes. You can then generate an LOA and handle the cross connection installation yourself, or you can have us manage it. For more information, see Cross Connects.
At this point, your network might look roughly like this:
Note that you are not required to have a Microsoft 365 environment.
When you create the circuit, you select the on-ramp location and capacity. You are also provided a service key.
Microsoft begins billing as soon as the service key is created, which is why we advise that you wait until your cross connect is established first.
Using the service key generated with your ExpressRoute circuit, create a Hosted Cloud Connection from the PacketFabric portal.
This is also where you establish the VLAN IDs you will use for peering with Azure and Microsoft 365.
5. (Optional) Repeat step 4 for the secondary circuit connection.
Each service key includes a primary circuit and a redundant secondary circuit connection.
To provision the secondary circuit, simply create another hosted connection. Use the same service key and the same VLAN IDs you specified for the primary circuit.
The secondary circuit will need to land at the same on-ramp location, but it should originate from a different source port.
For more information, see see High Availability and Redundancy in ExpressRoute Connections.
Use the Private peering VLAN ID you specified in your PacketFabric connection to set up peering with your Azure virtual network.
If you are using Microsoft 365/Office 365, you can use the Microsoft peering VLAN ID to peer with the Microsoft 365 cloud.
Azure VNets have two types of gateways: VPN and ExpressRoute. You will need an ExpressRoute gateway to link your circuit to your virtual network.
Add a connection to your circuit.
If you are peering with Microsoft 365, you will need to configure routing to establish a BGP session.