You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Quickstart - Integrate an Azure storage account with Azure CDN
2
+
title: Quickstart - Integrate an Azure Storage account with Azure CDN
3
3
description: Learn how to use the Azure Content Delivery Network (CDN) to deliver high-bandwidth content by caching blobs from Azure Storage.
4
4
services: cdn
5
5
documentationcenter: ''
@@ -13,135 +13,115 @@ ms.workload: tbd
13
13
ms.tgt_pltfrm: na
14
14
ms.devlang: na
15
15
ms.topic: quickstart
16
-
ms.date: 05/24/2018
16
+
ms.date: 04/30/2020
17
17
ms.author: allensu
18
18
ms.custom: mvc
19
19
20
20
---
21
-
# Quickstart: Integrate an Azure storage account with Azure CDN
22
-
In this quickstart, you enable [Azure Content Delivery Network (CDN)](cdn-overview.md) 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.
21
+
# Quickstart: Integrate an Azure Storage account with Azure CDN
In this quickstart, you enable [Azure Content Delivery Network (CDN)](cdn-overview.md) 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.
25
24
26
-
## Log in to the Azure portal
27
-
Log in to the [Azure portal](https://portal.azure.com) with your Azure account.
25
+
## Prerequisites
28
26
29
-
## Create a storage account
30
-
Use the following procedure to create a new storage account for an Azure subscription. A storage account gives access to Azure Storage services. The storage account represents the highest level
31
-
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](../storage/common/storage-introduction.md).
27
+
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
32
28
33
-
To create a storage account, you must be either the service administrator or a coadministrator for the associated subscription.
29
+
## Sign in to the Azure portal
30
+
31
+
Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
34
32
35
-
You can use several methods to create a storage account, including the Azure portal and PowerShell. This quickstart demonstrates how to use the Azure portal.
33
+
## Create a storage account
36
34
37
-
**To create a storage account for an Azure subscription**
35
+
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](../storage/common/storage-introduction.md).
38
36
39
-
1. In the Azure portal, in the upper left, select **Create a resource**.
37
+
To create a storage account, you must be either the service administrator or a coadministrator for the associated subscription.
40
38
41
-
The **New** pane appears.
39
+
1. In the Azure portal, select **Create a resource** on the upper left. The **New** pane appears.
1. In the **Create storage account pane**, enter the following details:
50
46
51
-
3. In the **Name** box, enter a subdomain name. This entry can contain 3-24 lowercase letters and numbers.
52
-
53
-
This value becomes the host name within the URI 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:
where *<StorageAccountLabel>* refers to the value you entered in the **Name** box.
58
-
59
-
> [!IMPORTANT]
60
-
> The URL label forms the subdomain of the storage account URI and must be unique among all hosted services in Azure.
61
-
62
-
This value is also used as the name of the storage account in the portal or when you're accessing this account programmatically.
47
+
| Setting | Value |
48
+
| --- | --- |
49
+
| Project details > Resource group | Select **Create new** and use the name *CDNQuickstart-rg*. You can also use an existing resource group if you prefer. |
50
+
| 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>*.
51
+
| Instance details > Location | Select an Azure region near you from the drop-down list. |
63
52
64
-
4. For the remainder of the settings, use the values specified in the following table:
53
+
Leave all other details set to the defaults, then select **Review + create**.
65
54
66
-
| Setting | Value |
67
-
| -------- | ----- |
68
-
|**Deployment model**| Use the default value. |
69
-
|**Account kind**| Use the default value. |
70
-
|**Location**| Select **Central US** from the drop-down list. |
71
-
|**Replication**| Use the default value. |
72
-
|**Performance**| Use the default value. |
73
-
|**Secure transfer required**| Use the default value. |
74
-
|**Subscription**| Select an Azure subscription from the drop-down list. |
75
-
|**Resource group**| Select **Create new** and enter *my-resource-group-123* for your resource group name. This name must be globally unique. If it is already in use, you may enter a different name or you can select **Use existing** and select **my-resource-group-123** from the drop-down list. <br />For information about resource groups, see [Azure Resource Manager overview](../azure-resource-manager/management/overview.md#resource-groups).|
76
-
|**Configure virtual networks**| Use the default value. |
77
-
78
-
5. Select **Pin to dashboard** to save the storage account to your dashboard after it is created.
79
-
80
-
6. Select **Create**. Creating the storage account might take several minutes to finish.
55
+
1. 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.
81
56
82
57
## Enable Azure CDN for the storage account
83
58
84
-
You can enable Azure CDN for your storage account directly from your storage account. If you want to specify advanced configuration settings for your CDN endpoint, such as [large file download optimization](cdn-optimization-overview.md#large-file-download), you can instead use the [Azure CDN extension](cdn-create-new-endpoint.md) to create a CDN profile and endpoint.
59
+
1. On the page for your storage account, select **Blob service** > **Azure CDN** from the left menu. The **Azure CDN** page appears.
85
60
86
-
1. Select a storageaccount from the dashboard, then select **Azure CDN** from the left pane. If the **Azure CDN** button is not immediately visible, you can enter CDN in the **Search** box of the left pane to find it.
2. Create a new endpoint by entering the required information specified in the following table:
63
+
1. In the **New endpoint** section, enter the following information:
93
64
94
65
| Setting | Value |
95
66
| -------- | ----- |
96
-
|**CDN profile**| Select **Create new** and enter your profile name, for example, *my-cdn-profile-123*. This name must be globally unique. |
97
-
|**Pricing tier**| Select **Standard Verizon**from the drop-down list. |
98
-
| **CDN endpoint name** | Enter your endpoint hostname, i.e. *my-endpoint-123*. This name must be globally unique. This name is used to access your cached resources at the domain _<endpointname>_.azureedge.net. |
67
+
|**CDN profile**| Select **Create new** and enter your profile name, for example, *cdn-profile-123*. A profile is a collection of endpoints.|
68
+
|**Pricing tier**| Select one of the **Standard**options, such as **Standard Microsoft**. |
69
+
| **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. |
99
70
| **Origin hostname** | By default, a new CDN endpoint uses the hostname of your storage account as the origin server. |
100
71
101
-
3. Select **Create**. After the endpoint is created, it appears in the endpoint list.
72
+
1. Select **Create**. After the endpoint is created, it appears in the endpoint list.
102
73
103
74
104
75
76
+
> [!TIP]
77
+
> If you want to specify advanced configuration settings for your CDN endpoint, such as [large file download optimization](cdn-optimization-overview.md#large-file-download), you can instead use the [Azure CDN extension](cdn-create-new-endpoint.md) to create a CDN profile and endpoint.
78
+
105
79
106
80
## Enable additional CDN features
107
-
From the storage account **Azure CDN** page, select the CDN endpoint from the list to open the CDN endpoint configuration page. From this page, you can enable additional CDN features for your delivery, such as [compression](cdn-improve-performance.md), [query string caching](cdn-query-string.md), and [geo filtering](cdn-restrict-access-by-country.md).
From the storage account **Azure CDN** page, select the CDN endpoint from the list to open the CDN endpoint configuration page.
83
+
84
+
From this page, you can enable additional CDN features for your delivery, such as [compression](cdn-improve-performance.md), [query string caching](cdn-query-string.md), and [geo filtering](cdn-restrict-access-by-country.md).
85
+
111
86
## Enable SAS
112
-
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](cdn-sas-storage-support.md).
87
+
88
+
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](cdn-sas-storage-support.md).
113
89
114
90
## Access CDN content
91
+
115
92
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.
121
98
122
99
## Remove content from Azure CDN
100
+
123
101
If you no longer want to cache an object in Azure CDN, you can take one of the following steps:
124
102
125
-
* Make the container private instead of public. For more information, see [Manage anonymous read access to containers and blobs](../storage/blobs/storage-manage-access-to-resources.md).
126
-
* Disable or delete the CDN endpoint by using the Azure portal.
127
-
* Modify your hosted service to no longer respond to requests for the object.
103
+
- Make the container private instead of public. For more information, see [Manage anonymous read access to containers and blobs](../storage/blobs/storage-manage-access-to-resources.md).
104
+
- Disable or delete the CDN endpoint by using the Azure portal.
105
+
- Modify your hosted service to no longer respond to requests for the object.
128
106
129
107
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](cdn-purge-endpoint.md). 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.
130
108
131
109
## Clean up resources
110
+
132
111
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](#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:
133
112
134
-
1. From the left-hand menu in the Azure portal, select **Resource groups** and then select **my-resource-group-123**.
113
+
1. From the left-hand menu in the Azure portal, select **Resource groups** and then select *CDNQuickstart-rg**.
135
114
136
-
2. On the **Resource group** page, select **Delete resource group**, enter *my-resource-group-123* in the text box, then select **Delete**.
115
+
2. On the **Resource group** page, select **Delete resource group**, enter *CDNQuickstart-rg* in the text box, then select **Delete**.
137
116
138
117
This action will delete the resource group, profile, and endpoint that you created in this quickstart.
139
118
140
119
3. To delete your storage account, select it from the dashboard, then select **Delete** from the top menu.
141
120
142
121
## Next steps
143
-
To learn about adding a custom domain and enable HTTPS on your CDN endpoint, see the following tutorial:
144
122
145
123
> [!div class="nextstepaction"]
146
-
> [Tutorial: Access storage blobs using an Azure CDN custom domain over HTTPS](cdn-storage-custom-domain-https.md)
124
+
> [Create an Azure CDN profile and endpoint](cdn-create-new-endpoint.md)
147
125
126
+
> [!div class="nextstepaction"]
127
+
> [Tutorial: Use CDN to server static content from a web app](cdn-add-to-web-app.md)
0 commit comments