Skip to main content
Verifying an ExpressRoute circuit’s provisioning and operational state is one of the first steps when troubleshooting connectivity issues. Use Azure PowerShell to inspect the circuit resource and confirm both Azure-side and service-provider provisioning information.
A presentation slide titled "Verifying Circuit Provisioning and State" with a large blue-green rounded shape and a white checkmark on the right. The bottom-left shows a small "© Copyright KodeKloud" label.

​
Inspect the ExpressRoute circuit with PowerShell

Run Get-AzExpressRouteCircuit and specify the resource group and circuit name: 
Get-AzExpressRouteCircuit `
  -ResourceGroupName "Lab-Network-RG" `
  -Name "Lab-ER-Circuit"
Sample output (showing properties most relevant to provisioning and state): 
Name                                   : ER-Demo-Ckt-SV
ResourceGroupName                      : USWest-ER-Demo-RG
Location                               : westus
Id                                     : /subscriptions/3e45ff-2422-56ead-2190b/resourceGroups/Lab-Network-RG/providers/Microsoft.Network/expressRouteCircuits/Lab-ER-Circuit
Etag                                   : W/"#########################"
ProvisioningState                      : Succeeded
Sku                                    : {
                                           "Name": "Standard_UnlimitedData",
                                           "Tier": "Standard",
                                           "Family": "UnlimitedData"
                                         }
CircuitProvisioningState               : Enabled
ServiceProviderProvisioningState       : Provisioned
ServiceProviderNotes                   :
ServiceProviderProperties              : {
                                           "ServiceProviderName": "*****",
                                           "PeeringLocation": "*******",
                                           "BandwidthInMbps": 200
                                         }
ServiceKey                              : ***************************
Peerings                                : []
Authorizations                          : []

​
Key fields to check

Use the table below to quickly identify which fields indicate healthy provisioning and what to watch for when troubleshooting.
FieldWhat it meansExpected value / notes
ProvisioningStateAzure resource provisioning statusSucceeded — Azure-side deployment succeeded
CircuitProvisioningStateCircuit enabled/disabled in AzureEnabled — circuit is active in Azure
ServiceProviderProvisioningStateProvider-side provisioningProvisioned — provider has completed their work
ServiceKeyUnique key given to provider to link their order to your circuitPresent and kept private — provider needs this to provision
Peerings / AuthorizationsConfigured peerings and any delegated authorizationsExpected peerings should appear (e.g., AzurePrivatePeering, MicrosoftPeering)
If any of these states are unexpected (for example ProvisioningState = Failed, CircuitProvisioningState = Disabled, or ServiceProviderProvisioningState = NotProvisioned), the issue is likely at the provisioning stage or with the service provider. Open a support ticket with your provider and verify any required provisioning steps or outstanding actions on their side.

​
Troubleshooting next steps

  1. Confirm provisioning is complete:
    • ProvisioningState = Succeeded
    • CircuitProvisioningState = Enabled
    • ServiceProviderProvisioningState = Provisioned
  2. If provisioning looks correct but connectivity fails, check:
    • Peerings configuration (ensure Azure, private, or Microsoft peerings are present and configured)
    • BGP status and neighbor sessions (see BGP overview)
    • Route filters and advertised prefixes (verify route filter configuration)
    • Local network gateway settings and on-premises configuration
  3. Use the Azure portal as an alternative:
    • Open the ExpressRoute circuit in the Azure portal and review the Overview and Provisioning / Service Provider sections for current statuses and any provider notes.
By confirming the provisioning state in Azure and the service provider’s provisioning state, you can quickly determine whether connectivity issues are due to incomplete provisioning or configuration problems that require deeper BGP and routing checks.

Watch Video