Create an Azure ExpressRoute Direct Connection
Your Azure subscription must be enrolled. See Onboard to ExpressRoute Direct.
Create an ExpressRoute Direct
The dedicated version of an Azure ExpressRoute is called ExpressRoute Direct. You create and manage these separately from other ExpressRoute circuits. For more information, see Microsoft - About ExpressRoute Direct.
For information on creating the ExpressRoute Direct, follow the instructions provided here: Microsoft - Create ExpressRoute Direct using the Azure portal.
When creating the ExpressRoute Direct, ensure you select a location in which PacketFabric is present:
Market - Site
Amsterdam - Equinix AM5
Chicago- CoreSite CH1
Chicago - Equinix CH1
Dallas - Equinix DA3
Denver - CoreSite DE1
Greater London Area - Equinix LD5
Las Vegas - Switch LV
Los Angeles - CoreSite LA1
Los Angeles - Equinix LA1
Marseille - Interxion MRS1
Miami - Equinix MI1
Minneapolis - Cologix MIN1
New York City - Equinix NY5
Paris - Interexion PAR5
Silicon Valley - Equinix SV1
Seattle - Equinix SE2
Sydney, AU - Equinix SY2
Washington D.C. - CoreSite VA2
Washington D.C. - Equinix DC2
Create a Dedicated connection in the PacketFabric portal
From the dashboard, click Dedicated Cloud under Create New Service:
Select Microsoft Azure.
Complete the following fields:
Select Transport Product Type
Select one of the following:
Metro: Your source interface is in the same metro market as the Azure cloud on-ramp. Note that when it comes time to build virtual circuits, you can only access your Dedicate cloud port from other PacketFabric interfaces within the same metro/city.
Long-haul: Your source interface is not in the same metro market as the Azure on-ramp. You can provision virtual circuits to your Dedicated cloud port from any other port.
Select the destination interface location. This is the port that will have the cross connect to Azure, and is the port for which Azure will issue an LOA.
- Select Speed
- The speed/capacity you are using for your connection. This should be the same as the capacity you selected when creating your ExpressRoute Direct circuit (10 Gbps or 100 Gbps).
- Select Availability Zone
- Select a zone.
- Allocating connections within different zones supports redundancy.
- Select Encapsulation
- Select the same encapsulation that you selected when creating the ExpressRoute Direct.
- Select Port Category
- This indicates whether you intend to use this port from the primary or secondary connection in your ExpressRoute Direct circuit.
- Product Description
- Provide a meaningful name for the connection.
- Billing and Term Selection
- Select the appropriate billing account to associate with this service.
- From the Select Term menu, select a contract length.
Review your information. When everything is correct, click Place Order.
Order the cross connect
Generate the LOA from the Azure portal. For instructions, see Microsoft - Generate the Letter of Authorization.
From the Dedicated Cloud page, click the connection to open its side panel and then select Actions > Cross Connect:
The Create a Cross Connect page provides the NRC (non-recurring costs), MRC (monthly recurring costs), and any additional costs (such as a disconnection fee). These fees vary by site.
In the Description field, enter a brief name for the cross connect.
Click the upload icon to upload the LOA that Google sent you earlier.
You are redirected to the connection details page. From here you can track the progress of the cross connect installation. For more information, see Cross Connects.
Complete configuration in the Azure portal
Follow the instructions provided here: Microsoft - Create ExpressRoute Direct using the Azure portal.
Provision a virtual circuit
You can now provision virtual circuits to your Dedicated port. For more information, see Create and Manage Virtual Circuits for Dedicated Cloud Connections.