Compliance

Azure Service Principal Compromise: What SMBs Must Do

Azure Service Principal Compromise: What SMBs Must Do

Know what attackers see before they do. See a live Radar report →

If you run Microsoft 365 for your business, there's a quiet attack happening right now that doesn't involve phishing emails, stolen passwords, or MFA fatigue. Attackers are signing into Microsoft Entra ID as application service principals using valid, pre-existing credentials — and they're doing it across multiple organizations simultaneously. No alarms go off. No password reset is triggered. To your tenant, it just looks like an app doing what apps do.

If that sentence made you uneasy, good. It should.

What's Actually Happening

A service principal is the identity an application uses to authenticate into your Azure or Entra ID environment — think of it as a login account, except it's for software instead of a person. Every connected app, integration, or automation tool in your Microsoft 365 environment has one. When attackers compromise a service principal's credentials (often a client secret or certificate), they can sign in as that app and inherit whatever permissions it was granted — sometimes including mail access, directory read/write, or file access across your entire tenant.

The active campaign described in recent threat intelligence shows actors using valid credentials to sign in as application identities across multiple unrelated organizations. That's the part that should concern small businesses most: this isn't a targeted attack against one company. It's a scalable technique, and once attackers have a working credential, they can sit quietly inside your tenant without ever triggering a typical suspicious-login alert tied to user accounts.

Why Small Businesses Are Exposed

Most small businesses and the IT admins supporting them focus security attention on user accounts — MFA, conditional access, password hygiene. App service principals get set up once during an integration and then forgotten. Nobody reviews what permissions that old CRM connector or marketing tool still has two years later.

According to recent reporting on Microsoft's AI Risk Report coverage, government agencies and organizations broadly are being targeted through Microsoft-specific infrastructure weaknesses that don't always make it into official vendor reporting. That's a polite way of saying: the threat is bigger than what gets officially disclosed, and small businesses can't assume Microsoft will flag it for them.

This pattern isn't isolated to Azure, either. According to The Hacker News, password manager mSecure recently warned users to change passwords and reset 2FA and passkeys after suspicious account activity — a reminder that credential compromise response needs to be fast and total, not partial. Similarly, Chainstack's breach disclosure confirms attackers are running large-scale, AI-assisted campaigns against cloud infrastructure providers, exposing customer data and password hashes at scale. The common thread across all three reports: attackers are moving faster and wider than most small business security programs are built to detect.

What to Check in Your Tenant Right Now

  1. Review all app registrations and enterprise applications in Entra ID. Look for apps you don't recognize, apps with no clear business owner, or apps with permissions far beyond what they need.
  2. Check client secret and certificate expiration dates. Old, long-lived secrets are a red flag — rotate anything that hasn't been touched in over a year.
  3. Audit sign-in logs filtered by service principal sign-ins, not just user sign-ins. Look for logins from unfamiliar IP ranges or at unusual times.
  4. Revoke permissions on any app you can't explain. If nobody on your team can say why an app has Mail.ReadWrite or Directory.Read.All, that's your answer.
  5. Set a recurring review cadence — quarterly at minimum — for app permissions, similar to how you'd review user access during offboarding.

This is the same discipline we walk through in our guide to auditing and revoking M365 OAuth app permissions, and it pairs directly with lessons from the ConnectWise/SkyKick breach, where attacker-controlled app permissions went unnoticed for far too long. If you're unsure who in your organization even owns decisions about app access, it's worth revisiting who owns admin credentials before you're forced to answer that question during an incident.

The Bigger Lesson

Service principal compromise is dangerous precisely because it doesn't look like a typical breach. There's no locked-out user, no obvious phishing email to point to. It just looks like business as usual — until data starts leaving your tenant through an app nobody remembers approving.

Small businesses don't need enterprise-grade SOC teams to catch this. They need a habit of checking what's connected to their environment before attackers find it first.

Take Action

Proactive scanning catches misconfigured app permissions and exposed credentials before attackers do — not after. Oscar Six Security's Radar gives small businesses and IT admins an affordable way to check their exposure for just $99 a scan, no long-term contract required. If you haven't reviewed your Entra ID app registrations this quarter, now is the time.

Check your exposure with Radar

Focus Forward. We've Got Your Six.

Frequently Asked Questions

What is a service principal in Azure?

A service principal is the identity an application uses to authenticate into Azure or Microsoft Entra ID, similar to a login account but for software instead of a person. It carries whatever permissions were granted during setup, which attackers can exploit if the credentials are compromised.

How do I check for suspicious app sign-ins in Microsoft 365?

In the Entra ID admin center, review sign-in logs filtered specifically by service principal sign-ins, not just user accounts, and look for unfamiliar IP addresses or unusual access times. You should also review all app registrations for permissions that exceed what the app actually needs.

How often should I audit Azure app permissions?

At minimum, review app registrations and service principal permissions quarterly, and immediately after any major Microsoft 365 integration change. Old, unused, or over-permissioned apps are a common entry point for attackers.

What should I do if I find a compromised app credential?

Immediately revoke the app's client secret or certificate, remove unnecessary permissions, and review sign-in logs to determine what data or systems the app accessed while compromised. Rotate any related credentials and document the incident for compliance purposes.

What tool can small businesses use to check for exposed Azure credentials?

Oscar Six Security's Radar scan checks for exposed credentials, misconfigured permissions, and other security gaps in your environment for $99 per scan. It's designed for small businesses and IT admins who need affordable, proactive visibility without a full enterprise security team.

Step-by-Step Guide

  1. Review app registrations

    Check Entra ID for all app registrations and enterprise applications, flagging any you don't recognize or that lack a clear business owner.

  2. Check credential age

    Look at client secret and certificate expiration dates and rotate anything that hasn't been updated in over a year.

  3. Audit service principal sign-ins

    Filter sign-in logs specifically for service principal activity and look for unfamiliar IPs or unusual login times.

  4. Revoke unnecessary permissions

    Remove access for any app whose purpose or permission level can't be clearly explained by someone on your team.

  5. Set a recurring review schedule

    Establish a quarterly cadence for reviewing app permissions, similar to user access reviews during offboarding.

Find out what's exposed. Radar scans your external attack surface and shows you exactly what needs fixing. See a sample report →