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/storage/blobs/storage-blob-static-website.md
+7-14Lines changed: 7 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,22 +76,16 @@ For example, if you change the public access level of the **$web** container fro
76
76
77
77
However, the public access to the primary blob service endpoint `https://contosoblobaccount.blob.core.windows.net/$web/index.html` does change from private to public. Now users can open that file by using either of these two endpoints.
78
78
79
-
## Content Delivery Network (CDN) and Secure Socket Layer (SSL) support
79
+
## Mapping a custom domain to a static website URL
80
80
81
-
To make your static website files available over your custom domain and HTTPS, see [Using the Azure CDN to access blobs with custom domains over HTTPS](storage-https-custom-domain-cdn.md). As a part of this process, you need to point your CDN to the primary *static website* endpoint as opposed to the primary *blob service* endpoint. You might need to wait a few minutes before your content is visible as the CDN configuration is not immediately executed.
81
+
You can make your static website available via a custom domain.
82
82
83
-
When you update your static website, be sure to clear cached content on the CDN edge servers by purging the CDN endpoint. For more information, see [Purge an Azure CDN endpoint](../../cdn/cdn-purge-endpoint.md).
83
+
It's easier to enable HTTP access for your custom domain, because Azure Storage natively supports it. To enable HTTPS, you'll have to use Azure CDN because Azure Storage does not yet natively support HTTPS with custom domains. see [Map a custom domain to an Azure Blob Storage endpoint](storage-custom-domain-name.md) for step-by-step guidance.
84
84
85
-
> [!NOTE]
86
-
> HTTPS is supported natively through the account web endpoint, so the web endpoint is accessible via both HTTP and HTTPS. However, if the storage account is configured to require secure transfer over HTTPS, then users must use the HTTPS endpoint. For more information, see [Require secure transfer in Azure Storage](../common/storage-require-secure-transfer.md).
87
-
>
88
-
> The use of custom domains over HTTPS requires the use of Azure CDN at this time.
89
-
90
-
## Custom domain names
91
-
92
-
You can make your static website available via a custom domain. To learn more, see [configure a custom domain name for your Azure Storage account](storage-custom-domain-name.md).
85
+
If the storage account is configured to [require secure transfer](../common/storage-require-secure-transfer.md) over HTTPS, then users must use the HTTPS endpoint.
93
86
94
-
For an in-depth look at hosting your domain on Azure, see [Host your domain in Azure DNS](../../dns/dns-delegate-domain-azure-dns.md).
87
+
> [!TIP]
88
+
> Consider hosting your domain on Azure. For more information, see [Host your domain in Azure DNS](../../dns/dns-delegate-domain-azure-dns.md).
95
89
96
90
## Pricing
97
91
@@ -106,8 +100,7 @@ To enable metrics on your static website pages, see [Enable metrics on static we
106
100
## Next steps
107
101
108
102
*[Host a static website in Azure Storage](storage-blob-static-website-how-to.md)
109
-
*[Use the Azure CDN to access blobs with custom domains over HTTPS](storage-https-custom-domain-cdn.md)
110
-
*[Configure a custom domain name for your blob or web endpoint](storage-custom-domain-name.md)
103
+
*[Map a custom domain to an Azure Blob Storage endpoint](storage-custom-domain-name.md)
Copy file name to clipboardExpand all lines: articles/storage/blobs/storage-custom-domain-name.md
+18-12Lines changed: 18 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Map a custom domain to a Blob Storage or web endpoint in an Azure s
5
5
author: normesta
6
6
ms.service: storage
7
7
ms.topic: conceptual
8
-
ms.date: 01/14/2020
8
+
ms.date: 01/23/2020
9
9
ms.author: normesta
10
10
ms.reviewer: dineshm
11
11
ms.subservice: blobs
@@ -15,13 +15,17 @@ ms.subservice: blobs
15
15
16
16
You can map a custom domain to a blob service endpoint or a [static website](storage-blob-static-website.md) endpoint.
17
17
18
+
[!NOTE] This mapping works only for subdomains (for example: `www.contoso.com`). If you want your web endpoint to be available on the root domain (for example: `contoso.com`), see the [Map a custom domain with HTTPS enabled](#enable-https) section of this article. The step within that section for enabling HTTPS is optional.
19
+
18
20
<aid="enable-http" />
19
21
20
22
## Map a custom domain with only HTTP enabled
21
23
22
-
This approach is easier, but enables users to access your site only by using HTTP (not HTTPS), and only with subdomains (for example: `www.contoso.com`).
24
+
This approach is easier, but enables only HTTP access.
25
+
26
+
> [!NOTE] If the storage account is configured to [require secure transfer](../common/storage-require-secure-transfer.md) over HTTPS, then users must use the HTTPS endpoint.
23
27
24
-
If you want to users to access your site by using HTTPS, or you want have your web endpoint to be available on the root domain (for example: `contoso.com`), then see the [Map a custom domain with HTTPS enabled](#enable-https) section of this article.
28
+
To enable HTTPS access, see the [Map a custom domain with HTTPS enabled](#enable-https) section of this article.
25
29
26
30
<aid="map-a-domain" />
27
31
@@ -289,29 +293,31 @@ To remove a custom domain registration, use the [Set-AzStorageAccount](/powershe
289
293
290
294
## Map a custom domain with HTTPS enabled
291
295
292
-
This approach involves more steps because you'll have to map your custom domain by using [Azure CDN](../../cdn/cdn-overview.md), but it enables users to access your site by using the HTTPS protocol.
296
+
This approach involves more steps, but it enables HTTPS access.
293
297
294
-
If you don't need users to access your site by using HTTPS, see the [Map a custom domain with only HTTP enabled](#enable-http) section of this article.
298
+
If you don't need users to access your blob or web content by using HTTPS, then see the [Map a custom domain with only HTTP enabled](#enable-http) section of this article.
295
299
296
-
To enable HTTPS for your custom Blob storage endpoint, do the following:
300
+
To map a custom domain and enable HTTPS access, do the following:
297
301
298
-
1. Enable Azure CDN on your blob or web endpoint.
302
+
1. Enable [Azure CDN](../../cdn/cdn-overview.md) on your blob or web endpoint.
299
303
300
-
To enable Azure CDN for your blob endpoint, see [Integrate an Azure storage account with Azure CDN](../../cdn/cdn-create-a-storage-account-with-cdn.md).
304
+
For a Blob Storage endpoint, see [Integrate an Azure storage account with Azure CDN](../../cdn/cdn-create-a-storage-account-with-cdn.md).
301
305
302
-
To enable Azure CDN for your web endpoint (static website), see [Integrate a static website with Azure CDN](storage-blob-static-website-cdn.md).
306
+
For a static website endpoint, see [Integrate a static website with Azure CDN](storage-blob-static-website-cdn.md).
303
307
304
308
2.[Map Azure CDN content to a custom domain](../../cdn/cdn-map-content-to-custom-domain.md).
305
309
306
310
3.[Enable HTTPS on an Azure CDN custom domain](../../cdn/cdn-custom-ssl.md).
307
311
312
+
> [!NOTE] When you update your static website, be sure to clear cached content on the CDN edge servers by purging the CDN endpoint. For more information, see [Purge an Azure CDN endpoint](../../cdn/cdn-purge-endpoint.md).
313
+
308
314
4. (Optional) Review the following guidance:
309
315
310
-
*If you're using shared access signatures (SAS) tokens with Azure CDN, review [best practice guidance](https://docs.microsoft.com/azure/cdn/cdn-storage-custom-domain-https#shared-access-signatures) for using them.
316
+
*[Shared access signature (SAS) tokens with Azure CDN](https://docs.microsoft.com/azure/cdn/cdn-storage-custom-domain-https#shared-access-signatures).
311
317
312
-
*If using Azure CDN, learn how to [redirect HTTP traffic to HTTPS](https://docs.microsoft.com/azure/cdn/cdn-storage-custom-domain-https#http-to-https-redirection).
318
+
*[HTTP-to-HTTPS redirection with Azure CDN](https://docs.microsoft.com/azure/cdn/cdn-storage-custom-domain-https#http-to-https-redirection).
313
319
314
-
*If using Azure CDN, learn about [pricing and billing](https://docs.microsoft.com/azure/cdn/cdn-storage-custom-domain-https#http-to-https-redirection).
320
+
*[Pricing and billing when using Blob Storage with Azure CDN](https://docs.microsoft.com/azure/cdn/cdn-storage-custom-domain-https#http-to-https-redirection).
0 commit comments