The Azure Content Delivery Network (CDN) is the fundamental building block to scale any HTTP application in Azure. It offers Azure customers a global solution by caching and delivering content close to end users. As a result, instead of hitting origin every single time, user requests get intelligently routed to the best performed CDN edge POP. This significantly increases the performance and user experience. For a current list of CDN node locations, see [Azure CDN Node Locations].
The benefits of using CDN to cache Azure data include:
Existing CDN customers can now use the Azure CDN in the [Azure Management Portal]. The CDN is an add-on feature to your subscription and has a separate [billing plan].
CDN origin is the location from which CDN fetch content and cache at the edge POPs. The integrated Azure origin includes Azure Apps, Cloud Services, Storage and Media services.
Once your origin is set up, it will be available in the origin list when you create a new CDN endpoint.
The configuration created for the endpoint will not immediately be available; it can take up to 60 minutes for the registration to propagate through the CDN network. Users who try to use the CDN domain name immediately may receive status code 400 (Bad Request) until the content is available via the CDN.
You can enable a number of features for your CDN endpoint, such as caching policy, query string caching, etc.
To access cached content on the CDN, use the CDN URL provided in the portal. For example, the address for a cached blob will be similar to the following: http://<CDNNamespace>.vo.msecnd.net/<myPublicContainer>/<BlobName>