Azure Front Door Classic Migration

Question

Our solution have some static pages currently running on the Azure Front Door and CDN Profile, classic version.

From Azure document, it seems straightforward steps to migrate from the classic version to standard / premium version.

However, we have planned to utilize the migrated Front Door perform routing the web services, but not just limited to the static pages.

Since the new standard / premium tier is created implicitly via migration, but not created via usual flow, will it provide the full features as its suppose to be.

Answer 1

Hello John Wong Yek Hon

Greetings!
I understand that you are looking to migrate classic to Standard/premium.

When migrating from the classic version of Azure Front Door to the Standard or Premium tier, a new instance is automatically created. This new instance should offer all the features associated with those tiers.

If you migrate directly from classic to standard, you will encounter some downtime issues. We suggest deploying the standard or premium tier and configuring the endpoint's origin groups before migration. Additionally, you need to map DNS records with the new endpoint domain name.

Afterward, add one of your origins and check the functionality. If everything is okay, you can migrate 50% of your existing resources to the new standard tier. If all is well, you can migrate 100% of your backend to the standard tier. Once everything is functioning properly, you can remove the classic version. If you follow the steps, you will face minimal down time 

Reference Doc: 

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

https://learn.microsoft.com/en-us/azure/cdn/migrate-tier

NOTE: The Standard and Premium tiers offer additional features not available in the classic version, including enhanced routing capabilities, Web Application Firewall (WAF) integration, and more advanced health probes. After migration, please ensure these features are enabled and configured according to your requirements.

Additionally check the document: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-cdn-comparison

However, we have planned to utilize the migrated Front Door perform routing the web services, but not just limited to the static pages.

 Ans. Not only for static pages; it will also work if you want to use new services.

Since the new standard / premium tier is created implicitly via migration, but not created via usual flow, will it provide the full features as it's supposed to be.

Ans: If you want to use the new service, you can configure a new endpoint and start using it.

---

I hope this has been helpful!

If above is unclear and/or you are unsure about something add a comment below Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.