Share via

When migrating from Azure CDN to Azure Front Door, the resource created is neither a CDN nor a Front Door, which prevents using API and SDK on it

Lucas Bouvy 40 Reputation points
2025-08-01T12:59:21.4066667+00:00

I recently migrated from Azure CDN classic to Azure Front Door following Microsoft's announcement regarding CDN becoming restricted by august 15.

I'm in the process of updating my automations to use front door now, however I face an issue as the Front Doors I created (one was created by automatic migration, one was manually created as front door) are of this type : /subscriptions/[sub-id]/resourcegroups/[rg-name]/providers/Microsoft.Cdn/profiles/[front-door-name]

As a result of this, I can't use front door API, which gives me 404 errors because the provider is wrong :
{"error":{"code":"ResourceNotFound","message":"The Resource 'Microsoft.Network/frontdoors/[front-door-name]' under resource group '[rg-name]' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"}}

I am able to get a 200 response when using the old CDN API to get profile:

{
  "id": "/subscriptions/[sub-id]/resourcegroups/[rg-name]/providers/Microsoft.Cdn/profiles/[front-door-name]",
  "type": "Microsoft.Cdn/profiles",
  "name": "[front-door-name]",
  "location": "Global",
  "kind": "frontdoor",
  "tags": {},
  "sku": {
    "name": "Standard_AzureFrontDoor"
  },
  "properties": {
    "originResponseTimeoutSeconds": 60,
    "logScrubbing": null,
    "frontDoorId": "975b3faf-11f7-4835-a692-5ccae43345bb",
    "extendedProperties": {},
    "resourceState": "Active",
    "provisioningState": "Succeeded"
  }
}

But others method do not work, for instance I need to fetch custom domains to validate if certificate has been correctly provisioned, when using CDN I would use this endpoint
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{profileName}/endpoints/{endpointName}/customDomains/{customDomainName}?api-version=2025-04-15
But now since it is a frontdoor, I get 404 because domains are no longer attached to endpoints

I can't use the frontdoor corresponding API call :
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/validateCustomDomain?api-version=2019-05-01

Because my frontdoor is not recognized as such and I get 404

What should I do to migrate my automations ? Why are front door created when migrating CDN profiles not "real frontdoors" ?

Azure Front Door
Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
0 comments
Accepted answer
  1. Thanmayi Godithi 230 Reputation points Microsoft External Staff Moderator
    2025-08-04T11:56:04.5666667+00:00

    Hi @Lucas Bouvy,

    Thank you for reaching out to the Microsoft Q&A forum.

    From your description, it appears that you have migrated from Azure CDN (Classic) to Azure Front Door Standard/Premium, and now you're encountering 404 errors when attempting to automate tasks using the Front Door (Classic) APIs. Let me explain why this is happening and how to resolve it.

    Azure Front Door Standard and Premium use a different resource provider namespace of Microsoft.Cdn, while Azure Front Door (classic) uses Microsoft.Network.

    You migrated from Azure CDN (Classic) to Azure Front Door Standard/Premium. Post-migration, your Front Door resources appear under the Microsoft.Cdn/profiles namespace with "kind": "frontdoor", not under Microsoft.Network/frontDoors as in classic Front Door. This causes 404 errors when calling classic Front Door APIs because the resource provider and API endpoints differ.

    Key Points:

    Resource Provider:

    Classic Front Door: Microsoft.Network/frontDoors

    Front Door Standard/Premium: Microsoft.Cdn/profiles with kind=frontdoor

    API Differences:

    • Classic Front Door APIs (e.g., /frontDoors/{name}) are incompatible with Standard/Premium profiles.
    • Use the Azure CDN (Microsoft.Cdn) REST API for Standard/Premium. Example to validate a custom domain: POST /subscriptions/{subId}/resourceGroups/{rgName}/providers/Microsoft.Cdn/profiles/{profileName}/customDomains/{customDomainName}/validateCustomDomain?api-version=2025-04-15

    Custom Domains:

    • In Standard/Premium, custom domains are direct children of profiles: /profiles/{profileName}/customDomains
    • In classic CDN, custom domains were nested under endpoints: /profiles/{profileName}/endpoints/{endpointName}/customDomains

    Actionable Steps:

    • Update automation scripts and API calls to target Microsoft.Cdn/profiles endpoints with the latest API version (2025-04-15).
    • Replace all classic Front Door API calls with their equivalent Standard/Premium CDN API counterparts (afdEndpoints, customDomains, etc.).
    • Consult the latest Azure Front Door Standard/Premium REST API documentation for updated resource paths and capabilities.

    This differentiation is due to architectural changes; Front Door Standard/Premium is built on the Azure CDN platform, hence the change in resource provider and API surface.

    Reference: Azure Front Door tier migration | Microsoft Learn

    Kindly let us know if the above helps or if you need further assistance on this issue.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.