Security checks / Check reference / Privileged access (PIM)

Role Custom Role In Use

High Severity Microsoft 365 security check in the Privileged access (PIM) domain.

A custom (non-built-in) role definition has active assignments Custom roles can hide privilege escalation paths, are harder to audit against benchmarks, and may grant unexpected permission combinations. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

High SeverityPrivileged access (PIM)SCuBA MS.AAD.7.1v1

Check summary

Severity

High

Domain

Privileged access (PIM)

Rank in domain

Frameworks

What this check verifies

A custom (non-built-in) role definition has active assignments

Why it matters

Custom roles can hide privilege escalation paths, are harder to audit against benchmarks, and may grant unexpected permission combinations. Risk level is determined by the permissions the role grants, roles with credential, role assignment, or tenant-wide write access are classified as highly privileged

How to fix it

Review custom role permissions; verify they follow least-privilege; document business justification; prefer built-in roles where possible

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 "Role Custom Role In Use" (source: https://senserva.com/check/imrolecustomroleinuse.html):
- Verifies: A custom (non-built-in) role definition has active assignments
- Severity: High; domain: Privileged access (PIM)
- Risk: Custom roles can hide privilege escalation paths, are harder to audit against benchmarks, and may grant unexpected permission combinations. Risk level is determined by the permissions the role grants, roles with credential, role assignment, or tenant-wide write access are classified as highly privil
- Remediation guidance: Review custom role permissions; verify they follow least-privilege; document business justification; prefer built-in roles where possible
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; SCuBA MS.AAD.7.1v1, MS.AAD.7.2v1, MS.AAD.7.3v1, MS.AAD.7.4v1, MS.AAD.7.5v1, MS.AAD.7.6v1, MS.AAD.7.7v1, MS.AAD.7.8v1, MS.AAD.7.9v1; MCSB PA-1, PA-7
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.7.1v1 SCuBA MS.AAD.7.2v1 SCuBA MS.AAD.7.3v1 SCuBA MS.AAD.7.4v1 SCuBA MS.AAD.7.5v1 SCuBA MS.AAD.7.6v1 SCuBA MS.AAD.7.7v1 SCuBA MS.AAD.7.8v1 SCuBA MS.AAD.7.9v1MCSB PA-1MCSB PA-7

References

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

Related Privileged access (PIM) checks

PIM Alert Configuration Incorrect PIM Alerts PIM Alerts License Suspended PIM Alerts No MFA On Activation Alert PIM Alerts Stale Alert Incident PIM Alerts Too Many Global Admins Assigned To Ten...PIM Group Number Of Groups In High Privilege Roles PIM Group Number Of Groups In Privilege Roles

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 Privileged access (PIM) checks

Common questions

What does the Role Custom Role In Use check verify?

A custom (non-built-in) role definition has active assignments It is a High Severity check in the Privileged access (PIM) domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Role Custom Role In Use finding?

Review custom role permissions; verify they follow least-privilege; document business justification; prefer built-in roles where possible 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.7.1v1, MS.AAD.7.2v1, MS.AAD.7.3v1, MS.AAD.7.4v1, MS.AAD.7.5v1, MS.AAD.7.6v1, MS.AAD.7.7v1, MS.AAD.7.8v1, MS.AAD.7.9v1, and MCSB controls PA-1, PA-7. 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.