Skip to content

Commit 6356bf1

Browse files
remove redundant section
1 parent 81ec4b0 commit 6356bf1

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

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

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -331,13 +331,6 @@ https://<domain-name>/11111111-1111-1111-1111-111111111111/v2.0/
331331
```
332332
::: zone pivot="b2c-custom-policy"
333333

334-
## (Optional) Block access to the default domain name
335-
336-
After you configure custom domains, users will still be able to access the Azure AD B2C default domain name *&lt;tenant-name&gt;.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.
337-
338-
> [!WARNING]
339-
> Don't request blocking of the default domain until your custom domain works properly.
340-
341334
## (Optional) Azure Front Door advanced configuration
342335

343336
You can use Azure Front Door advanced configuration, such as [Azure Web Application Firewall (WAF)](partner-web-application-firewall.md). Azure WAF provides centralized protection of your web applications from common exploits and vulnerabilities.

0 commit comments

Comments
 (0)