Azure Content Delivery Network (CDN) is a managed edge-caching service that stores eligible copies of web content at distributed locations closer to users. It can reduce the distance a request travels to an origin and limit repeated transfers from that origin. Azure CDN Standard from Microsoft (classic) is now a legacy service: Microsoft says it retires on September 30, 2027, and directs new and migrating workloads toward Azure Front Door Standard or Premium.
What Azure CDN does
A website or application normally retrieves content from an origin, such as an Azure Storage account or web application. With a CDN, eligible responses can be cached at edge points of presence (PoPs). When a user requests cached content, a nearby edge location can serve it instead of sending every request back to the origin.
This is most useful for content that can be reused across requests, such as images, scripts, stylesheets, downloads, and other static assets. It can reduce latency for users far from the origin and reduce repeated origin transfers. A CDN does not make every request faster: uncached, non-cacheable, or frequently changing content may still need to be fetched from the origin.
How Azure CDN handles a request
- A client requests content. The request is directed to the CDN endpoint associated with the content.
- The edge checks its cache. If an eligible, usable copy is present, the edge can return it to the client.
- A cache miss goes to the origin. The CDN retrieves the content from the configured source and may cache it according to the applicable caching rules.
- Later requests may use the cached copy. Serving reusable content at the edge can reduce repeated origin transfers.
Microsoft describes Azure CDN as storing cached content at PoPs close to consumers. The origin remains the source of truth; the CDN is an intermediary for delivery, not a replacement for the storage or application that produces the content.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
Azure CDN and Azure Front Door compared
Both services use globally distributed infrastructure, but they address different delivery needs. Azure CDN is centered on globally distributed content caching. Azure Front Door is Microsoft’s broader application-delivery service, with Layer 7 load balancing and application-layer routing alongside caching and security capabilities.
| Decision area | Azure CDN | Azure Front Door |
|---|---|---|
| Best fit | Workloads centered on globally distributed delivery of cacheable content. | Applications needing a broader combination of static and dynamic delivery. |
| Routing | Edge content delivery and caching. | Layer 7 application delivery, including routing and health-aware traffic handling. |
| Security | Primarily a content-delivery service. | Application protection capabilities, including enhanced Web Application Firewall (WAF) capabilities in the recommended Standard and Premium tiers. |
| Private connectivity | Evaluate the specific tier and required integration. | Microsoft identifies Private Link integration for Standard and Premium. |
| Current lifecycle | CDN Standard from Microsoft (classic) is being retired; it is not a normal choice for a new deployment. | Microsoft’s recommended direction for new and migrating workloads. |
| Pricing | Depends on the selected tier and applicable regional pricing. | Depends on tier, geography, traffic, and contract; check current regional pricing. |
The services should not be treated as interchangeable solely because both can cache content. If an application needs routing decisions, health-aware failover, WAF protection, or private connectivity, assess Front Door’s features and requirements directly. For a workload using CDN mainly to distribute static files, compare whether Front Door’s capabilities and commercial model suit that simpler need.
Is Azure CDN still available?
Microsoft’s retirement FAQ describes CDN Standard from Microsoft (classic) as a legacy static-caching service. The FAQ says that new resource creation, new domain onboarding, and managed certificates stopped on August 15, 2025, and gives September 30, 2027 as the retirement date. Microsoft’s pricing page separately says no new instances will be created as of October 1, 2025. These are distinct dates stated on different Microsoft pages; for deployment planning, treat the classic tier as closed to new deployments and check the current Azure documentation for the rules that apply to an existing resource.
The retirement date is not a reason to wait until the deadline to plan. Existing deployments should be inventoried and their replacement tested before production traffic is changed.
What is replacing Azure CDN?
Microsoft points new and migrating workloads to Azure Front Door Standard or Premium. The retirement FAQ describes these tiers as a modern platform for static and dynamic delivery, with enhanced WAF capabilities, Private Link integration, and a simplified pricing model.
That recommendation does not establish that every CDN configuration has a drop-in equivalent or that migration is automatic. Feature availability, regional pricing, traffic patterns, origin behavior, security requirements, and the existing configuration all affect the right design. Verify current support and migration instructions for the workload before changing production traffic.
Rank #4
How to decide whether Front Door fits a CDN workload
- Identify what is being delivered. Separate cacheable static assets from dynamic requests that must be handled by the application.
- List routing requirements. Determine whether edge caching is enough or whether Layer 7 rules, health-aware routing, or broader application delivery are needed.
- Review security and connectivity. Check whether WAF protections or Private Link are required, and confirm the capabilities and configuration available in the selected tier.
- Check lifecycle and migration scope. If the workload uses CDN Standard from Microsoft (classic), document its current endpoints, domains, certificates, origins, and caching behavior, then consult Microsoft’s current migration guidance.
- Compare commercial terms for the actual workload. Use current regional pricing for the relevant tier and estimate based on expected traffic and configuration. There is no single representative price or per-GB figure that applies across regions and contracts.
- Validate before cutover. Test representative content and application flows, including cache behavior and origin access, then plan the production traffic change and rollback approach.
What to check before migrating
Do not assume that moving a CDN endpoint means copying its hostname into a new service. A migration can affect how domains, certificates, origins, cache rules, routing, and security are configured. Review each of these against the current Front Door documentation and the needs of the application. Where a capability or regional availability is not confirmed for the intended configuration, verify it with current Microsoft product documentation before committing to a design.
Microsoft has not established a universal latency improvement, PoP count, or representative price in the information summarized here. Actual performance depends on the users, origin, content, cacheability, network conditions, and configuration; costs depend on tier, geography, traffic, and contract.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
