A cloud-based identity and access management service for securing user authentication and resource access
Microsoft Entra ID Protection does not provide a supported exclusion that suppresses user-risk detections for a particular malicious IP while retaining those events, so first identify the exact detection raising user risk and then replace the user-risk Block control with supported self-remediation where appropriate.
1. Verify what is actually raising user risk
A failed authentication appearing at the same time as a risk change does not establish that the failed attempt caused it. Some detections are calculated offline and can appear later.
- Go to Microsoft Entra admin center → Protection → Identity Protection → Risk detections.
- Filter by the affected user and incident period.
- Open each new detection and record:
- Detection type
- Risk level and state
- Detection time and last updated
- IP address
- Associated risky sign-in
- Open Entra ID → Monitoring & health → Sign-in logs, select the corresponding event, and inspect:
- Authentication details
- Status/error code
- Risk details
- Conditional Access tab and applied policy
The Risk detections report exposes the detection type, attack type, source, risk state, and associated sign-ins.^1^ The sign-in log’s Conditional Access tab identifies exactly which policy interrupted the legitimate user.^2^
This distinction matters because:
- Password spray detection requires a successful credential match; unsuccessful spray attempts do not generate that detection.^3^
- Malicious IP address is an offline detection based partly on high invalid-credential failure rates or other reputation data, and can reflect previous malicious activity.^4^
- Offline detections can take up to 48 hours to surface and unremediated sign-in risks can contribute to aggregate user risk.^5^
If the report genuinely shows a new Password spray detection generated solely by an invalid old password, preserve the request/correlation IDs and timestamps and open a Microsoft support case; that behavior conflicts with the documented detection semantics.
2. Avoid administrative lockouts through self-remediation
If the legitimate user is currently blocked because the user-risk policy uses Block access, change that policy to a self-remediating grant control:
- Open Entra ID → Conditional Access → Policies.
- Select the policy whose condition is User risk.
- Under Access controls → Grant, replace Block access with:
- Require risk remediation, where available and appropriate; or
- Require password change for password-based users.
- Validate the change in report-only mode or against a controlled pilot group before broad deployment.
Require risk remediation lets ID Protection choose the appropriate remediation flow for password-based and passwordless authentication. A secure password change remediates user risk; for passwordless scenarios, remediation can revoke sessions and require another sign-in. Block overrides other grant controls, so the same users should not simultaneously be targeted by another user-risk policy that blocks access.^6^
For sign-in risk, use a separate policy requiring MFA rather than applying the user-wide block. Successful MFA can remediate that risky sign-in before it contributes further to user risk.^7^
3. Do not suppress or misclassify the hostile activity
- Do not mark the attacker’s IP as a trusted named location. Trusted locations lower sign-in risk and are intended for organization-controlled networks.
- Do not select Confirm sign-in safe for a known hostile attempt. That action identifies a false positive and tells the system that similar sign-ins should not be considered risky.
- Do not use Dismiss sign-in risk for this activity; it is intended for a benign true positive, such as approved penetration testing.
- Confirm sign-in compromised is accurate for a malicious true positive, but it immediately raises aggregate user and sign-in risk to high, so it is not a suppression mechanism.^8^
Continue exporting and alerting on failed sign-ins independently of the user-risk enforcement decision. Microsoft recommends monitoring failure code 50126 for invalid credentials and 53003 for Conditional Access blocks, with thresholds adjusted to organizational baselines.^9^
Blocking the source through Conditional Access does not prevent the initial authentication signal from being processed: Conditional Access location policies are enforced after first-factor authentication. Therefore, a location block can deny resource access while the attempt remains visible to sign-in logging and risk analysis.^10^
References
- Microsoft Entra ID Protection risk reports
- Troubleshoot sign-in problems with Conditional Access
- How to investigate risk
- What are risk detections?
- Risk detection types and levels
- Risk-based access policies
- Remediate risks and unblock users
- How To: Give risk feedback in Microsoft Entra ID Protection
- Microsoft Entra security operations for user accounts
- Block access by location