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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.custom: mvc, mode-other
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'll create an Azure Storage account and enable Front Door to cache and accelerate content 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 create an Azure Storage account and enable Front Door to cache and accelerate content from Azure Storage.
17
17
18
18
## Prerequisites
19
19
@@ -63,7 +63,7 @@ A storage account provides access to Azure Storage services. It represents the h
63
63
| Pricing tier | Select **Standard** for content delivery or **Premium** for content delivery with security features. |
64
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
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. |
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 subresource. |
67
67
68
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
@@ -79,7 +79,7 @@ A storage account provides access to Azure Storage services. It represents the h
79
79
> * The endpoint list will only show Front Door and CDN profiles within the same subscription.
80
80
81
81
## Extra features
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).
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 other Azure Front Door features such as the [rules engine](front-door-rules-engine.md) and configure traffic [load balancing](routing-methods.md).
83
83
84
84
For best practices, refer to [Use Azure Front Door with Azure Storage blobs](scenario-storage-blobs.md).
85
85
@@ -119,7 +119,7 @@ If you no longer want to cache an object in Azure Front Door, you can purge the
119
119
120
120
1. Select the Azure Front Door endpoint from the list to open the Azure Front Door endpoint configuration page.
121
121
122
-
1.Click on the **Purge cache** option at the top of the page.
122
+
1.Select on the **Purge cache** option at the top of the page.
123
123
124
124
1. Select the endpoint, domain, and path you want to purge.
0 commit comments