Skip to content

Commit c7d966c

Browse files
Merge pull request #99150 from DennisLee-DennisLee/v-dele-1645361-011
1645361 portal-nav: Updated articles/cdn/cdn-custom-ssl.md.
2 parents 48ab178 + 0240c72 commit c7d966c

File tree

2 files changed

+17
-13
lines changed

2 files changed

+17
-13
lines changed

articles/cdn/cdn-custom-ssl.md

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ In this tutorial, you learn how to:
4747

4848
Before you can complete the steps in this tutorial, you must first create a CDN profile and at least one CDN endpoint. For more information, see [Quickstart: Create an Azure CDN profile and endpoint](cdn-create-new-endpoint.md).
4949

50-
In addition, you must associate an Azure CDN custom domain on your CDN endpoint. For more information, see [Tutorial: Add a custom domain to your Azure CDN endpoint](cdn-map-content-to-custom-domain.md)
50+
In addition, you must associate an Azure CDN custom domain on your CDN endpoint. For more information, see [Tutorial: Add a custom domain to your Azure CDN endpoint](cdn-map-content-to-custom-domain.md).
5151

5252
> [!IMPORTANT]
5353
> CDN-managed certificates are not available for root or apex domains. If your Azure CDN custom domain is a root or apex domain, you must use the Bring your own certificate feature.
@@ -65,27 +65,29 @@ When you use a CDN-managed certificate, the HTTPS feature can be turned on with
6565

6666
To enable HTTPS on a custom domain, follow these steps:
6767

68-
1. In the [Azure portal](https://portal.azure.com), browse to your **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Akamai**, **Azure CDN Standard from Verizon** or **Azure CDN Premium from Verizon** profile.
68+
1. Go to the [Azure portal](https://portal.azure.com) to find a certificate managed by your Azure CDN. Search for and select **CDN profiles**.
6969

70-
2. In the list of CDN endpoints, select the endpoint containing your custom domain.
70+
2. Choose your **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Akamai**, **Azure CDN Standard from Verizon**, or **Azure CDN Premium from Verizon** profile.
71+
72+
3. In the list of CDN endpoints, select the endpoint containing your custom domain.
7173

7274
![Endpoints list](./media/cdn-custom-ssl/cdn-select-custom-domain-endpoint.png)
7375

7476
The **Endpoint** page appears.
7577

76-
3. In the list of custom domains, select the custom domain for which you want to enable HTTPS.
78+
4. In the list of custom domains, select the custom domain for which you want to enable HTTPS.
7779

7880
![Custom domains list](./media/cdn-custom-ssl/cdn-custom-domain.png)
7981

8082
The **Custom domain** page appears.
8183

82-
4. Under Certificate management type, select **CDN managed**.
84+
5. Under Certificate management type, select **CDN managed**.
8385

84-
5. Select **On** to enable HTTPS.
86+
6. Select **On** to enable HTTPS.
8587

8688
![Custom domain HTTPS status](./media/cdn-custom-ssl/cdn-select-cdn-managed-certificate.png)
8789

88-
6. Proceed to [Validate the domain](#validate-the-domain).
90+
7. Proceed to [Validate the domain](#validate-the-domain).
8991

9092

9193
# [Option 2: Enable HTTPS with your own certificate](#tab/option-2-enable-https-with-your-own-certificate)
@@ -201,7 +203,7 @@ webmaster@<your-domain-name.com>
201203
hostmaster@<your-domain-name.com>
202204
postmaster@<your-domain-name.com>
203205

204-
You should receive an email in a few minutes, similar to the following example, asking you to approve the request. If you are using a spam filter, add [email protected] to its whitelist. If you don't receive an email within 24 hours, contact Microsoft support.
206+
You should receive an email in a few minutes, similar to the following example, asking you to approve the request. If you are using a spam filter, add [email protected] to its allow list. If you don't receive an email within 24 hours, contact Microsoft support.
205207

206208
![Domain validation email](./media/cdn-custom-ssl/domain-validation-email.png)
207209

@@ -257,15 +259,17 @@ In the preceding steps, you enabled the HTTPS protocol on your custom domain. If
257259

258260
### Disable the HTTPS feature
259261

260-
1. In the [Azure portal](https://portal.azure.com), browse to your **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Verizon** or **Azure CDN Premium from Verizon** profile.
262+
1. In the [Azure portal](https://portal.azure.com), search for and select **CDN profiles**.
263+
264+
2. Choose your **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Verizon**, or **Azure CDN Premium from Verizon** profile.
261265

262-
2. In the list of endpoints, click the endpoint containing your custom domain.
266+
3. In the list of endpoints, pick the endpoint containing your custom domain.
263267

264-
3. Click the custom domain for which you want to disable HTTPS.
268+
4. Choose the custom domain for which you want to disable HTTPS.
265269

266270
![Custom domains list](./media/cdn-custom-ssl/cdn-custom-domain-HTTPS-enabled.png)
267271

268-
4. Click **Off** to disable HTTPS, then click **Apply**.
272+
5. Choose **Off** to disable HTTPS, then select **Apply**.
269273

270274
![Custom HTTPS dialog](./media/cdn-custom-ssl/cdn-disable-custom-ssl.png)
271275

@@ -313,7 +317,7 @@ The following table shows the operation progress that occurs when you disable HT
313317

314318
7. *How do cert renewals work with Bring Your Own Certificate?*
315319

316-
To ensure a newer certificate is deployed to PoP infrastructure, simply upload your new certificate to Azure KeyVault, and then in your SSL settings on Azure CDN, choose the newest certificate version and hit save. Azure CDN will then propogate your new updated cert.
320+
To ensure a newer certificate is deployed to PoP infrastructure, simply upload your new certificate to Azure KeyVault, and then in your SSL settings on Azure CDN, choose the newest certificate version and hit save. Azure CDN will then propagate your new updated cert.
317321

318322
## Next steps
319323

-47.4 KB
Loading

0 commit comments

Comments
 (0)