Security checks / Check reference / Service principals
Sp Risk Detection Suspicious Sign In
Medium Severity Microsoft 365 security check in the Service principals domain.
Suspicious sign-in risk detection on a service principal A suspicious sign-in on a service principal may indicate stolen credentials being used from an unfamiliar location or IP Check for unauthorized API calls immediately Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Suspicious sign-in risk detection on a service principal
Why it matters
A suspicious sign-in on a service principal may indicate stolen credentials being used from an unfamiliar location or IP Check for unauthorized API calls immediately
How to fix it
Investigate suspicious sign-in patterns; rotate credentials if compromise is likely
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 Risk Detection Suspicious Sign In check verify?
Suspicious sign-in risk detection on a service principal 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 Risk Detection Suspicious Sign In finding?
Investigate suspicious sign-in patterns; rotate credentials if compromise is likely 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 LT-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.