Maintain of Azure CDN Endpoint with Akamai Retirement

Hello @Savita Mittal ,

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

I understand that you would like some information about the upcoming retirement of Azure CDN from Akamai, scheduled for October 31.

We got alert on CDN migration for our internal test subscriptions. We didn't get alert on our prod subscription 'Project Vienna Prod - Global AME'. Does this mean we are not required to migrate Prod or its already migrated by CDN team?

Azure and Akamai Technologies Inc have decided not to renew the partnership. As a result, on 31 October 2023, services of Azure CDN Standard from Akamai will no longer be supported. And this is applicable for all subscriptions using Azure CDN Standard from Akamai.

I'm not sure why an email/alert was not received for your prod subscription, but the same migration timeline applies to both of your subscriptions if both of them are using Azure CDN Standard from Akamai.

Are you using Azure CDN Standard from Akamai on your prod subscription? If yes, then maybe you need to create a support request to get details on why the alert was not triggered for this subscription.

Refer: https://azure.microsoft.com/en-us/updates/azure-cdn-will-be-retiring-azure-cdn-standard-from-akamai-on-31-october-2023-transition-to-another-cdn-profile-to-avoid-servi/

Alert email states that Azure CDN Standard from Akamai profiles still active on 31 October 2023 will be migrated by Azure CDN product engineering to another Azure CDN. With this auto migration, will the profiles and endpoints remain same? Is there a change needed from team?

Below are some points that I found while discussing this issue with our Azure CDN Product Group team:

• If a custom domain is used/cnamed to azureedge.net endpoint, then you can refer the below doc for more general guidance for manually migrating between CDN providers: https://video2.skills-academy.com/en-us/azure/cdn/cdn-change-provider
• If you are using CDN endpoints such as xyz.azureedge.net without a custom domain, then manually migrating the CDN endpoint without downtime is not possible because you won't be able to create multiple Azure CDN profiles with the same endpoint name.
• The only way to manually migrate your CDN endpoint will be to delete the old CDN endpoint and reuse it in another CDN provider. The endpoint should be available to re-use within 5 to 10 minutes of its deletion, but you should consider some downtime which is needed for the creation of a new endpoint and updating DNS records. NOTE: It is not possible to rename a CDN endpoint. So, you need to create a fresh endpoint with the required endpoint name as soon as it is deleted from your Akamai CDN profile.
• You can wait until we auto migrate, and that migration is expected to be graceful. With the Nov 1 auto migrate: the profiles and endpoints will remain consistent; the downstream provider will be changed behind the scenes from Akamai to Azure CDN Standard from Verizon. But we still encourage customers to migrate their CDN themselves.

Kindly let us know if the above helps or 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.