Skip to content

Commit f9041b4

Browse files
authored
Update howto-identity-protection-configure-risk-policies.md
1 parent 75b1789 commit f9041b4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/identity-protection/howto-identity-protection-configure-risk-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Configured trusted [network locations](../conditional-access/location-condition.
3737
Organizations can choose to block access when risk is detected. Blocking sometimes stops legitimate users from doing what they need to. A better solution is to allow self-remediation using Azure AD multifactor authentication (MFA) and secure password change.
3838

3939
> [!WARNING]
40-
> Users must register for Azure AD MFA and password writeback before they face a situation requiring remediation. Users not registered are blocked and require administrator intervention.
40+
> Users must register for Azure AD MFA before they face a situation requiring remediation.For hybrid users that are synced from on-premises to cloud, password writeback must have been enabled on them. Users not registered are blocked and require administrator intervention.
4141
>
4242
> Password change (I know my password and want to change it to something new) outside of the risky user policy remediation flow does not meet the requirement for secure password change.
4343

0 commit comments

Comments
 (0)