Skip to content

Commit 77646e6

Browse files
committed
review
1 parent 05c3b72 commit 77646e6

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

articles/active-directory-b2c/custom-domain.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: kengaderdus
66
manager: CelesteDG
77
ms.service: active-directory
88
ms.topic: how-to
9-
ms.date: 02/09/2024
9+
ms.date: 02/14/2024
1010
ms.author: kengaderdus
1111
ms.subservice: B2C
1212
ms.custom: "b2c-support"
@@ -52,8 +52,12 @@ When using custom domains, consider the following:
5252

5353
- You can set up multiple custom domains. For the maximum number of supported custom domains, see [Microsoft Entra service limits and restrictions](/entra/identity/users/directory-service-limits-restrictions) for Azure AD B2C and [Azure subscription and service limits, quotas, and constraints](/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-front-door-classic-limits) for Azure Front Door.
5454
- Azure Front Door is a separate Azure service, so extra charges will be incurred. For more information, see [Front Door pricing](https://azure.microsoft.com/pricing/details/frontdoor).
55-
- After you configure custom domains, users will still be able to access the Azure AD B2C default domain name *<tenant-name>.b2clogin.com*. You need to block access to the default domain so that attackers can't use it to access your apps or run distributed denial-of-service (DDoS) attacks. [Submit a support ticket](find-help-open-support-ticket.md) to request for the restriction of access to the default domain.
56-
- If you have multiple applications, migrate them all to the custom domain because the browser stores the Azure AD B2C session under the domain name currently being used.
55+
- If you've multiple applications, migrate all oft them to the custom domain because the browser stores the Azure AD B2C session under the domain name currently being used.
56+
- After you configure custom domains, users will still be able to access the Azure AD B2C default domain name *<tenant-name>.b2clogin.com*. You need to block access to the default domain so that attackers can't use it to access your apps or run distributed denial-of-service (DDoS) attacks. [Submit a support ticket](find-help-open-support-ticket.md) to request for the blocking of access to the default domain.
57+
58+
> [!WARNING]
59+
> Don't request blocking of the default domain until your custom domain works properly.
60+
5761

5862
## Prerequisites
5963

0 commit comments

Comments
 (0)