Skip to content

Commit c797263

Browse files
authored
Update partner-cloudflare.md
1 parent 098a3e2 commit c797263

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

articles/active-directory-b2c/partner-cloudflare.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,7 @@ To get started, you'll need:
3434
Cloudflare WAF integration includes the following components:
3535

3636
- **Azure AD B2C tenant** – The authorization server that verifies user credentials using the custom policies defined in the tenant. It's known as the identity provider
37-
3837
- [**Azure Front Door**](../frontdoor/front-door-overview.md) – Enables custom domains for Azure B2C tenant. Traffic from Cloudflare WAF is routed to Azure Front Door before arriving at Azure AD B2C tenant.
39-
4038
- **Cloudflare** – The web application firewall that manages traffic sent to the authorization server
4139

4240
## Integrate with Azure AD B2C
@@ -45,21 +43,21 @@ For custom domains in Azure AD B2C, use the custom domain feature in Azure Front
4543

4644
After a custom domain for Azure AD B2C is configured using Azure Front Door, [test the custom domain](./custom-domain.md?pivots=b2c-custom-policy#test-your-custom-domain) before proceeding.
4745

48-
## Onboard with Cloudflare
46+
## Create a Cloudflare account
4947

5048
On cloudflare.com, you can [create an account](https://dash.cloudflare.com/sign-up). To enable WAF, on [Application Services]([https://www.cloudflare.com/plans/](https://www.cloudflare.com/plans/#price-matrix) select **Pro**, which is required.
5149

5250
### Configure DNS
5351

5452
1. To enable WAF for a domain, in the DNS console for the CNAME entry, turn on the proxy setting from the DNS console for the CNAME entry as shown.
5553

56-
![Image shows how to select proxy settings](./media/partner-cloudflare/select-proxy-settings.png)
54+
![Image shows how to select proxy settings](./media/partner-cloudflare/select-proxy-settings.png)
5755

5856
2. Under the DNS pane, toggle the **Proxy status** option to **Proxied**. It turns orange.
5957

6058
The settings appear in the following image.
6159

62-
![Image shows how to select proxied](./media/partner-cloudflare/select-proxied.png)
60+
![Image shows how to select proxied](./media/partner-cloudflare/select-proxied.png)
6361

6462
### Configure the Web Application Firewall
6563

@@ -69,22 +67,22 @@ Go to your Cloudflare settings, and use the Cloudflare content to [configure the
6967

7068
In the top pane of the console, use the firewall option to add, update, or remove firewall rules. For example, the following firewall setting enables CAPTCHA for incoming requests to *contosobank.co.uk* domain before the request goes to Azure Front Door.
7169

72-
![Image shows how to enforce captcha](./media/partner-cloudflare/configure-firewall-rule.png)
70+
![Image shows how to enforce captcha](./media/partner-cloudflare/configure-firewall-rule.png)
7371

7472
Learn more: [Cloudflare Firewall Rules](https://support.cloudflare.com/hc/articles/360016473712-Cloudflare-Firewall-Rules)
7573

7674
### Test the settings
7775

7876
1. Complete CAPTCHA when access to the custom domain is requested.
7977

80-
![Image shows cloudflare WAF enforce CAPTCHA](./media/partner-cloudflare/enforce-captcha.png)
78+
![Image shows cloudflare WAF enforce CAPTCHA](./media/partner-cloudflare/enforce-captcha.png)
8179

8280
> [!NOTE]
8381
> Cloudflare has functionality to customize block pages. See, [Configuring Custom Pages (Error and Challenge)](https://support.cloudflare.com/hc/en-us/articles/200172706-Configuring-Custom-Pages-Error-and-Challenge-).
8482
8583
2. The Azure AD B2C policy sign-in dialog appears.
8684

87-
![Image shows Azure AD B2C policy log in](./media/partner-cloudflare/azure-ad-b2c-policy.png)
85+
![Image shows Azure AD B2C policy log in](./media/partner-cloudflare/azure-ad-b2c-policy.png)
8886

8987
## Resources
9088

0 commit comments

Comments
 (0)