High Risk Sign-Ins Shall Be Blocked
PreviousHigh Risk Users Shall Be BlockedNextBrowser Sessions shall not be persistent for privileged users
Last updated
Azure AD Identity Protection uses various signals to detect the risk level for each user sign-in. Sign-ins detected as high risk are to be blocked via Conditional Access.
Sign-Ins detected as high risk shall be blocked.
Notifications will be sent to admins when high-risk sign-ins are detected.
Azure AD P2. Can be purchased standalone or part of the following bundles:
EMS + E5
Microsoft 365 E3
Microsoft 365 E5
Create a conditional access policy for Sign-In risk: Risk policies - Azure Active Directory Identity Protection - Microsoft Entra | Microsoft Learn
Under Access Controls> Grant, select Block Access
To Create notifications for admins: Azure Active Directory Identity Protection notifications - Microsoft Entra | Microsoft Learn
Identity Protection Overview: Azure Active Directory Identity Protection notifications - Microsoft Entra | Microsoft Learn
Level: High
Once a respective conditional access policy is implemented, if a high-risk user attempts to login, the user will receive an error message with instructions to contact the administrator to re-enable their access.

If after implementing this, it is observed that numerous legitimate user sign-ins are consistently being blocked due to their location being interpreted as suspicious and this creates an operational burden on the agency, then a Trusted Location can be configured in the Conditional Access blade for each of the legitimate sign-in locations. Azure AD Identity Protection considers the Trusted Location data when it calculates sign-in risk, and this may help to prevent users signing in from legitimate locations from being flagged as high risk.
Tips
Investigate the risk event following these steps: Investigate risk Azure Active Directory Identity Protection - Microsoft Entra | Microsoft Learn
• None Currently
Last updated