Azure Front Door - Showing "This profile cannot be edited during migration"

Dhruval Dave 0 Reputation points
2024-01-30T07:15:17.0466667+00:00

Hi Team, I have performed an Azure Front Door migration activity where I have migrated my Classic Azure Front Door to the Premium Version. After performing all the steps, It is still showing me a warning "This profile cannot be edited during migration" and its operational state is "Migrating" for Old and New Front Door profiles. If someone can please help me how change the status of my Azure Front Door to a completely transformed status would be a great help. Thank You

Azure Front Door
Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
546 questions
{count} votes

1 answer

Sort by: Most helpful
  1. GitaraniSharma-MSFT 45,501 Reputation points Microsoft Employee
    2024-01-30T12:32:09.7933333+00:00

    Hello @Dhruval Dave ,

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

    I understand that you've performed an Azure Front Door migration activity where you tried to migrate your Classic Azure Front Door to the Premium Version and after performing all the steps, it is stuck at operational state "Migrating" for Old and New Front Door profiles and showing a warning "This profile cannot be edited during migration".

    As you mentioned that you've been waiting for the last 2 weeks and the state has not changed, it looks like there was some validation issues or internal error in the backend which got stuck and is not moving forward.

    So, you can either try to finish/commit the migration using PowerShell command or abort the migration now and attempt it later.

    To finish the migration, you could run the below PowerShell command:

    Enable-AzFrontDoorCdnProfileMigration -ProfileName myAzureFrontDoor -ResourceGroupName myAFDResourceGroup
    

    The above command will help commit the migrated Azure Front Door Premium profile.

    NOTE: Make sure you add the new profile name in the above command.

    Refer: https://learn.microsoft.com/en-us/azure/frontdoor/migrate-tier-powershell?tabs=without-waf-byoc%2Cmigrate-profile#migrate

    https://learn.microsoft.com/en-us/powershell/module/az.cdn/enable-azfrontdoorcdnprofilemigration?view=azps-11.2.0

    If you decided you no longer want to move forward with the migration process, you can select Abort migration. Aborting the migration deletes the new Front Door profile that was created. The Azure Front Door (classic) profile remains active, and you can continue to use it. Any WAF policy copies need to be manually deleted.

    Refer: https://learn.microsoft.com/en-us/azure/frontdoor/tier-migration#migrate

    If the migration command fails or you would like to abort the migration, you could run the below PowerShell command:

    Stop-AzFrontDoorCdnProfileMigration -ProfileName myAzureFrontDoor -ResourceGroupName myAFDResourceGroup
    

    The above command will abort classic CDN migrate to AFDx. Your new Front Door Profile will be deleted, and your existing profile will remain active. WAF policies will not be deleted.

    NOTE: Make sure you add the new profile name in the above command.

    Refer: https://learn.microsoft.com/en-us/azure/frontdoor/migrate-tier-powershell?tabs=without-waf-byoc%2Cabort-migration#migrate

    https://learn.microsoft.com/en-us/powershell/module/az.cdn/stop-azfrontdoorcdnprofilemigration?view=azps-11.2.0

    Once the migration is aborted, you can validate the prerequisites and compatibility of your Azure Front Door Classic profile and try the migration at a later time.

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


    Please don’t forget to "Accept the answer" wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments