In this article I will show you how does the Azure CDN really works and what you should do in case your CDN Endpoint stopped after re-enabling your Azure Subscription or remove the spending limit for the current billing period.
The Azure Content Delivery Network (CDN) is a service that allows you to send audio, images, and other static files faster and more reliably to customers across the globe.
You can check out the article about how to improve your WebApp performance using Azure CDN… Azure uses some third party providers to enable Azure CDN.
Let´s review the following scenario, let´s assume you are using an MSDN / Azure Pass / or any credit limited Azure Subscription.
When you reach your credit limit, Azure will automatically shut down your services until you either remove your spending limit for the current billing period or you change for another Subscription model like PAYG.
At this stage Azure will stop all your services including Azure CDN endpoint provided from Verizon, the endpoint from Verizon side will be deleted; so you need to go to the CDN Profile and manually start the CDN endpoint.
Azure CDN Endpoint stopped:
When you restart the endpoint in Azure portal, the endpoint from Verizon will get re-created, Verizon CDN will take about 90 min to be available. See more at:
The endpoint will not immediately be available for use, as it takes time for the registration to propagate through the CDN.
For Azure CDN from Akamai profiles, propagation will usually complete within one minute. For Azure CDN from Verizon profiles, propagation will usually complete within 90 minutes, but in some cases can take longer.
In case you´re hosting a critical application it is highly recommended to take care about the CDN propagation and needless to mention have a High Availability scenario.
If you want to get a detailed configuration and best practices on how to improve your WebApp performance using Azure CDN check this case: How to improve your WebApp performance using Azure CDN