--- title: "Azure ExpressRoute Portal" canonical: "https://docs.aryaka.com/space/KNOW/1292304437/Azure%20ExpressRoute%20Portal" format: markdown --- Microsoft Azure is a computing and services platform hosted in datacenters that are managed and supported by Microsoft. Microsoft provides Azure ExpressRoute as a service, which allows customers to create private connections between Azure datacenters and a colocation. Aryaka—as a service provider—offers optimized access to your Azure resources by providing a low latency, redundant, and dedicated connection from the Aryaka POPs. This allows customers to establish a highly available end-to-end path between the remote sites and Microsoft Azure using Aryaka’s global, secured private network. ExpressRoute is available from Aryaka for the following regions. Azure approved list of locations and regions can be found in the ExpressRoute connectivity providers document at microsoft.com.  Azure Location Aryaka POP Location Provider Silicon Valley San Jose Equinix Washington DC Ashburn Equinix New York New Jersey Equinix Dallas Dallas Equinix Chicago Chicago Equinix Seattle Seattle Equinix Amsterdam Amsterdam Equinix Tokyo Tokyo Equinix London  London Equinix Sao Paulo Sao Paulo Equinix Singapore Singapore Equinix Hong Kong  Hong Kong Equinix This document explains how to connect Azure's VNets in these regions with the nearby Aryaka POP using ExpressRoute. Contact Aryaka support to discuss possible VPN connectivity to other Azure locations. Prerequisites Satisfy the following prerequisites before performing the ExpressRoute configuration: You must be an administrator user on the Azure Portal. You must provide the following information to Aryaka support before configuring an ExpressRoute: Location of the Azure VNet instance Peering type (see the next section for additional information) Azure subscription ID Local subnets in the VNet Remote sites and subnets to be made accessible over Aryaka Additionally, after ExpressRoute is configured, you must share the Azure service key used by ExpressRoute with Aryaka support. Peering type Determine the peering type based on the resources that you want to access over ExpressRoute: Private peering—Used to access all private resources hosted in Azure, including, but not limited to, your virtual machines and Azure’s private cloud services. Microsoft peering—Used to access services like Microsoft 365, Power BI, Active Directory, Azure DevOps, virtual machines, and load balancers over a public IP address. Aryaka does not accept new ExpressRoute connection requests for Microsoft peering. Refer to Azure connectivity with Aryaka for alternate options to access your public resources. Configure an Azure ExpressRoute circuit Complete the following procedure to configure an ExpressRoute circuit in the Azure Portal. While we have made every effort possible to ensure accurate descriptions and screen captures at time of publication, updates to the third-party UI are beyond our control. Refer to the third-party documentation to ensure you have the most recent information. To configure an Azure ExpressRoute circuit Login to the Azure portal https://portal.azure.com . The Azure Home page appears. Click the blue  Portal Menu  icon, then select All Services > Networking > ExpressRoute circuits from the series of menus that appear: Click Create . The Create ExpressRoute page appears with the Configuration tab displayed by default: Provide the following project details on the Configuration tab:  Subscription—Select the subscription type for your account. Resource Group—Select a resource group for the ExpressRoute or click Create new to create new one. Resiliency—Click Standard Resiliency . Click Next: Configuration . The Configuration tab page appears: Provide the following details on the Configuration tab: Note: You can either use an existing circuit or create a new one  Region—Select the geographic location where your instance is deployed. Circuit Name—Enter a name for the new ExpressRoute circuit. Port Type—Click Provider . Peering Location—Select one of the locations supported by Aryaka (refer to the table earlier in this topic). Provider—Select Equinix . Bandwidth—Select  Agreed upon bandwidth of ExpressRoute circuit . SKU—Select as appropriate. The default is Standard. Billing Model—Select as appropriate. The default is Metered. Click  Review + create . The Review + Create tab page appears: Verify all of the details, and then click Create . Azure takes a moment to configure and deploy the new ExpressRoute circuit. After it is deployed, the Provider Status of the circuit is Not Provisioned: Share the service key with Aryaka support so they can complete their part of configuration. Because the provider is Equinix, you must configure the peering as described in the next section. To configure Equinix private peering Navigate to your ExpressRoute page and select the newly created circuit. Ensure the circuit’s status is Provisioned, then click Private peering . The Private Peering page appears: Enter following information provided by Aryaka: Peer ASN—Enter 11179. Subnets—Select IPv4. IPV Primary subnet—Enter the primary subnet for the BGP session.  IPV Secondary subnet—Enter the secondary subnet for the BGP session. The second IP of the /30 is used by the Microsoft gateway. VLAN ID— Enter a unique dot1.q VLAN ID in 3xxx. Shared key—Can be left blank if one was not provided. Click Save . After the peering is complete, and Aryaka has configured necessary links with remote sites, verify access from Azure to the remote site subnets and from the subnets to Azure. In this topic Related topics Azure connectivity with Aryaka ExpressRoute documentation (microsoft.com)