Azure ExpressRoute Circuit
Does ZopNight manage Azure ExpressRoute Circuit?
ExpressRoute circuits bill monthly by bandwidth tier from the moment Azure provisions them, even when the connectivity-provider side was never completed, so a circuit can charge for months while carrying zero traffic. ZopNight discovers circuits via Resource Graph with bandwidth and provisioning state, attributing spend through the Cost Management API.
Rules that fire on Azure ExpressRoute Circuit
No active rule family targets Azure ExpressRoute Circuit today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost visibility only. |
ExpressRoute circuits provide dedicated private connectivity between on-premises networks and Azure, billed monthly by bandwidth tier. Unprovisioned or underused circuits are among the largest fixed network charges.
A fixed monthly charge tied to bandwidth tier
An ExpressRoute circuit bills a flat monthly amount determined by its bandwidth tier and plan, independent of utilization. A circuit runs at the same price moving a trickle of backup traffic as it does saturated. Critically, it runs at the same price moving nothing. Among networking resources this makes ExpressRoute the heaviest fixed line item most estates carry: where a public IP or DNS zone leaks small amounts, an abandoned circuit leaks at enterprise-connectivity rates, month after month, until someone notices.
Half-provisioned circuits, full-price billing
Provisioning an ExpressRoute is a two-party act: Azure creates the circuit and issues a service key, then the connectivity provider must complete their side before traffic can flow. Azure’s meter starts at its step, not the provider’s. A circuit whose provider side was never finished (a stalled project, a switched provider, a proof of concept that ended) is the canonical ExpressRoute waste pattern: fully billed, structurally incapable of carrying a single packet. The second pattern is the migration leftover, where traffic moved to a new circuit or to VPN and the old circuit was never deprovisioned.
Circuit facts ZopNight records
Discovered via Azure Resource Graph with bandwidth and provisioning state. Cost Management billing attributes spend, flagging circuits whose provider side was never completed. The provisioning-state field is what turns billing data into a verdict: spend on a circuit still awaiting its provider is spend with no possible return. ExpressRoute is discovery and cost visibility only. A dedicated physical-connectivity product has no stop/start lifecycle to schedule, so remediation is always a deprovision-and-delete decision made by a human.
ExpressRoute circuits in the portal
Azure portal → ExpressRoute circuits lists each circuit with its provider, bandwidth, and both status fields. The pair to read together is Circuit status and Provider status: Enabled plus Not provisioned is the fully-billed, zero-traffic combination worth escalating the day it appears.