Azure CDN Profile
Does ZopNight manage Azure CDN Profile?
Azure CDN profiles bill by egress volume, the gigabytes delivered from edge locations, so a forgotten endpoint serving stale assets keeps incurring transfer charges every month. ZopNight inventories profiles via Resource Graph and attributes egress spend from Cost Management, making endpoints nobody has touched in months visible for cleanup.
Rules that fire on Azure CDN Profile
No active rule family targets Azure CDN Profile 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. |
Azure CDN profiles cache and deliver content from edge locations, billed by egress volume. Forgotten endpoints serving stale content keep incurring transfer charges.
Egress is the CDN meter
A CDN profile’s cost tracks the gigabytes it delivers from the edge, with rates varying by delivery region. That makes it one of Azure’s more honest meters, since an endpoint that delivers nothing costs essentially nothing, but also one of the easiest to lose track of, because the charge follows consumption by end users rather than any decision the owning team makes. An old JavaScript bundle referenced by third-party sites, a public download link shared years ago, or a misconfigured cache rule that keeps fetching from origin will all sustain egress charges on an endpoint everyone assumes is dormant. The bill arrives whether or not the traffic is wanted.
Visibility ZopNight brings to CDN endpoints
Discovered via Azure Resource Graph. Cost Management billing attributes egress spend for review of unused endpoints. There is no lifecycle action to schedule against a CDN profile, because content delivery cannot be paused, only reconfigured or deleted. So ZopNight’s value is attribution: putting a monthly egress figure against each profile so that “is anyone still using this?” becomes a number rather than a hallway question. Endpoints whose spend persists after their product was retired are exactly the ones this surfaces.
Stale endpoints that keep transferring
Watch for these patterns. Orphaned asset hosts: a CDN endpoint still fronting a storage container of images for a decommissioned site, paying delivery costs for scrapers and stale bookmarks. Hotlinked content: files on a public endpoint embedded by external pages, generating egress for other people’s audiences. Origin-miss loops: an endpoint with broken caching that forwards most requests to origin, paying CDN egress on top of origin bandwidth for no caching benefit.
Finding CDN profiles in the portal
Azure portal → Front Door and CDN profiles lists classic CDN profiles alongside Front Door. Drill into a profile’s endpoints and review each one’s traffic charts. Sustained egress on an endpoint with no active product behind it is a deletion conversation, not a mystery.