Skip to content

Commit 3b02e13

Browse files
Merge pull request #291905 from duongau/patch-2
Front Door - On-board APEX domain (add mention of provider for creating alias record)
2 parents a35904c + f4a3a84 commit 3b02e13

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/frontdoor/front-door-how-to-onboard-apex-domain.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,7 @@ You can use the Azure portal to onboard an apex domain on your Azure Front Door
9393
> * The **DNS state** column is used for CNAME mapping check. An apex domain doesn't support a CNAME record, so the DNS state shows **CNAME record is currently not detected** even after you add the alias record to the DNS provider.
9494
> * When you place a service like an Azure Web App behind Azure Front Door, you need to configure the web app with the same domain name as the root domain in Azure Front Door. You also need to configure the back-end host header with that domain name to prevent a redirect loop.
9595
> * Apex domains don't have CNAME records pointing to the Azure Front Door profile. Managed certificate autorotation always fails unless domain validation is finished between rotations.
96+
> * The **Microsoft.Network** resource provider is required to create alias records.
9697
9798
## Enable HTTPS on your custom domain
9899

0 commit comments

Comments
 (0)