Quickstart: Integrate an Azure Storage account with Azure CDN
In this quickstart, you enable Azure Content Delivery Network (CDN) to cache content from Azure Storage. Azure CDN offers developers a global solution for delivering high-bandwidth content. It can cache blobs and static content of compute instances at physical nodes in the United States, Europe, Asia, Australia, and South America.
- An Azure account with an active subscription. Create an account for free.
Sign in to the Azure portal
Sign in to the Azure portal with your Azure account.
Create a storage account
A storage account gives access to Azure Storage services. The storage account represents the highest level of the namespace for accessing each of the Azure Storage service components: Azure Blob, Queue, and Table storage. For more information, see Introduction to Microsoft Azure Storage.
To create a storage account, you must be either the service administrator or a coadministrator for the associated subscription.
In the Azure portal, select Create a resource on the upper left. The New pane appears.
Search for Storage account and select Storage account - blob, file, table, queue from the drop-down list. Then select Create:
In the Create storage account pane, enter the following details:
Setting Value Project details > Resource group Select Create new and use the name CDNQuickstart-rg. You can also use an existing resource group if you prefer. Instance details > Storage account name Enter a name for the account using 3-24 lowercase letters and numbers only. The name must be unique across Azure, and becomes the host name in the URL that's used to address blob, queue, or table resources for the subscription. To address a container resource in Blob storage, use a URI in the following format: http://<storageaccountname>.blob.core.windows.net/<container-name>. Instance details > Location Select an Azure region near you from the drop-down list.
Leave all other details set to the defaults, then select Review + create.
Creating the storage account might take several minutes to complete. Once creation is complete, select Go to resource to open the storage account's page for the next step.
Enable Azure CDN for the storage account
On the page for your storage account, select Blob service > Azure CDN from the left menu. The Azure CDN page appears.
In the New endpoint section, enter the following information:
Setting Value CDN profile Select Create new and enter your profile name, for example, cdn-profile-123. A profile is a collection of endpoints. Pricing tier Select one of the Standard options, such as Standard Microsoft. CDN endpoint name Enter your endpoint hostname, such as cdn-endpoint-123. This name must be globally unique across Azure because it's to access your cached resources at the URL <endpoint-name>.azureedge.net. Origin hostname By default, a new CDN endpoint uses the hostname of your storage account as the origin server.
Select Create. After the endpoint is created, it appears in the endpoint list.
If you want to specify advanced configuration settings for your CDN endpoint, such as large file download optimization, you can instead use the Azure CDN extension to create a CDN profile and endpoint.
Enable additional CDN features
From the storage account Azure CDN page, select the CDN endpoint from the list to open the CDN endpoint configuration page.
If you want to grant limited access to private storage containers, you can use the Shared Access Signature (SAS) feature of your Azure Storage account. A SAS is a URI that grants restricted access rights to your Azure Storage resources without exposing your account key. For more information, see Using Azure CDN with SAS.
Access CDN content
To access cached content on the CDN, use the CDN URL provided in the portal. The address for a cached blob has the following format:
After you enable Azure CDN access to a storage account, all publicly available objects are eligible for CDN POP caching. If you modify an object that's currently cached in the CDN, the new content will not be available via Azure CDN until Azure CDN refreshes its content after the time-to-live period for the cached content expires.
Remove content from Azure CDN
If you no longer want to cache an object in Azure CDN, you can take one of the following steps:
- Make the container private instead of public. For more information, see Manage anonymous read access to containers and blobs.
- Disable or delete the CDN endpoint by using the Azure portal.
- Modify your hosted service to no longer respond to requests for the object.
An object that's already cached in Azure CDN remains cached until the time-to-live period for the object expires or until the endpoint is purged. When the time-to-live period expires, Azure CDN determines whether the CDN endpoint is still valid and the object is still anonymously accessible. If they are not, the object will no longer be cached.
Clean up resources
In the preceding steps, you created a CDN profile and an endpoint in a resource group. Save these resources if you want to go to Next steps and learn how to add a custom domain to your endpoint. However, if you don't expect to use these resources in the future, you can delete them by deleting the resource group, thus avoiding additional charges:
From the left-hand menu in the Azure portal, select Resource groups and then select CDNQuickstart-rg*.
On the Resource group page, select Delete resource group, enter CDNQuickstart-rg in the text box, then select Delete.
This action will delete the resource group, profile, and endpoint that you created in this quickstart.
To delete your storage account, select it from the dashboard, then select Delete from the top menu.