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
<!-- Add this BuildingBlocks section to the relying party policy. -->
133
138
<BuildingBlocks>
134
-
<!-- Add the XML code outlined in Step 2 if this section. -->
139
+
<!-- Add the XML code outlined in Step 2 in this section. -->
135
140
</BuildingBlocks>
136
141
137
142
<RelyingParty>
138
143
...
139
144
</RelyingParty>
140
145
</TrustFrameworkPolicy>
141
146
```
147
+
> [!IMPORTANT]
148
+
>Add the code in step 2 to the _relying party policy_ to enforce country/region code restrictions on the server side. You must not define these elements only in parent policies; put them in the relying party policy.
142
149
143
150
1. In the `BuildingBlocks` section of this policy file, add the following code. Make sure to include only the country/region codes relevant to your organization:
144
151
@@ -178,11 +185,8 @@ To help prevent fraudulent sign-ups, remove any country/region codes that do not
178
185
179
186
The countryList acts as an allow list. Only the countries/regions you specify in this list (for example, Japan, Bulgaria, and the United States) are permitted to use MFA. All other countries/regions are blocked.
180
187
181
-
> [!IMPORTANT]
182
-
> This code must be added to the relying party policy to ensure the country/region code restrictions are properly enforced on the server side.
188
+
183
189
184
190
## Related content
185
191
186
192
- Learn about [Identity Protection and Conditional Access for Azure AD B2C](conditional-access-identity-protection-overview.md)
187
-
188
-
- Apply [Conditional Access to user flows in Azure Active Directory B2C](conditional-access-user-flow.md)
0 commit comments