Migration from CDN to Front Door did not finish - can't edit resource

Question

Migration from CDN to Front Door did not finish - can't edit resource

Patrick Gebhardt 20

Hello,

I tried to update my Azure CDN to Azure Front Door. The migration did run for roughly 44 minutes, before it was canceled with the following error:
Failed to migrate CDN (classic) Failed to migrate the CDN (classic). Error: Sorry, it looks like there was an error on our end. Please contact Support if you keep having this problem

When looking into the resource, I am also unable to edit any configuration as it is stating:

This profile cannot be edited during migration.

When looking into the resource via CLI, I get the following information:

{

"id": "redacted",

"kind": "cdn",

"location": "WestUs",

"name": "redacted",

"properties": {

"extendedProperties": {

  "Sku": "Standard_AzureFrontDoor"

},

"provisioningState": "Succeeded",

"resourceState": "CommittingMigration"

},

"sku": {

"name": "Standard_Microsoft"

},

"tags": {},

This does state that the migration is done, but not committed. How can I commit it so that I can change configurations?

Thanks and Best Regards

Anonymous

2025-09-26T08:07:26.2566667+00:00

Hello @Patrick Gebhardt,
Good day.

Could you please review my comment and let us know if it was helpful? If you need any further assistance, please feel free to reach us.

Regard's
Jeevan S
Anonymous

2025-09-29T04:00:42.6533333+00:00

Hello @Patrick Gebhardt,
Good day.

Just checking in to see if you had a chance to see the previous response by Jeevan Shanigarapu. To help the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer. And, if you have any further questions do let us know.

Regard's
Jeevan S

Answer accepted by question author

Anonymous

Hello @Patrick Gebhardt,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand your question about the Azure CDN (Classic) migration to Azure Front Door Standard/Premium being stuck in the CommittingMigration state. This typically occurs when the migration encounters a backend error or a validation issue, which can result in the profile being locked and prevent configuration changes.

To resolve the issue, please follow the steps below:
Try to commit the migration manually via PowerShell:

Enable-AzFrontDoorCdnProfileMigration `

-ProfileName "<YourFrontDoorProfileName>" `

-ResourceGroupName "<YourResourceGroupName>"

This attempts to force the migration to complete.

If the commit does not succeed, cancel the operation and try again.

Stop-AzFrontDoorCdnProfileMigration `

-ProfileName "<YourFrontDoorProfileName>" `

-ResourceGroupName "<YourResourceGroupName>"

This will cancel the migration and restore the profile, allowing you to try again after resolving any problems.

Check prerequisites before retrying:

Make sure all custom domains are validated and have HTTPS enabled.

Check Key Vault permissions for certificates if they are being used.

Verify that backend pools and routing rules are set up properly.

Note: During this transitional phase, you won't be able to edit the profile. After the migration is finalized, it can't be rolled back, so make sure to check your configuration before attempting again.

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

Please do not forget to "Accept the answer” and “up-vote it” wherever the information provided helps you, this can be beneficial to other community members__.__ It would be greatly appreciated and helpful to others.

Patrick Gebhardt 20

Hello Jeevan,

thank you very much for detailed answer, hope you are well.

I have tried both commands and got the following responses:

PS /home/patrick> Enable-AzFrontDoorCdnProfileMigration -ProfileName "redacted" -ResourceGroupName "redacted" 
The requested operation cannot be executed on the entity in the current state.

PS /home/patrick> Stop-AzFrontDoorCdnProfileMigration -ProfileName "redacted" -ResourceGroupName "redacted"
Provided FrontDoorCdnProfile does not exist.

However, calling the follwoing endpoint shows that (if I understand correctly) FrontDoor already serves traffic:

PS /home/patrick> Get-AzCdnEndpoint -ProfileName redacted -ResourceGroupName redacted

Thank you very much for your further help

Best Regards

Patrick

Anonymous

2025-10-06T17:18:48.6233333+00:00

Hello @Patrick Gebhardt,
Good day.

We have requested some details in a private message. Could you please check and share them in message with us?

Regard's
Jeevan S
Thanmayi Godithi 11,905 Reputation points Microsoft External Staff Moderator

2025-10-10T09:22:23.3866667+00:00

Hello @Patrick Gebhardt,

Our backend team cleaned up invalid data and set the profile to migrating state. Now you can be able to try migrating again and it should succeed.

Let us know if that worked.
Patrick Gebhardt 20 Reputation points

2025-10-13T04:52:58.8+00:00

Hello,

after the invalid data was deleted, the migration with the powershell command was successful!

Thanks for the help and Best Regards

Patrick

1 additional answer

Your answer

Anonymous

2025-09-26T08:07:26.2566667+00:00

Hello @Patrick Gebhardt,
Good day.

Could you please review my comment and let us know if it was helpful? If you need any further assistance, please feel free to reach us.

Regard's
Jeevan S
Anonymous

2025-09-29T04:00:42.6533333+00:00

Hello @Patrick Gebhardt,
Good day.

Just checking in to see if you had a chance to see the previous response by Jeevan Shanigarapu. To help the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer. And, if you have any further questions do let us know.

Regard's
Jeevan S
Patrick Gebhardt 20 Reputation points

2025-10-06T05:07:07.6733333+00:00

Hello Jeevan,

thank you very much for detailed answer, hope you are well.

I have tried both commands and got the following responses:

PS /home/patrick> Enable-AzFrontDoorCdnProfileMigration -ProfileName "redacted" -ResourceGroupName "redacted" The requested operation cannot be executed on the entity in the current state.

PS /home/patrick> Stop-AzFrontDoorCdnProfileMigration -ProfileName "redacted" -ResourceGroupName "redacted" Provided FrontDoorCdnProfile does not exist.

However, calling the follwoing endpoint shows that (if I understand correctly) FrontDoor already serves traffic:

PS /home/patrick> Get-AzCdnEndpoint -ProfileName redacted -ResourceGroupName redacted

Thank you very much for your further help

Best Regards

Patrick
Anonymous

2025-10-06T17:18:48.6233333+00:00

Hello @Patrick Gebhardt,
Good day.

We have requested some details in a private message. Could you please check and share them in message with us?

Regard's
Jeevan S
Thanmayi Godithi 11,905 Reputation points Microsoft External Staff Moderator

2025-10-10T09:22:23.3866667+00:00

Hello @Patrick Gebhardt,

Our backend team cleaned up invalid data and set the profile to migrating state. Now you can be able to try migrating again and it should succeed.

Let us know if that worked.
Patrick Gebhardt 20 Reputation points

2025-10-13T04:52:58.8+00:00

Hello,

after the invalid data was deleted, the migration with the powershell command was successful!

Thanks for the help and Best Regards

Patrick

Answer 1

JimmySalian-2011 45,981 Volunteer Moderator

Hi,

If the resources are locked from the backend and there is no way to unlock, please can you raise a support ticket so someone can have a look at the backend locks - https://azure.microsoft.com/en-ca/support/create-ticket/

Hope this helps.

JS

==

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

0 comments