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
Copy file name to clipboardExpand all lines: articles/frontdoor/integrate-storage-account.md
+51-40Lines changed: 51 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,14 +6,14 @@ services: frontdoor
6
6
author: duongau
7
7
ms.service: azure-frontdoor
8
8
ms.topic: how-to
9
-
ms.date: 08/22/2023
9
+
ms.date: 11/13/2024
10
10
ms.author: duau
11
11
ms.custom: mvc, mode-other
12
12
---
13
13
14
14
# Integrate an Azure Storage account with Azure Front Door
15
15
16
-
Azure Front Door can be used to deliver high-bandwidth content by caching blobs from Azure Storage. In this article, you create an Azure Storage account and then enable Front Door to cache and accelerate contents from Azure Storage.
16
+
Azure Front Door can be used to deliver high-bandwidth content by caching blobs from Azure Storage. In this article, you'll create an Azure Storage account and enable Front Door to cache and accelerate content from Azure Storage.
17
17
18
18
## Prerequisites
19
19
@@ -25,105 +25,116 @@ Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
25
25
26
26
## Create a storage account
27
27
28
-
A storage account gives access to the 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).
28
+
A storage account provides access to Azure Storage services. It represents the highest level of the namespace for accessing each Azure Storage service component: Azure Blob, Queue, and Table storage. For more information, see [Introduction to Microsoft Azure Storage](../storage/common/storage-introduction.md).
29
29
30
30
1. In the Azure portal, select **+ Create a resource** in the upper left corner. The **Create a resource** pane appears.
31
31
32
32
1. On the **Create a resource** page, search for **Storage account** and select **Storage account** from the list. Then select **Create**.
33
33
34
-
:::image type="content" source="./media/integrate-storage-account/create-new-storage-account.png" alt-text="Screenshot of create a storage account.":::
34
+
:::image type="content" source="./media/integrate-storage-account/create-new-storage-account.png" alt-text="Screenshot of creating a storage account.":::
35
35
36
36
1. On the **Create a storage account** page, enter or select the following information for the new storage account:
37
37
38
38
| Setting | Value |
39
39
| --- | --- |
40
-
| Resource group | Select **Create new** and enter the name **AFDResourceGroup**. You may also select an existing resource group. |
41
-
| 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>*.
40
+
| Resource group | Select **Create new** and enter the name **AFDResourceGroup**. You can also select an existing resource group. |
41
+
| 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 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>*.|
42
42
| Region | Select an Azure region closest to you from the drop-down list. |
43
43
44
44
Leave all other settings as default. Select the **Review** tab, select **Create**, and then select **Review + Create**.
45
45
46
-
1. The creation of the storage account may take a few minutes to complete. Once creation is complete, select **Go to resource** to go to the new storage account resource.
46
+
1. The creation of the storage account can take a few minutes to complete. Once creation is complete, select **Go to resource** to go to the new storage account resource.
47
47
48
48
## Enable Azure Front Door CDN for the storage account
49
49
50
-
1. From the storage account resource, select **Front Door and CDN**from under **Security + networking**on the left side menu pane.
50
+
1. From the storage account resource, select **Front Door and CDN** under **Security + networking**in the left menu.
51
51
52
-
:::image type="content" source="./media/integrate-storage-account/storage-endpoint-configuration.png" alt-text="Screenshot of create an AFD endpoint.":::
53
-
52
+
:::image type="content" source="./media/integrate-storage-account/storage-endpoint-configuration.png" alt-text="Screenshot of creating an AFD endpoint.":::
53
+
54
54
1. In the **New endpoint** section, enter the following information:
55
55
56
56
| Setting | Value |
57
57
| -------- | ----- |
58
58
| Service type | Select **Azure Front Door**. |
59
-
| Create new/use existing profile |You can create a new Front Door profile or select an existing one. |
60
-
| Profile name | Enter a name for the Front Door profile. You have a list of available Front Door profiles if you selected **Use existing**.|
59
+
| Create new/use existing profile |Choose to create a new Front Door profile or select an existing one. |
60
+
| Profile name | Enter a name for the Front Door profile. If you selected **Use existing**, choose from the available profiles. |
61
61
| Endpoint name | Enter your endpoint hostname, such as *contoso1234*. This name is used to access your cached resources at the URL _<endpoint-name + hash value>_.z01.azurefd.net. |
62
62
| Origin hostname | By default, a new Front Door endpoint uses the hostname of your storage account as the origin server. |
63
-
| Pricing tier | Select **Standard**if you want to do content delivery or select **Premium**if you want to do content delivery and use security features. |
64
-
| Caching |*Optional* - Toggle on if you want to [enable caching](front-door-caching.md) for your static content. Choose an appropriate query string behavior. Enable compression if required.|
65
-
| WAF |*Optional* - Toggle on if you want to protect your endpoint from common vulnerabilities, malicious actor and bots with [Web Application Firewall](web-application-firewall.md). You can use an existing policy from the WAF policy dropdown or create a new one. |
66
-
| Private link |*Optional* - Toggle on if you want to keep your storage account private that is, not exposed to public internet. Select the region that is the same region as your storage account or closest to your origin. Select target sub resource as **blob**. |
63
+
| Pricing tier | Select **Standard**for content delivery or **Premium**for content delivery with security features. |
64
+
| Caching |*Optional* - Toggle on to [enable caching](front-door-caching.md) for your static content. Choose an appropriate query string behavior and enable compression if needed. |
65
+
| WAF |*Optional* - Toggle on to protect your endpoint from vulnerabilities, malicious actors, and bots with [Web Application Firewall](web-application-firewall.md). Use an existing policy from the WAF policy dropdown or create a new one. |
66
+
| Private link |*Optional* - Toggle on to keep your storage account private, not exposed to the public internet. Select the region that matches your storage account or is closest to your origin. Choose **blob** as the target sub-resource. |
67
67
68
-
:::image type="content" source="./media/integrate-storage-account/security-settings.png" alt-text="Screenshot of the caching, WAF and private link settings for an endpoint.":::
68
+
:::image type="content" source="./media/integrate-storage-account/security-settings.png" alt-text="Screenshot of the caching, WAF, and private link settings for an endpoint.":::
69
69
70
70
> [!NOTE]
71
-
> * With Standard tier, you can only use custom rules with WAF. To deploy managed rules and bot protection, choose Premium tier. For detailed comparison, see [Azure Front Door tier comparison](./standard-premium/tier-comparison.md).
72
-
> * Private Link feature is **only** available with Premium tier.
71
+
> * With the Standard tier, you can only use custom rules with WAF. To deploy managed rules and bot protection, choose the Premium tier. For a detailed comparison, see [Azure Front Door tier comparison](./standard-premium/tier-comparison.md).
72
+
> *The Private Link feature is **only** available with the Premium tier.
73
73
74
-
1. Select **Create** to create the new endpoint. After the endpoint is created, it appears in the endpoint list.
74
+
1. Select **Create** to create the new endpoint. After creation, it appears in the endpoint list.
75
75
76
-
:::image type="content" source="./media/integrate-storage-account/endpoint-created.png" alt-text="Screenshot of new Front Door endpoint created from Storage account.":::
76
+
:::image type="content" source="./media/integrate-storage-account/endpoint-created.png" alt-text="Screenshot of a new Front Door endpoint created from a Storage account.":::
77
77
78
78
> [!NOTE]
79
-
> * The endpoint list will only show Front Door and CDN profiles within the same subscription.
80
-
79
+
> * The endpoint list will only show Front Door and CDN profiles within the same subscription.
81
80
82
81
## Extra features
83
-
84
-
From the storage account **Front Door and CDN** page, select the endpoint from the list to open the Front Door endpoint configuration page. You can enable more Front Door features for your delivery, such as [rules engine](front-door-rules-engine.md) and configure how traffic gets [load balanced](routing-methods.md).
82
+
From the storage account **Front Door and CDN** page, select the endpoint from the list to open the Front Door endpoint configuration page. Here, you can enable additional Front Door features such as the [rules engine](front-door-rules-engine.md) and configure traffic [load balancing](routing-methods.md).
85
83
86
84
For best practices, refer to [Use Azure Front Door with Azure Storage blobs](scenario-storage-blobs.md).
87
85
88
86
## Enable SAS
89
87
90
-
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.
88
+
To grant limited access to private storage containers, 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.
91
89
92
90
## Access CDN content
93
91
94
-
To access cached content with Azure Front Door, use the Front Door URL provided in the portal. The address for a cached blob has the following format:
92
+
To access cached content with Azure Front Door, use the Front Door URL provided in the portal. The address for a cached blob follows this format:
> After you enable Azure Front Door access to a storage account, all publicly available objects are eligible for Front Door POP (Point-of-presence) caching. If you modify an object that is currently cached in Front Door, the new content won't be available through Azure Front Door until Front Door refreshes its content after the time-to-live period for the cached content expires.
97
+
> After enabling Azure Front Door access to a storage account, all publicly available objects are eligible for Front Door POP (Point-of-presence) caching. If you modify an object that is currently cached in Front Door, the new content won't be available until Front Door refreshes its content after the time-to-live period expires.
100
98
101
99
## Add a custom domain
100
+
## Add a custom domain
101
+
102
+
Using a custom domain with Azure Front Door allows your own domain name to be visible in end-user requests, which can enhance customer convenience and support branding efforts.
103
+
104
+
To add a custom domain:
102
105
103
-
When you use Azure Front Door for content delivery, a custom domain is necessary if you would like your own domain name to be visible in your end-user requests. Having a visible domain name can be convenient for your customers and useful for branding purposes.
106
+
1. Navigate to the storage account *Front Door and CDN** page.
104
107
105
-
From the storage account **Front Door and CDN** page, select **View custom domains** for the Front Door endpoint. On the domains page, you can add a new custom domain to access your storage account. For more information, see [Configure a custom domain with Azure Front Door](./standard-premium/how-to-add-custom-domain.md).
108
+
1. Select **View custom domains** for the Azure Front Door endpoint.
106
109
107
-
## Purge cached content from Front Door
110
+
1. On the domains page, add a new custom domain to access your storage account.
108
111
109
-
If you no longer want to cache an object in Azure Front Door, you can purge the cached content.
112
+
For detailed instructions, see [Configure a custom domain with Azure Front Door](./standard-premium/how-to-add-custom-domain.md).
110
113
111
-
From the storage account **Front Door and CDN** page, select the Front Door endpoint from the list to open the Front Door endpoint configuration page. Select **Purge cache** option at the top of the page and then select the endpoint, domain, and path to purge.
114
+
## Purge cached content from Azure Front Door
115
+
116
+
If you no longer want to cache an object in Azure Front Door, you can purge the cached content.
117
+
118
+
1. Navigate to the storage account **Front Door and CDN** page.
119
+
120
+
1. Select the Azure Front Door endpoint from the list to open the Azure Front Door endpoint configuration page.
121
+
122
+
1. Click on the **Purge cache** option at the top of the page.
123
+
124
+
1. Select the endpoint, domain, and path you want to purge.
112
125
113
126
> [!NOTE]
114
-
> An object that's already cached in Azure Front Door remains cached until the time-to-live period for the object expires or until the endpoint is purged.
127
+
> An object already cached in Azure Front Door will remain cached until the time-to-live period expires or until you purge the endpoint.
115
128
116
129
## Clean up resources
117
130
118
-
In the preceding steps, you created an Azure Front Door profile and an endpoint in a resource group. However, if you don't expect to use these resources in the future, you can delete them by deleting the resource group to avoid any charges.
119
-
120
-
1. From the left-hand menu in the Azure portal, select **Resource groups** and then select *AFDResourceGroup**.
131
+
In the preceding steps, you created an Azure Front Door profile and an endpoint in a resource group. If you no longer need these resources, you can delete them to avoid incurring charges.
121
132
122
-
2. On the **Resource group** page, select **Delete resource group**, enter *AFDResourceGroup* in the text box, then select **Delete**.
133
+
1. In the Azure portal, select **Resource groups** from the left-hand menu, then select **AFDResourceGroup**.
123
134
124
-
This action deletes the resource group, profile, and endpoint that you created in this quickstart.
135
+
1. On the **Resource group** page, select **Delete resource group**. Enter **AFDResourceGroup** in the text box, then select **Delete**. This action deletes the resource group, profile, and endpoint created in this guide.
125
136
126
-
3. To delete your storage account, select it from the dashboard, then select **Delete** from the top menu.
137
+
1. To delete your storage account, select the storage account from the dashboard, then select **Delete** from the top menu.
0 commit comments