Security checks / Check reference / Purview subject rights
Purview SRR Permission Check Skipped
Medium Severity Microsoft 365 security check in the Purview subject rights domain.
Purview Subject Rights Request checks were skipped because the scanning credential lacks SubjectRightsRequest.Read.All or a required directory role. The scanning credential does not hold the SubjectRightsRequest.Read.All permission or one of the required directory roles. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Purview Subject Rights Request checks were skipped because the scanning credential lacks SubjectRightsRequest.Read.All or a required directory role.
Why it matters
The scanning credential does not hold the SubjectRightsRequest.Read.All permission or one of the required directory roles.
How to fix it
Without these, subject rights request 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.
Find this in your own Microsoft 365
This page is the public reference for one check. Siemserva by Senserva runs it, and 650+ others, against your own tenant: it shows exactly where Purview SRR Permission Check Skipped is failing across your environment, ranks it against everything else by real risk, maps it to the frameworks your auditors ask about, and attaches a validated fix you approve before it applies.
Your Three Free Unlimited Audits cover all of it, free with registration: 1 scan to find, 2 to review your fixes.
Built for the people who own this outcome: security and IT teams closing gaps, auditors and compliance teams gathering evidence, and MSPs and MSSPs running it across every client tenant.
Ask your own AI about this check
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Compliance framework mappings
Findings from this check serve as evidence for:
Related Purview subject rights checks
Common questions
What does the Purview SRR Permission Check Skipped check verify?
Purview Subject Rights Request checks were skipped because the scanning credential lacks SubjectRightsRequest.Read.All or a required directory role. It is a Medium Severity check in the Purview subject rights domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.
How do I fix a Purview SRR Permission Check Skipped finding?
Without these, subject rights request 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 GS-1, DP-2. 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.
