Skip to content

Commit 5997944

Browse files
committed
tls policy updates
1 parent fc8011d commit 5997944

File tree

10 files changed

+31
-26
lines changed

10 files changed

+31
-26
lines changed

articles/frontdoor/end-to-end-tls.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
---
2-
title: TLS encryption with Azure Front Door
2+
title: TLS encryption
3+
titleSuffix: Azure Front Door
34
description: Learn about end-to-end TLS encryption, supported TLS versions, and supported cipher suites with Azure Front Door.
45
author: halkazwini
56
ms.author: halkazwini
67
ms.service: azure-frontdoor
78
ms.topic: concept-article
8-
ms.date: 03/18/2025
9+
ms.date: 03/26/2025
910
zone_pivot_groups: front-door-tiers
1011
---
1112

@@ -109,7 +110,7 @@ For your own custom TLS/SSL certificate:
109110

110111
## Supported cipher suites
111112

112-
For TLS 1.2/1.3 the following cipher suites are supported:
113+
For TLS 1.2/1.3, the following cipher suites are supported:
113114

114115
- TLS_AES_256_GCM_SHA384 (TLS 1.3 only)
115116
- TLS_AES_128_GCM_SHA256 (TLS 1.3 only)
@@ -120,7 +121,7 @@ For TLS 1.2/1.3 the following cipher suites are supported:
120121
- TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
121122
- TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
122123

123-
Azure Front Door doesn’t support disabling or configuring specific cipher suites for your profile.
124+
To configure specific cipher suites for your profile, use TLS policy. Azure Front Door Standard and Premium offer two mechanisms for controlling TLS policy. You can use either a predefined policy or a custom policy per your own needs. For more information, see [Configure TLS policy on a Front Door custom domain](standard-premium/tls-policy-configure.md).
124125

125126
> [!NOTE]
126127
> For Windows 10 and later versions, we recommend enabling one or both of the ECDHE_GCM cipher suites for better security. Windows 8.1, 8, and 7 aren't compatible with these ECDHE_GCM cipher suites. The ECDHE_CBC and DHE cipher suites have been provided for compatibility with those operating systems.
@@ -129,6 +130,7 @@ Azure Front Door doesn’t support disabling or configuring specific cipher suit
129130

130131
::: zone pivot="front-door-standard-premium"
131132

133+
- [Azure Front Door TLS policy](standard-premium/tls-policy.md)
132134
- [Domains in Azure Front Door](domain.md)
133135
- [Configure a custom domain on Azure Front Door](standard-premium/how-to-add-custom-domain.md)
134136

52.6 KB
Loading
Binary file not shown.
Binary file not shown.
5.41 KB
Loading
44 KB
Loading

articles/frontdoor/standard-premium/how-to-add-custom-domain.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,13 @@
11
---
2-
title: 'How to add a custom domain - Azure Front Door'
2+
title: How to add a custom domain
3+
titleSuffix: Azure Front Door
34
description: In this article, you learn how to onboard a custom domain to an Azure Front Door profile by using the Azure portal.
45
author: halkazwini
56
ms.author: halkazwini
67
ms.service: azure-frontdoor
78
ms.topic: how-to
8-
ms.date: 11/12/2024
9+
ms.date: 03/26/2025
10+
911
#Customer intent: As a website owner, I want to add a custom domain to my Azure Front Door configuration so that my users can use my custom domain to access my content.
1012
---
1113

@@ -35,11 +37,11 @@ To configure a custom domain, go to the **Domains** pane of your Azure Front Doo
3537

3638
* **Non-Azure validated domain**: The domain requires ownership validation. We recommend using the Azure-managed DNS option. You can also use your own DNS provider. If you choose Azure-managed DNS, select an existing DNS zone and either select an existing custom subdomain or create a new one. If you're using another DNS provider, manually enter the custom domain name. Then select **Add** to add your custom domain.
3739

38-
:::image type="content" source="../media/how-to-add-custom-domain/add-domain-page.png" alt-text="Screenshot that shows the Add a domain pane.":::
40+
:::image type="content" source="../media/add-domain.png" alt-text="Screenshot that shows the Add a domain pane." lightbox="../media/add-domain.png":::
3941

4042
* **Azure pre-validated domain**: The domain is already validated by another Azure service, so domain ownership validation isn't required from Azure Front Door. A dropdown list of validated domains by different Azure services appear.
4143

42-
:::image type="content" source="../media/how-to-add-custom-domain/pre-validated-custom-domain.png" alt-text="Screenshot that shows Prevalidated custom domains on the Add a domain pane.":::
44+
:::image type="content" source="../media/pre-validated-custom-domain.png" alt-text="Screenshot that shows Prevalidated custom domains on the Add a domain pane.":::
4345

4446
> [!NOTE]
4547
> * Azure Front Door supports both Azure-managed certificates and Bring Your Own Certificates (BYOCs). For non-Azure validated domains, Azure-managed certificates are issued and managed by Azure Front Door. For Azure prevalidated domains, the Azure-managed certificate is issued and managed by the Azure service that validates the domain. To use your own certificate, see [Configure HTTPS on a custom domain](how-to-configure-https-custom-domain.md).
@@ -87,7 +89,7 @@ After validating your custom domain, you can associate it with your Azure Front
8789

8890
> [!NOTE]
8991
> * If HTTPS is enabled, certificate provisioning and propagation might take a few minutes as it propagates to all edge locations.
90-
> * If your domain CNAME is indirectly pointed to an Azure Front Door endpoint, such as through Azure Traffic Manager for multi-CDN failover, the **DNS state** column may show **CNAME/Alias record currently not detected**. Azure Front Door can't guarantee 100% detection of the CNAME record in this scenario. If you configured an Azure Front Door endpoint to Traffic Manager and still see this message, it doesn't necessarily mean there is an issue with your setup. No further action is required.
92+
> * If your domain CNAME is indirectly pointed to an Azure Front Door endpoint, such as through Azure Traffic Manager for multi-CDN failover, the **DNS state** column may show **CNAME/Alias record currently not detected**. Azure Front Door can't guarantee 100% detection of the CNAME record in this scenario. If you configured an Azure Front Door endpoint to Traffic Manager and still see this message, it doesn't necessarily mean there's an issue with your setup. No further action is required.
9193
9294
## Verify the custom domain
9395

@@ -97,8 +99,8 @@ After validating and associating the custom domain, ensure that the custom domai
9799

98100
Finally, verify that your application content is being served by using a browser.
99101

100-
## Next steps
102+
## Related content
101103

102-
* Learn how to [enable HTTPS for your custom domain](how-to-configure-https-custom-domain.md).
103-
* Learn more about [custom domains in Azure Front Door](../domain.md).
104-
* Learn about [end-to-end TLS with Azure Front Door](../end-to-end-tls.md).
104+
- [Enable HTTPS on your custom domain](how-to-configure-https-custom-domain.md)
105+
- [Custom domains in Azure Front Door](../domain.md)
106+
- [End-to-end TLS with Azure Front Door](../end-to-end-tls.md)

articles/frontdoor/standard-premium/how-to-configure-https-custom-domain.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,17 @@
11
---
2-
title: 'Configure HTTPS for your custom domain - Azure Front Door'
3-
description: In this article, you learn how to configure HTTPS on an Azure Front Door custom domain by using the Azure portal.
2+
title: Configure HTTPS for your custom domain
3+
titleSuffix: Azure Front Door
4+
description: In this article, you learn how to configure HTTPS on an Azure Front Door custom domain using the Azure portal.
45
author: halkazwini
56
ms.author: halkazwini
67
ms.service: azure-frontdoor
78
ms.topic: how-to
8-
ms.date: 04/30/2024
9+
ms.date: 03/26/2025
910

1011
#Customer intent: As a website owner, I want to add a custom domain to my Azure Front Door configuration so that my users can use my custom domain to access my content.
1112
---
1213

13-
# Configure HTTPS on an Azure Front Door custom domain by using the Azure portal
14+
# Configure HTTPS on an Azure Front Door custom domain using the Azure portal
1415

1516
Azure Front Door enables secure Transport Layer Security (TLS) delivery to your applications by default when you use your own custom domains. To learn more about custom domains, including how custom domains work with HTTPS, see [Domains in Azure Front Door](../domain.md).
1617

@@ -50,7 +51,7 @@ If you have your own domain, and the domain is associated with [another Azure se
5051

5152
1. On the **Add a domain** pane, enter or select the following information. Then select **Add** to onboard the custom domain.
5253

53-
:::image type="content" source="../media/how-to-configure-https-custom-domain/add-pre-validated-domain.png" alt-text="Screenshot that shows the Add a domain pane with a prevalidated domain.":::
54+
:::image type="content" source="../media/pre-validated-custom-domain.png" alt-text="Screenshot that shows the Add a domain pane with a prevalidated domain.":::
5455

5556
| Setting | Value |
5657
|--|--|
@@ -81,7 +82,7 @@ There are currently two ways to authenticate Azure Front Door to access your Key
8182
8283
#### Register Azure Front Door
8384

84-
Register the service principal for Azure Front Door as an app in your Microsoft Entra ID by using Microsoft Graph PowerShell or the Azure CLI.
85+
Register the service principal for Azure Front Door as an app in your Microsoft Entra ID using Microsoft Graph PowerShell or the Azure CLI.
8586

8687
> [!NOTE]
8788
> * This action requires you to have User Access Administrator permissions in Microsoft Entra ID. The registration only needs to be performed *once per Microsoft Entra tenant*.
@@ -99,7 +100,7 @@ Register the service principal for Azure Front Door as an app in your Microsoft
99100
New-MgServicePrincipal -AppId '205478c0-bd83-4e1b-a9d6-db63a3e1e1c8'
100101
```
101102
102-
Azure government cloud:
103+
Azure Government cloud:
103104
104105
```azurepowershell-interactive
105106
New-MgServicePrincipal -AppId 'd4631ece-daab-479b-be77-ccb713491fc0'
@@ -117,7 +118,7 @@ Register the service principal for Azure Front Door as an app in your Microsoft
117118
az ad sp create --id 205478c0-bd83-4e1b-a9d6-db63a3e1e1c8
118119
```
119120
120-
Azure government cloud:
121+
Azure Government cloud:
121122
122123
```azurecli-interactive
123124
az ad sp create --id d4631ece-daab-479b-be77-ccb713491fc0
@@ -184,8 +185,8 @@ You can change a domain between using an Azure Front Door-managed certificate an
184185
185186
1. Select **Update** to change the associated certificate with a domain.
186187
187-
## Next steps
188+
## Related content
188189
189-
* Learn about [caching with Azure Front Door Standard/Premium](../front-door-caching.md).
190-
* [Understand custom domains](../domain.md) on Azure Front Door.
191-
* Learn about [end-to-end TLS with Azure Front Door](../end-to-end-tls.md).
190+
- Learn about [caching with Azure Front Door Standard/Premium](../front-door-caching.md)
191+
- [Understand custom domains](../domain.md) on Azure Front Door
192+
- Learn about [end-to-end TLS with Azure Front Door](../end-to-end-tls.md)

articles/frontdoor/standard-premium/tls-policy-configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ In this article, you learn how to configure TLS policy on a Front Door custom do
3939

4040
1. For **TLS policy**, select the predefined policy from the dropdown list or **Custom** to customize the cipher suites per your needs.
4141

42-
:::image type="content" source="../media/tls-policy-configure/tls-policy.png" alt-text="Screenshot that shows the TLS policy option in Add a domain page." lightbox="../media/tls-policy-configure/tls-policy.png":::
42+
:::image type="content" source="../media/add-domain.png" alt-text="Screenshot that shows the TLS policy option in Add a domain page." lightbox="../media/add-domain.png":::
4343

4444
You can view the supported cipher suites by selecting **View policy details**.
4545

0 commit comments

Comments
 (0)