Security checks / Check reference / Service principals
Sp Service Principal No Verified Publisher
Medium Severity Microsoft 365 security check in the Service principals domain.
Service principal does not have a verified publisher but has a publisher name. Third-party apps without verification pose higher trust risk Without a verified publisher, users cannot distinguish this app from a phishing app Consent prompts look the same for legitimate and malicious apps Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Service principal does not have a verified publisher but has a publisher name. Third-party apps without verification pose higher trust risk
Why it matters
Without a verified publisher, users cannot distinguish this app from a phishing app Consent prompts look the same for legitimate and malicious apps
How to fix it
Require verified publishers for third-party service principals
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:
References
Related Service principals checks
Common questions
What does the Sp Service Principal No Verified Publisher check verify?
Service principal does not have a verified publisher but has a publisher name. Third-party apps without verification pose higher trust risk It is a Medium 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 No Verified Publisher finding?
Require verified publishers for third-party service principals 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 control 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.