Skip to content

Commit 32282c1

Browse files
authored
Update partner-bloksec.md
1 parent f80995c commit 32282c1

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,8 @@ zone_pivot_groups: b2c-policy-type
2121

2222
Use the **Choose a policy type** selector for policy type. Azure Active Directory B2C has two methods to define users interaction with applications: predefined user flows or configurable custom policies.
2323

24-
Learn more: [User flows and custom policies overview](user-flow-overview.md)
24+
>[!NOTE]
25+
>In Azure Active Directory B2C, custom policies primarily address complex scenarios. For most scenarios, we recommend built-in user flows.</br> See, [User flows and custom policies overview](./user-flow-overview.md).
2526
2627
## Azure AD B2C and BlokSec
2728

@@ -169,7 +170,7 @@ You should now see BlokSec as a new OIDC Identity provider listed within your B2
169170
1. Once the authentication challenge is accepted, the browser will redirect the user to the replying URL.
170171

171172
>[!NOTE]
172-
>In Azure Active Directory B2C, [**custom policies**](./user-flow-overview.md) are designed primarily to address complex scenarios. For most scenarios, we recommend that you use built-in [**user flows**](./user-flow-overview.md).
173+
>In Azure Active Directory B2C, [custom policies](./user-flow-overview.md) are designed primarily to address complex scenarios. For most scenarios, we recommend that you use built-in [user flows](./user-flow-overview.md).
173174
174175
### Part 2 - Create a policy key
175176

0 commit comments

Comments
 (0)