Security checks / Check reference / Service principals

Sp Service Principal Disabled By Microsoft Status

Critical Severity Microsoft 365 security check in the Service principals domain.

Service principal has been disabled by Microsoft due to policy violation or abuse Microsoft disabled this service principal for a reason. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Critical SeverityService principalsSCuBA MS.AAD.5.1v1

Check summary

Severity
Critical
Domain
Service principals
Rank in domain
5
Frameworks
6

What this check verifies

Service principal has been disabled by Microsoft due to policy violation or abuse

Why it matters

Microsoft disabled this service principal for a reason. Dependent automations may be broken and existing permission grants still reference it

How to fix it

Remove or fix dependent automation referencing the disabled service principal

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.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISHIPAASCuBA MS.AAD.5.1v1SCuBA MS.AAD.5.2v1SCuBA MS.AAD.5.3v1MCSB AM-1MCSB IM-3

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:

Common questions

What does the Sp Service Principal Disabled By Microsoft Status check verify?

Service principal has been disabled by Microsoft due to policy violation or abuse It is a Critical Severity check in the Service principals domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Sp Service Principal Disabled By Microsoft Status finding?

Remove or fix dependent automation referencing the disabled service principal 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.5.1v1, MS.AAD.5.2v1, MS.AAD.5.3v1, and MCSB controls AM-1, IM-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.

Reference: the compliance and audit guide, and the full checks catalog.
Data notice: check definitions describe what Siemserva verifies and are provided as is, for informational purposes only, without warranty of any kind. Framework mappings are informational and do not constitute compliance advice; confirm requirements with your assessor. All use of this data is subject to the Senserva EULA.