Security checks / Check reference / Purview

Purview Audit Permission Check Skipped

Medium Severity Microsoft 365 security check in the Purview domain.

Purview audit log checks were skipped because the scanning credential lacks the AuditLogsQuery.Read.All permission or required directory role. The scanning credential does not hold the AuditLogsQuery.Read.All permission, or does not hold one of the required directory roles. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Medium SeverityPurview

Check summary

Severity

Medium

Domain

Purview

Rank in domain

Frameworks

What this check verifies

Purview audit log checks were skipped because the scanning credential lacks the AuditLogsQuery.Read.All permission or required directory role.

Why it matters

The scanning credential does not hold the AuditLogsQuery.Read.All permission, or does not hold one of the required directory roles.

How to fix it

Without these, audit log health checks cannot be executed and findings for this area will be absent from the report.

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 "Purview Audit Permission Check Skipped" (source: https://senserva.com/check/purviewauditpermissioncheckskipped.html):
- Verifies: Purview audit log checks were skipped because the scanning credential lacks the AuditLogsQuery.Read.All permission or required directory role.
- Severity: Medium; domain: Purview
- Risk: The scanning credential does not hold the AuditLogsQuery.Read.All permission, or does not hold one of the required directory roles.
- Remediation guidance: Without these, audit log health checks cannot be executed and findings for this area will be absent from the report.
- Compliance frameworks: MCSB, NIST, SOC2, HIPAA; MCSB LT-3, LT-4
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:

MCSBNISTSOC2HIPAAMCSB LT-3MCSB LT-4

References

learn.microsoft.com: /security/benchmark/azure/mcsb-logging-threat-dete...

Related Purview checks

Purview Audit Log No Records Returned Purview Audit Log Unavailable

Common questions

What does the Purview Audit Permission Check Skipped check verify?

Purview audit log checks were skipped because the scanning credential lacks the AuditLogsQuery.Read.All permission or required directory role. It is a Medium Severity check in the Purview domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Purview Audit Permission Check Skipped finding?

Without these, audit log health checks cannot be executed and findings for this area will be absent from the report. 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 MCSB, NIST, SOC2, HIPAA, and MCSB controls LT-3, LT-4. 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.