ExpressRoute Circuit should be successfully provisioned

High Azure General expressroutecircuits-expressroute-circuit-successf

Applies to

Microsoft.Network/expressRouteCircuits

What CGPulse checks

A resource passes this rule when circuitProvisioningState must equal Provisioned. Anything else is reported as a finding with the evaluated property value attached as evidence.

How to fix it

Resolve provisioning with the service provider to ensure reliable connectivity. In Azure Portal: ExpressRoute Circuit > Overview > check provisioning state. See: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-troubleshooting-expressroute-overview

CLI

az network express-route show --ids "{id}" --query circuitProvisioningState

Bicep

resource expressRoute 'Microsoft.Network/expressRouteCircuits@2023-09-01' = {
  name: '{name}'
  location: location
  sku: {
    name: 'Standard_MeteredData'
    tier: 'Standard'
    family: 'MeteredData'
  }
  properties: {
    serviceProviderProperties: {
      serviceProviderName: '{provider}'
      peeringLocation: '{peeringLocation}'
      bandwidthInMbps: 50
    }
  }
}

Terraform

resource "azurerm_express_route_circuit" "{name}" {
  name                  = "{name}"
  resource_group_name   = "{rg}"
  location              = var.location
  service_provider_name = "Equinix"
  peering_location      = "Silicon Valley"
  bandwidth_in_mbps     = 50
  sku {
    tier   = "Standard"
    family = "MeteredData"
  }
}

Compliance frameworks

Cloud Security: Azure Foundations

Is your environment compliant with this rule?

CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.

Run a free scan