You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/partner-cloudflare.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,13 +51,13 @@ On cloudflare.com, you can [create an account](https://dash.cloudflare.com/sign-
51
51
52
52
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.
53
53
54
-

54
+

55
55
56
56
2. Under the DNS pane, toggle the **Proxy status** option to **Proxied**. It turns orange.
57
57
58
58
The settings appear in the following image.
59
59
60
-

60
+

61
61
62
62
### Configure the Web Application Firewall
63
63
@@ -67,22 +67,22 @@ Go to your Cloudflare settings, and use the Cloudflare content to [configure the
67
67
68
68
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.
69
69
70
-

70
+


79
79
80
80
> [!NOTE]
81
81
> 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-).
82
82
83
83
2. The Azure AD B2C policy sign-in dialog appears.
84
84
85
-

85
+

0 commit comments