---
title: "Azure ExpressRoute Power Shell"
canonical: "https://docs.aryaka.com/space/KNOW/1292894279/Azure%20ExpressRoute%20Power%20Shell"
format: markdown
---
Microsoft Azure is an internet-scale computing and services platform hosted in data centers managed or supported by Microsoft. Microsoft provides Azure ExpressRoute as a service that allows customers to create private connections between Azure data centers and a colocation. This allows the colocation to access the Azure services in a secure, reliable manner with faster speeds and lower latency. Customers with Azure subscriptions in US and South East Asia can use Azure ExpressRoute with Aryaka to optimize access to their services. The following table maps Azure regions to the nearest Aryaka POP that supports ExpressRoute connectivity: Azure Location Aryaka POP Location California-West US San Jose Virginia-East US Ashburn or New Jersey Texas-South Central US Dallas Seattle Seattle Chicago Chicago Brazil Sao Paulo Netherlands - West Europe Amsterdam Frankfurt (Germany West Central) Frankfurt Dublin Dublin London London Hong Kong Hong Kong Tokyo, Saitama-Japan East Tokyo South East Asia Singapore Sydney (Australia Southeast) Sydney All other Azure datacenter locations connect to Aryaka using Azure VPN. This document describes the steps that Aryaka customers must perform to enable ExpressRoute peering for their configuration instance. Prerequisites To configure an Azure instance to connect to Aryaka using ExpressRoute, the following information must be shared with  support@aryaka.com . Where is the Azure Service hosted? Azure subscription ID. Azure service key (created as described in the next section) Is the Azure subscription for a private virtual network, a public service, or both? Private virtual networks use private peering and are used for virtual machines and private cloud services. If the subscription is for a private virtual network, what are the subnets at this location that should be accessed over Aryaka? Public services use public peering and are used for web apps, service bus, CDN, and so on. A full list of services can be found  here . Aryaka support uses this information to configure your Aryaka network subscription to connect to Azure. After this is complete, the virtual circuit created as described later in this document has its state changed to Provisioned. Create a service key for Aryaka Install Azure Power Shell as described in the  Azure documentation . Issue the following commands to import the PowerShell module for ExpressRoute: Import-Module 'C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure\Azure.psd1'
Import-Module 'C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure\ExpressRoute\ExpressRoute.psd1' Issue the following command to log in to your Azure account using PowerShell: PS C:\> Add-AzureAccount Enter your credentials in the dialog that appears. Issue the following command to display a list of providers, circuit locations, and circuit bandwidth: PS C:\> Get-AzureDedicatedCircuitServiceProvider  Output similar to the following appears: Issue the following command to create new circuit  and  a new service key. PS C:\> New-AzureDedicatedCircuit Provide the following circuit information: Enter Aryaka Networks as the Service Provider Name. Set the BillingType to MeteredData or UnlimitedData as appropriate. Enter 200 as the Bandwidth. Enter the Location from the Dedicated Circuit Location column in the following table: Issue the following command to display the circuit configuration: PS C:\> Get-AzureDedicatedCircuit 
  Bandwidth : 200
  CircuitName : aryakaazure-sjc3
  Location : Silicon Valley
  ServiceKey : 9b5ba1a3-8aed-4f61-914f-dc667b6ff441
  ServiceProviderName : aryaka networks
  ServiceProviderProvisioningState : NotProvisioned
  Status : Enabled Copy the circuit configuration output from the previous step to a file or email message and send it to  support@aryaka.com . After Aryaka support performs the configuration based on this output, you are contacted to migrate the traffic from the Azure VPN to Aryaka as described in the next section. If you do not already have an Azure VPN tunnel to migrate from, skip to the Linking Virtual Network to Circuit section, and instead perform the procedure in it. Migrate traffic from Azure VPN to Aryaka 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 move the exiting virtual network from Azure VPN gateway to Aryaka Delete the existing site-to-site gateway from the Azure portal. Resize the gateway subnet to a /28 and save the configuration. Click the  Use ExpressRoute  checkbox on the gateway. Create the gateway. Link the virtual link to the ExpressRoute circuit as described in the next section. Link virtual network to circuit After the status of the circuit configured by Aryaka support is set to Provisioned, you must link the virtual network to the circuit. Issue the following command to verify the state of the circuit in the ServiceProviderProvisioningState output: PS C:\> Get-AzureDedicatedCircuit Ensure the output returned by the previous command matches the following two fields: Issue the following command to link the virtual network to the circuit: PS C:\> New-AzureDedicatedCircuitLink Enter the following parameters when prompted by the output: ServiceKey—Key generated in Step 6 of Create a service key for Aryaka. You can also view the key in the output of the Get-AzureDedicatedCircuit command VNetName—Name of the virtual network that you want to link to the circuit. After the status of the Azure Dedicated Circuit link is set to Provisioned by Aryaka support, the configuration is complete and remote sites can access the Azure subnets to Aryaka. In this topic Related topics Azure connectivity with Aryaka Azure ExpressRoute Portal Azure VPN ExpressRoute documentation  ( microsoft.com )