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/cdn/cdn-custom-ssl.md
+2-16Lines changed: 2 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,8 +95,8 @@ To enable HTTPS on a custom domain, follow these steps:
95
95
# [Option 2: Enable HTTPS with your own certificate](#tab/option-2-enable-https-with-your-own-certificate)
96
96
97
97
> [!IMPORTANT]
98
-
> This option is available only with **Azure CDN from Microsoft** and **Azure CDN from Edgio** profiles.
99
-
>
98
+
> *This option is available only with **Azure CDN from Microsoft** and **Azure CDN from Edgio** profiles.
99
+
>* The option to use your own certificate with Azure CDN from Edgio will undergo maintenance on June 20, 2024. This feature will be unavailable during this time and will be restored in early 2025.
100
100
101
101
You can use your own certificate to enable the HTTPS feature. This process is done through an integration with Azure Key Vault, which allows you to store your certificates securely. Azure CDN uses this secure mechanism to get your certificate and it requires a few extra steps. When you create your TLS/SSL certificate, you must create a complete certificate chain with an allowed certificate authority (CA) that is part of the [Microsoft Trusted CA List](https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT). If you use a nonallowed CA, your request is rejected. If a certificate without complete chain is presented, requests, which involve that certificate aren't guaranteed to work as expected. For Azure CDN from Edgio, any valid CA is accepted.
102
102
@@ -332,20 +332,6 @@ The following table shows the operation progress that occurs when you disable HT
#### Certificate auto rotation with Azure CDN from Edgio
336
-
337
-
Managed certificates from Azure Key Vault can utilize the certificate autorotate feature, allowing Azure CDN from Edgio to automatically retrieve updated certificates and propagate them to the Edgio CDN platform. To enable this feature:
338
-
339
-
1. Register Azure CDN as an application within your Microsoft Entra ID.
340
-
341
-
1. Authorize the Azure CDN service to access the secrets in your Key Vault. Navigate to "Access policies" within your Key Vault to add a new policy, then grant the **Microsoft.AzureFrontDoor-Cdn** service principal a **Get secrets** permission.
342
-
343
-
1. Set the certificate version to **Latest** under the **Certificate management type** within the **Custom domain** menu. If a specific version of the certificate is selected, manual updates are required.
344
-
345
-
> [!NOTE]
346
-
> * Be aware that it can take up to 24 hours for the certificate auto-rotate to fully complete the propagation of the new certificate.
347
-
> * If a certificate is utilized to cover multiple custom domains, it is imperative to enable certificate auto-rotate on all the custom domains sharing this certificate to ensure correct operation. Failure to do so may result in the Edgio platform serving an incorrect version of the certificate for the custom domain that does not have this feature enabled."
348
-
349
335
## Frequently asked questions
350
336
351
337
1. *Who is the certificate provider and what type of certificate is used?*
0 commit comments