--- title: "Azure CDN Setup and Pricing 2026: Front Door Migration Guide" description: "Set up Azure content delivery in 2026: Azure Front Door vs classic Azure CDN, pricing, caching rules and a step-by-step migration path." image: https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-12-2026-07-01-19-9802-AM.jpeg --- [![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us) [๐Ÿ“˜Learn โ–พ](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us) [CDN Fundamentals](https://blog.blazingcdn.com/cdn-fundamentals?hsLang=en-us) [By Content Type](https://blog.blazingcdn.com/by-content-type?hsLang=en-us) [Advanced Concepts](https://blog.blazingcdn.com/advanced-concepts?hsLang=en-us) [Glossary](https://blog.blazingcdn.com/glossary?hsLang=en-us) [โšก Web Performance](https://blog.blazingcdn.com/web-performance?hsLang=en-us) [๐ŸŽฌVideo & Streaming โ–พ](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us) [๐Ÿ”ด Live Streaming](https://blog.blazingcdn.com/live-streaming?hsLang=en-us) [๐Ÿ“บ VOD & OTT](https://blog.blazingcdn.com/vod-ott?hsLang=en-us) [๐Ÿ’ฐ Bandwidth & Costs](https://blog.blazingcdn.com/bandwidth-costs?hsLang=en-us) [๐Ÿญ Other Industries โ–พ](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us) [๐Ÿ“บ Media & Broadcasting](https://blog.blazingcdn.com/media-broadcasting?hsLang=en-us) [๐Ÿ’พ Software & SaaS](https://blog.blazingcdn.com/software-saas?hsLang=en-us) [๐Ÿ—๏ธ DevOps & Cloud Infra](https://blog.blazingcdn.com/devops-cloud-infra?hsLang=en-us) [๐Ÿ“š AdTech & Advertising](https://blog.blazingcdn.com/adtech-advertising?hsLang=en-us) [๐ŸŽฎ Gaming & Esports](https://blog.blazingcdn.com/gaming-esports?hsLang=en-us) [๐Ÿ“ฑ Mobile Apps & Developers](https://blog.blazingcdn.com/mobile-apps-developers?hsLang=en-us) [๐Ÿค– AI & Machine Learning](https://blog.blazingcdn.com/ai-machine-learning?hsLang=en-us) [๐Ÿ›๏ธ Enterprise & Corporate](https://blog.blazingcdn.com/enterprise-corporate?hsLang=en-us) [๐Ÿ“š E-Learning & EdTech](https://blog.blazingcdn.com/e-learning-edtech?hsLang=en-us) [๐ŸŸ๏ธ Sports & Live Events](https://blog.blazingcdn.com/sports-live-events?hsLang=en-us) [๐Ÿ’ฐ Pricing & Costs โ–พ](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us) [Provider Pricing](https://blog.blazingcdn.com/provider-pricing?hsLang=en-us) [Cost Optimization](https://blog.blazingcdn.com/cost-optimization?hsLang=en-us) [Decision Support](https://blog.blazingcdn.com/decision-support?hsLang=en-us) [โšกCompare โ–พ](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [Provider Comparisons](https://blog.blazingcdn.com/provider-comparisons?hsLang=en-us) [Strategy Comparisons](https://blog.blazingcdn.com/strategy-comparisons?hsLang=en-us) [Ratings & Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [๐Ÿ“Š Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [๐Ÿ”’ Security โ–พ](https://blog.blazingcdn.com/cdn-security?hsLang=en-us) [Attack Protection](https://blog.blazingcdn.com/attack-protection?hsLang=en-us) [Encryption & Access](https://blog.blazingcdn.com/encryption-access?hsLang=en-us) [Video & DRM Security](https://blog.blazingcdn.com/video-drm-security?hsLang=en-us) [๐Ÿ“ Case Studies](https://blog.blazingcdn.com/case-studies?hsLang=en-us) [๐Ÿ”Œ Integrations](https://blog.blazingcdn.com/integrations?hsLang=en-us) [๐Ÿ› ๏ธ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us) [Get Started](https://blazingcdn.com/sign-up-contact-form/) [Learn](https://blog.blazingcdn.com/en-us/tag/learn) [Pricing - Pricing & Costs](https://blog.blazingcdn.com/en-us/tag/pricing-pricing-costs) [Pricing - Provider Pricing](https://blog.blazingcdn.com/en-us/tag/pricing-provider-pricing) [Learn - CDN Fundamentals](https://blog.blazingcdn.com/en-us/tag/learn-cdn-fundamentals) [Compare - Provider Comparisons](https://blog.blazingcdn.com/en-us/tag/compare-provider-comparisons) # Azure CDN Setup and Pricing 2026: Front Door Migration Guide Vadym Borovskyi Oct 12, 2026, 9:03:58โ€ฏAM ![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-12-2026-07-01-19-9802-AM.jpeg) New Azure CDN deployments now go only one way: Microsoft stopped accepting new Azure CDN Standard from Microsoft (classic) profiles on August 15, 2025 and retires the service on September 30, 2027. In 2026, a new Azure CDN setup means an Azure Front Door profile. Front Door Standard carries a $35 monthly base fee and Premium carries $330, and both bill per GB and per request on top. This guide covers the retirement timeline, current Azure CDN pricing, a step-by-step Front Door setup for Blob Storage, caching rules, a migration path with rollback, and a worked 150 TB cost model. Azure Front Door Standard costs $35 a month before traffic, and at 150 TB a month its published rates add up to about $9,500 (published price lists, checked August 2026). Classic Azure CDN from Microsoft cannot be created for new profiles and stops serving traffic on September 30, 2027, so any profile still on it has under a year left as of October 2026. ## **What happened to classic Azure CDN: the retirement timeline** Microsoft has collapsed its four CDN offerings into one product family over three years. The dates below come from vendor documentation and are the ones your migration plan must respect. - **Azure CDN Standard from Akamai:** retired October 31, 2023. Existing profiles were moved or shut down. - **Azure CDN Standard and Premium from Edgio (formerly Verizon):** retired January 15, 2025, ahead of the original schedule after Edgio's insolvency. Many azureedge.net hostnames from these profiles went dark that day. - **Azure Front Door (classic):** no new profiles since April 1, 2025; retirement on March 31, 2027. - **Azure CDN Standard from Microsoft (classic):** no new profiles or domain onboarding since August 15, 2025; retirement on September 30, 2027. Every pricing table that still lists Standard Verizon, Standard Akamai or Premium Verizon rates describes products you can no longer buy. The only tiers that matter for planning are Front Door Standard and Front Door Premium. ## **Azure CDN pricing in 2026: Front Door tiers and meters** Azure CDN pricing in 2026 means Azure Front Door pricing: a fixed monthly base fee per profile ($35 Standard, $330 Premium), plus metered data transfer from edge to client, data transfer from edge to origin, and HTTP/HTTPS requests billed per 10,000. Egress rates vary by billing zone, with North America and Europe cheapest and Asia-Pacific, South America and Africa higher. | Tier | Base fee | Billing model | Security and origins | Status | | --- | --- | --- | --- | --- | | Front Door Standard | $35 per month | Per GB by zone (roughly $0.08/GB for the first 10 TB in Zone 1, approximate), per 10,000 requests, origin transfer | Custom WAF rules only, public origins | Current | | Front Door Premium | $330 per month | Same meters, Premium request rates | Managed WAF rule sets, bot protection, Private Link origins | Current | | Azure CDN Standard from Microsoft (classic) | None | Per GB only, no request meter | No integrated WAF | No new profiles; retires September 30, 2027 | The real cost change in a migration is the request meter and base fee, which classic CDN never charged, so small-object workloads see the largest bill increase. HTTPS and Azure-managed certificates remain included on both Front Door tiers. Custom WAF rules on Standard carry their own policy and rule charges, while Premium bundles managed rule sets. ## **Azure Front Door vs classic Azure CDN: what changes in your config** Azure Front Door replaces the classic endpoint model with four objects: a profile, endpoints (azurefd.net hostnames), origin groups with health probes, and routes that bind domains and path patterns to origin groups. Caching, compression and query-string behavior are set per route and overridden by rule sets, not configured once per endpoint. Three behaviors catch teams moving from classic. Without Cache-Control from the origin, Front Door caches for a random duration between 1 and 3 days, which surprises anyone relying on short implicit TTLs. Compression applies only to files between 1 KB and 8 MB with a listed content type. Large objects are fetched from origin in 8 MB chunks, so range-heavy video and installer traffic produces many partial origin requests rather than one full fetch. ## **How to set up Azure CDN on Front Door for Blob Storage** An Azure CDN setup on Front Door Standard for a Blob Storage origin takes about 30 to 60 minutes, most of it waiting on DNS validation and certificate issuance. Prerequisites: a storage account with the static website or a public container enabled, rights to create resources in the subscription, and access to your DNS zone. 1. **Create the profile.** In the Azure portal open Front Door and CDN profiles, choose Create, then Azure Front Door, Custom create, Standard tier. Standard is enough unless you need Private Link or managed WAF rules. 2. **Add an endpoint.** Name it; Azure appends a hash and issues an azurefd.net hostname. Treat that hostname as internal and never hardcode it in clients. 3. **Create the origin group.** Add the storage account as origin type Storage or Storage static website, keeping the origin host header equal to the storage hostname. With a single origin, disable health probes: they generate origin requests and add nothing. 4. **Create the route.** Match the path pattern for all paths, accept HTTPS only with HTTP redirected, forward over HTTPS, enable caching, and choose a query-string behavior. Ignore query string is correct for versioned static assets. 5. **Enable compression** on the route for text types (HTML, CSS, JavaScript, JSON, SVG). 6. **Add the custom domain.** Create the TXT record Front Door shows under the dnsauth label, wait for Approved, attach an Azure-managed certificate, then point a CNAME at the endpoint hostname. Apex domains need an Azure DNS alias record. 7. **Validate.** Send two HEAD requests for one asset with any HTTP client. The X-Cache header should read TCP\_MISS, then TCP\_HIT. Note the X-Azure-Ref header value for support tickets. ### Caching rules that hold up at scale Put explicit Cache-Control headers on blobs at upload time and let the route honor origin. Then add a rule set with two rules: for fingerprinted extensions (js, css, woff2, images) use a route configuration override set to override always with a 365-day duration; for HTML and manifests, set a short duration such as 5 minutes. Use versioned filenames instead of wildcard purges, since purges take minutes to propagate and trigger an origin refill. ## **Migrating a classic Azure CDN profile to Front Door** Microsoft's in-portal migration tool moves an Azure CDN Standard from Microsoft (classic) profile to Front Door Standard or Premium in three phases: Validate checks compatibility, Prepare builds a new profile with converted endpoints, routes and domains while traffic stays on classic, and Migrate commits the switch. Abort is available until you commit. After Prepare, audit three areas manually. Rules engine conditions and rewrite actions do not translate one to one, so compare each converted rule against the original. Query-string caching modes need rechecking per route. Confirm which hostname clients use: move every client to a custom domain before the retirement date rather than depending on legacy azureedge.net behavior. ### Diagnostics and rollback Lower the CNAME TTL on every custom domain to 300 seconds at least 48 hours before cutover. Keep the classic profile intact until the new profile has carried a full week of traffic, which is possible until September 30, 2027. | Symptom | Likely cause | Fix | | --- | --- | --- | | Hit ratio near zero, X-Cache always TCP\_MISS | Route set to use query string while clients append cache-busting parameters | Ignore query string, or include only the parameters that change content | | X-Cache shows CONFIG\_NOCACHE or PRIVATE\_NOSTORE | Caching disabled on the route, or origin sends private or no-store | Enable caching; fix blob Cache-Control metadata | | 400 or 403 from Blob Storage | Origin host header does not match the storage hostname | Set the host header to the storage account hostname | | Custom domain stuck in Pending | Missing TXT record or conflicting existing CNAME | Recreate the dnsauth TXT record; regenerate the token if it expired | | 504 on large objects | Origin response timeout (default 60 seconds) exceeded | Raise the timeout on the endpoint, up to 240 seconds | Most post-migration incidents are cache-key and header problems visible in X-Cache within minutes, not network faults. Rollback is a DNS change: point the CNAME back at the classic endpoint, and with a 300-second TTL most resolvers follow within 5 to 10 minutes. ## **Worked cost model: 150 TB a month on Azure Front Door** Assumptions: 150 TB a month of edge egress mostly in Zone 1, a 1 MB average object, Front Door Standard. Published rates reach 150 TB, where transfer comes to about $9,500 (published price lists, checked August 2026), an effective $63 per TB. Requests: 150 TB at 1 MB per object is about 150 million requests, or 15,000 billing units of 10,000; at an assumed rate near $0.01 per unit, that adds roughly $150 (estimate). With the $35 base fee, the month lands near $9,700 before origin transfer. For the same 150 TB, BlazingCDN charges $590 as of October 2026: $415 for the first 100 TB plus 50 TB at $3.50 per TB. It bills from $5 per TB down to $2.50 per TB at volume, with one rate for US, Europe and Asia, no request fees and no long-term contract, so the request line above disappears. Current rates are on the BlazingCDN pricing page, and the [**BlazingCDN vs Azure CDN comparison**](https://blazingcdn.com/vs/azure-cdn/) sets the two billing models side by side. The honest limit: BlazingCDN is a delivery layer, not a security suite. It has no WAF, no DDoS mitigation, no HTTP/3 and no WebSockets, so Front Door stays in front of the application while heavy static files move to a second hostname. ## **Best fit by workload: Front Door Standard, Premium or a delivery CDN** | Workload | Best fit | Why | | --- | --- | --- | | Static site or SPA under 5 TB a month | Front Door Standard | Base fee dominates and stays small; native Azure integration | | API and app traffic needing WAF and Layer 7 routing | Front Door Standard or Premium | Integrated WAF, path routing, session affinity | | Origins reachable only privately | Front Door Premium | Private Link origins exist only on Premium | | Video, installers, game patches above 50 TB a month | Delivery CDN such as BlazingCDN, Front Door kept for the app | Per-TB cost gap grows with volume; no request meter on large files | Front Door earns its price on security and routing, while bulk egress is where a split architecture pays off. ## **Tuning checklist after cutover** - Track X-Cache hit share per route; above 85 percent is a reasonable target for static assets. - Normalize query strings so analytics parameters never fragment the cache key. - Confirm compressed responses for text types and expect none above 8 MB. - Review the request meter monthly against egress: a rising ratio signals shrinking objects. - Set Azure Cost Management budget alerts on the Front Door profile. ## **FAQ: Azure CDN pricing, setup and Front Door migration** ### How much does Azure CDN cost in 2026? Azure CDN in 2026 is billed as Azure Front Door: $35 a month for Standard or $330 for Premium, plus per-GB egress by zone and per-10,000 request charges. At 150 TB a month, published Front Door rates reach about $9,500 for transfer, per published price lists checked August 2026, before request and origin charges. ### Can I still create a new classic Azure CDN profile? No. Microsoft blocked new Azure CDN Standard from Microsoft (classic) profiles and domain onboarding on August 15, 2025. Akamai and Edgio tiers are already retired. Existing classic Microsoft profiles keep serving until September 30, 2027, so every new deployment and every long-term plan should target Azure Front Door Standard or Premium. ### What is the difference between Azure Front Door Standard and Premium? Azure Front Door Premium adds managed WAF rule sets, bot protection and Private Link origins to the Standard feature set, for $330 a month instead of $35. Caching, compression, rule sets, custom domains and managed certificates work identically on both, so static delivery without private origins rarely justifies Premium's base fee. ### How long does an Azure CDN to Front Door migration take? A classic Azure CDN to Front Door migration usually takes a few hours of hands-on work per profile, spread over one to two weeks. The tool's Validate and Prepare phases run in minutes, but rule auditing, domain revalidation, lowered DNS TTLs and a week of parallel observation before decommissioning make up most of the calendar time. ### Is HTTPS extra on Azure Front Door? No. HTTPS and Azure-managed certificates are included on Azure Front Door Standard and Premium at no extra fee. Certificates are issued after the custom domain passes TXT validation and renew automatically. Bring-your-own certificates stored in Azure Key Vault are also supported for teams that need specific certificate authorities or extended validation. ## **Price your Azure CDN traffic before the 2027 cutoff** This week, export 30 days of Front Door or classic CDN metrics and compute three numbers: egress TB by zone, requests per GB, and cache hit share per route. Requests per GB tells you how much of the bill the new request meter will add, and egress by route shows which paths are bulk files that could move to a separate hostname without touching your WAF or routing. Run the migration tool's Validate phase on any classic profile now, while rollback is still free. If that export shows tens of terabytes of video, installers or patches, the [**BlazingCDN CDN cost calculator**](https://blazingcdn.com/cdn-cost-calculator/) prices the same volume on progressive tiers from $5 per TB with no request fees. Share: [f](https://www.facebook.com/sharer/sharer.php?u=https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside) [in](https://www.linkedin.com/sharing/share-offsite/?url=https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside) [๐•](https://twitter.com/intent/tweet?url=https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside&text=) [โœ‰](mailto:?subject=%3Cspan%20id="hs_cos_wrapper_name"%20class="hs_cos_wrapper%20hs_cos_wrapper_meta_field%20hs_cos_wrapper_type_text"%20style=""%20data-hs-cos-general-type="meta_field"%20data-hs-cos-type="text"%20%3EAzure%20CDN%20Setup%20and%20Pricing%202026:%20Front%20Door%20Migration%20Guide%3C/span%3E&body=https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside) ![BlazingCDN](https://blog.blazingcdn.com/hs-fs/hubfs/Logo/blog-logo-w.png?height=24&name=blog-logo-w.png) *Heavy traffic.* Light bill. The CDN for video and large traffic Their monthly bill vs ours - 20 TBFastly $2,087**$92.50** - 50 TBCDN77 $990**$215** - 200 TBCloudFront $11,965**$765** Published list prices, Aug 2026 [Calculate your cost](https://blazingcdn.com/cdn-cost-calculator/?utm_source=blog&utm_medium=sidebar&utm_campaign=blog_sidebar&utm_content=compare_calc) ## Related posts [![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-13-2026-07-30-24-3649-AM.jpeg)](https://blog.blazingcdn.com/en-us/cbr-vs-vbr-choosing-a-bitrate-mode-for-streaming?hsLang=en-us) Learn ### [CBR vs VBR: Choosing a Bitrate Mode for Streaming](https://blog.blazingcdn.com/en-us/cbr-vs-vbr-choosing-a-bitrate-mode-for-streaming?hsLang=en-us) For most on-demand video, capped variable bitrate (VBR) wins the cbr vs vbr decision: it spends bits where the picture ... Oct 13, 2026, 9:32:48โ€ฏAM [Read more](https://blog.blazingcdn.com/en-us/cbr-vs-vbr-choosing-a-bitrate-mode-for-streaming?hsLang=en-us) [![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-13-2026-07-01-14-3701-AM.jpeg)](https://blog.blazingcdn.com/en-us/azure-cdn-vs-aws-cloudfront-which-is-better-for-enterprise-content-delivery?hsLang=en-us) Compare ### [Azure Front Door vs AWS CloudFront: Enterprise CDN Comparison](https://blog.blazingcdn.com/en-us/azure-cdn-vs-aws-cloudfront-which-is-better-for-enterprise-content-delivery?hsLang=en-us) As of October 2026, the Azure service that matches Amazon CloudFront is Azure Front Door Standard or Premium: Microsoft ... Oct 13, 2026, 9:03:40โ€ฏAM [Read more](https://blog.blazingcdn.com/en-us/azure-cdn-vs-aws-cloudfront-which-is-better-for-enterprise-content-delivery?hsLang=en-us) [![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-12-2026-07-30-18-1504-AM.jpeg)](https://blog.blazingcdn.com/en-us/what-is-a-keyframe-gop-size-and-keyframe-interval?hsLang=en-us) Learn ### [What Is a Keyframe? GOP Size and Keyframe Interval](https://blog.blazingcdn.com/en-us/what-is-a-keyframe-gop-size-and-keyframe-interval?hsLang=en-us) In answer to what is a keyframe: a keyframe, or I-frame, is a video frame encoded without reference to any other frame, ... Oct 12, 2026, 9:31:59โ€ฏAM [Read more](https://blog.blazingcdn.com/en-us/what-is-a-keyframe-gop-size-and-keyframe-interval?hsLang=en-us) [![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us) [๐Ÿ“˜ Learn](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us) [๐Ÿ“Š Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [๐ŸŽฌ Video & Streaming](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us) [๐Ÿญ Industries](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us) [๐Ÿ’ฐ Pricing & Costs](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us) [โšก Compare](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [๐Ÿ”’ Security](https://blog.blazingcdn.com/cdn-security?hsLang=en-us) [๐Ÿ› ๏ธ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us) [โœ๏ธ Publish with us](https://blog.blazingcdn.com/publish-with-us?hsLang=en-us) in f ๐• โœ‰ Copyright ยฉ BlazingCDN |. All rights reserved. ```json { "@context" : "https://schema.org", "@id" : "https://blazingcdn.com/#organization", "@type" : "Organization", "description" : "High-volume CDN for video, live streaming, OTT/IPTV, software, games, SaaS and large-file delivery.", "logo" : { "@id" : "https://blazingcdn.com/#logo", "@type" : "ImageObject", "height" : 560, "url" : "https://blazingcdn.com/wp-content/uploads/2024/08/logo-560-560.png", "width" : 560 }, "name" : "BlazingCDN", "sameAs" : [ "https://www.linkedin.com/company/blazingcdn", "https://x.com/BlazingCdn", "https://www.reddit.com/r/BlazingCDN/", "https://www.wikidata.org/wiki/Q141711074" ], "url" : "https://blazingcdn.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.blazingcdn.com/#website", "@type" : "WebSite", "inLanguage" : "en-US", "name" : "BlazingCDN Blog", "publisher" : { "@id" : "https://blazingcdn.com/#organization" }, "url" : "https://blog.blazingcdn.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside#article", "@type" : "BlogPosting", "author" : { "@id" : "https://blog.blazingcdn.com/en-us/author/blazingcdn#person", "@type" : "Person", "description" : "Vadym Borovskyi is Chief Product and Marketing Officer at BlazingCDN, where he has led product strategy and growth since 2021. He has more than 11 years of experience in IT product management and B2B marketing. On this blog he writes about CDN pricing and egress costs, video and software delivery, cache configuration, and how teams evaluate and switch CDN providers. He is based in Warsaw, Poland.", "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/vadym-borovskyi.jpg", "jobTitle" : "Chief Product and Marketing Officer", "knowsAbout" : [ "Content Delivery Networks (CDN)", "CDN pricing", "Video streaming delivery", "Software and game distribution", "Cache optimization", "Product Management", "B2B Marketing", "Digital Marketing", "Pay Per Click Marketing (PPC)", "Google Ads", "Search Engine Marketing (SEM)", "Marketing Strategy", "Artificial Intelligence (AI)", "Cloud Management", "SaaS Development", "IT Consulting", "Computer Networking", "Project Management", "Startups" ], "name" : "Vadym Borovskyi", "sameAs" : [ "https://www.linkedin.com/in/axelt/" ], "url" : "https://blog.blazingcdn.com/en-us/author/blazingcdn", "worksFor" : { "@id" : "https://blazingcdn.com/#organization" } }, "dateModified" : "2026-10-12T07:03:59Z", "datePublished" : "2026-10-12T07:03:58Z", "description" : "Set up Azure content delivery in 2026: Azure Front Door vs classic Azure CDN, pricing, caching rules and a step-by-step migration path.", "headline" : "Azure CDN Setup and Pricing 2026: Front Door Migration Guide", "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/Gemini-Blog/image-Oct-12-2026-07-01-19-9802-AM.jpeg", "inLanguage" : "en-us", "isPartOf" : { "@id" : "https://blog.blazingcdn.com/#website" }, "mainEntityOfPage" : { "@id" : "https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside", "@type" : "WebPage" }, "publisher" : { "@id" : "https://blazingcdn.com/#organization" }, "wordCount" : 2275 } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside#breadcrumb", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://blog.blazingcdn.com/en-us", "name" : "Blog", "position" : 1 }, { "@type" : "ListItem", "item" : "https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside", "name" : "Azure CDN Setup and Pricing 2026: Front Door Migration Guide", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.blazingcdn.com/en-us/set-up-microsoft-cdn-via-azure-step-by-step-guide-pricing-inside#faq", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Azure CDN in 2026 is billed as Azure Front Door: $35 a month for Standard or $330 for Premium, plus per-GB egress by zone and per-10,000 request charges. At 150 TB a month, published Front Door rates reach about $9,500 for transfer, per published price lists checked August 2026, before request and origin charges." }, "name" : "How much does Azure CDN cost in 2026?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "No. Microsoft blocked new Azure CDN Standard from Microsoft (classic) profiles and domain onboarding on August 15, 2025. Akamai and Edgio tiers are already retired. Existing classic Microsoft profiles keep serving until September 30, 2027, so every new deployment and every long-term plan should target Azure Front Door Standard or Premium." }, "name" : "Can I still create a new classic Azure CDN profile?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Azure Front Door Premium adds managed WAF rule sets, bot protection and Private Link origins to the Standard feature set, for $330 a month instead of $35. Caching, compression, rule sets, custom domains and managed certificates work identically on both, so static delivery without private origins rarely justifies Premium's base fee." }, "name" : "What is the difference between Azure Front Door Standard and Premium?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "A classic Azure CDN to Front Door migration usually takes a few hours of hands-on work per profile, spread over one to two weeks. The tool's Validate and Prepare phases run in minutes, but rule auditing, domain revalidation, lowered DNS TTLs and a week of parallel observation before decommissioning make up most of the calendar time." }, "name" : "How long does an Azure CDN to Front Door migration take?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "No. HTTPS and Azure-managed certificates are included on Azure Front Door Standard and Premium at no extra fee. Certificates are issued after the custom domain passes TXT validation and renew automatically. Bring-your-own certificates stored in Azure Key Vault are also supported for teams that need specific certificate authorities or extended validation." }, "name" : "Is HTTPS extra on Azure Front Door?" } ] } ```