We are very excited to extend new CDN capabilities available in the new Azure portal to existing CDN endpoints created from the classic Azure portal. We started a seamless process to migrate your CDN endpoints from the classic Azure portal to the new portal. Subscriptions will be individually migrated in a phased manner over the next few weeks and your service will not be interrupted during this process.

Stage 1

CDN endpoints will be available in both classic and new Azure portal March 2016

Endpoints created from the classic portal will be added to the new portal. They will be placed in a profile named “DefaultProfile” with the Standard SKU and in a resource group named “DefaultResourceGroup.”

New CDN POPs in India, Australia and South America will be enabled by default and CDN zone pricing will be applied.

Stage 2

CDN endpoint will be available only in the new Azure portal April 2016

CDN service in classic Azure portal will be directed to the new Azure portal.

Additional information

CDN capabilities in the new portal

• New CDN POPs and pricing zones in India, Australia and South America
• New SKUs (CDN Standard and CDN Premium) with different feature set
• New CDN features including purge, load etc.
• CDN REST API and Developer tools (.NET SDK, PowerShell, Swagger)

How do I know if my subscription has migrated?

After migration, your CDN endpoints created from the classic portal shall also be accessible from the new Azure portal.

Profile upgrade or downgrade

Currently, we do not support profile upgrade from Standard to Premium. You can create another profile with Premium SKU.

What should I do if I have an issue or question regarding the migration?

You can create a support ticket or add a post to the Azure CDN forum.