Security checks / Check reference / Users & accounts

User Medium Risk User

Medium Severity Microsoft 365 security check in the Users & accounts domain.

User flagged as medium risk by Entra ID Protection Medium-risk users show suspicious behavior patterns (unfamiliar sign-in properties, atypical travel). Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Medium SeverityUsers & accountsSCuBA MS.AAD.6.1v1

Check summary

Severity

Medium

Domain

Users & accounts

Rank in domain

Frameworks

What this check verifies

User flagged as medium risk by Entra ID Protection

Why it matters

Medium-risk users show suspicious behavior patterns (unfamiliar sign-in properties, atypical travel). Without intervention, a compromised session may escalate to data exfiltration

How to fix it

Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.

Ask your own AI about this check

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I manage Microsoft 365 security. Facts for the Senserva check "User Medium Risk User" (source: https://senserva.com/check/imusermediumriskuser.html):
- Verifies: User flagged as medium risk by Entra ID Protection
- Severity: Medium; domain: Users & accounts
- Risk: Medium-risk users show suspicious behavior patterns (unfamiliar sign-in properties, atypical travel). Without intervention, a compromised session may escalate to data exfiltration
- Remediation guidance: Entra admin center → Protection → Identity Protection → Risky users; click the user to review the detection reason; if suspicious, confirm compromise and require password reset; verify a risk-based Conditional Access policy is active (Protection → Conditional Access) requiring MFA for medium+ risk s
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; SCuBA MS.AAD.6.1v1; MCSB LT-3, IM-6
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISHIPAASCuBA MS.AAD.6.1v1MCSB LT-3MCSB IM-6

References

learn.microsoft.com: /security/benchmark/azure/mcsb-identity-management...www.cisa.gov: /sites/default/files/2023-12/Azure%20Active%20Dire...

Related Users & accounts checks

User Break Glass Account Disabled User Break Glass Account Is Not Highly Privileged User Break Glass Account Last Password Change User Break Glass User Has Login History User Break Glass User Has No Login History User Break Glass User Not Enabled User Device Registered To Not Enabled User User Disabled User Device Last Signin Date

Related Entra ID guides

This is an Entra ID and identity check. See the broader guidance and the exact checks Siemserva runs in this area:

Entra ID security best practices Azure AD and Entra ID security All Users & accounts checks

Common questions

What does the User Medium Risk User check verify?

User flagged as medium risk by Entra ID Protection It is a Medium Severity check in the Users & accounts domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a User Medium Risk User finding?

Entra admin center → Protection → Identity Protection → Risky users; click the user to review the detection reason; if suspicious, confirm compromise and require password reset; verify a risk-based Conditional Access policy is active (Protection → Conditional Access) requiring MFA for medium+ risk sign-ins Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.

Which compliance frameworks does this check evidence?

Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, including SCuBA policy MS.AAD.6.1v1, and MCSB controls LT-3, IM-6. That mapping is what turns a scan finding into audit evidence.

Can I ask my own AI about this check?

Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.

All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.