Azure Classic CDN & Front Door Retirement Checker

Microsoft is retiring the classic Azure edge services:

• Azure Front Door (classic) retires on 31 March 2027.
• Azure CDN Standard from Microsoft (classic) retires on 30 September 2027.
• "Starting April 1, 2028, classic endpoints are no longer supported and might stop functioning." Custom domains must point to the new name-hash.z01.azurefd.net endpoint instead of name.azurefd.net (Front Door classic) or name.azureedge.net (CDN classic) by 31 March 2028 — even after a profile has been migrated.

Source: Microsoft Learn, Front Door migration FAQ (updated 26 Aug 2026).

Microsoft emails the subscription owner, but agencies, MSPs, security teams and companies that only use assets served from someone else's endpoint aren't told. This Actor checks, from the outside and in bulk:

• Hostnames: follows each custom domain's CNAME chain and tells you whether it ends at a Front Door (classic) endpoint, an azureedge.net (CDN classic) endpoint, or an already-migrated Standard/Premium endpoint.
• Pages (optional): reads a web page and checks every host its scripts, styles, images, fonts and iframes load from, so you also catch third-party widgets and asset hosts that sit on classic endpoints.

No Azure login, no access to anyone's subscription: public DNS and public pages only.

Input

{
  "hostnames": ["www.example.com", "cdn.example.com", "assets.example.org"],
  "pageUrls": ["https://www.example.com"]
}

Output

{
  "hostname": "amcdn.msftauth.net",
  "kind": "classic-front-door",
  "risk": "high",
  "endpoint": "mecontrol-prod.azurefd.net",
  "cnameChain": ["mecontrol-prod.azurefd.net", "mr-azurefd.tm-azurefd.net"],
  "action": "Points to a Front Door (classic) endpoint. Front Door (classic) retires on 31 Mar 2027: migrate the profile..."
}

kind is classic-front-door, classic-cdn (azureedge.net), front-door-standard-premium (nothing to do) or not-azure-cdn. (Real example from 27 Oct 2026; js.monitor.azure.com in the same check is already on a Standard/Premium endpoint.)

Good to know

• A profile that was migrated but whose CNAME still points to the classic endpoint looks the same as one that wasn't migrated: both need the CNAME change before 31 March 2028.
• *.azureedge.net hostnames used directly (without a custom domain) are reported too: replace them in your apps and integrations.

Pricing

Pay per hostname checked.

FAQ

When does Azure Front Door classic retire? On 31 March 2027. Azure CDN Standard from Microsoft (classic) retires on 30 September 2027, and classic endpoints may stop working from 1 April 2028.

How do I find which of my domains use azureedge.net? Paste your hostnames (or your DNS zone's CNAME records) into this Actor; every hostname whose CNAME chain reaches azureedge.net is flagged.

What do I change after migrating to Front Door Standard/Premium? Point the custom domain's CNAME to the new name-hash.z01.azurefd.net endpoint, verify traffic, then delete the classic resource (Front Door classic).

More tools from the same author

• Google Merchant Center Q&A Writer: write the new question_and_answer attribute for every product, as a ready supplemental feed.
• AI Visibility Monitor: does ChatGPT, Perplexity, Claude or Gemini recommend your brand.
• Shopify Script Tag Shutoff Scanner: which apps on a Shopify store stop on 1 March 2027, and legacy customer accounts.
• PayPal Legacy Button Finder: every old PayPal Buy Now / Add to Cart button before PayPal retires them.
• SSL Root Certificate Distrust Checker: which sites, APIs and mail servers break when Mozilla removes 19 roots on 15 April 2027.
• Drupal Version & End-of-Life Checker: which sites run Drupal 10 (end of life 9 December 2026) or older.
• Website 2027 Breakage Audit: every 2026-2027 deadline (certificates, Shopify, PayPal, Azure, Drupal, PHP) in one report per site.

Microsoft, Azure and Azure Front Door are trademarks of the Microsoft group of companies. This Actor is independent and not affiliated with or endorsed by Microsoft.