Security checks / Check reference / Logging & threat detection

Log Flagged For Review

Critical Severity Microsoft 365 security check in the Logging & threat detection domain.

Microsoft flagged this sign-in for review as potentially suspicious Microsoft's internal risk engine identified anomalous behavior; ignoring flagged sign-ins leaves confirmed-risk events unresolved Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Critical SeverityLogging & threat detectionSCuBA MS.AAD.4.1v1

Check summary

Severity

Critical

Domain

Logging & threat detection

Rank in domain

Frameworks

What this check verifies

Microsoft flagged this sign-in for review as potentially suspicious

Why it matters

Microsoft's internal risk engine identified anomalous behavior; ignoring flagged sign-ins leaves confirmed-risk events unresolved

How to fix it

Investigate the flagged sign-in; correlate with risk detections; confirm or dismiss in Identity Protection

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 "Log Flagged For Review" (source: https://senserva.com/check/ltlogflaggedforreview.html):
- Verifies: Microsoft flagged this sign-in for review as potentially suspicious
- Severity: Critical; domain: Logging & threat detection
- Risk: Microsoft's internal risk engine identified anomalous behavior; ignoring flagged sign-ins leaves confirmed-risk events unresolved
- Remediation guidance: Investigate the flagged sign-in; correlate with risk detections; confirm or dismiss in Identity Protection
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; SCuBA MS.AAD.4.1v1; MCSB LT-3
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.4.1v1MCSB LT-3

References

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

Related Logging & threat detection checks

Audit As App Application Activity Audit As App Failed Application Management Change Audit Audit Completed Audit Audit Started Audit Authentication Change Audit Authorization Change Authorization Change Audit CA Change Audit CA Failed Conditional Access Change

Common questions

What does the Log Flagged For Review check verify?

Microsoft flagged this sign-in for review as potentially suspicious It is a Critical Severity check in the Logging & threat detection domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Log Flagged For Review finding?

Investigate the flagged sign-in; correlate with risk detections; confirm or dismiss in Identity Protection 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.4.1v1, and MCSB control LT-3. 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.