Compliance

Global Admin Sprawl: How to Audit M365 Permissions

Global Admin Sprawl: How to Audit M365 Permissions

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

A Reddit post went viral recently when an IT admin described inheriting a 40-seat client's Microsoft 365 tenant and finding 14 Global Admins. One of them was a Xerox scanner's service account. Another belonged to an employee who'd left the company back in 2022. The comments filled with similar horror stories: marketing coordinators with tenant-wide admin rights, old MSP technicians never offboarded, break-glass accounts nobody remembered creating.

This isn't a rare edge case. It's the default state of most small business M365 tenants, because Global Admin is the easiest checkbox to click when something isn't working and nobody wants to spend twenty minutes figuring out the correct role.

The problem is that admin sprawl isn't just messy — it's a force multiplier for every other vulnerability sitting in your environment right now.

Why This Matters More Right Now

According to The Hacker News, this month's Patch Tuesday included an actively exploited Outlook zero-day capable of exposing NTLMv2 hashes. In practice, that means an attacker who successfully triggers the flaw could walk away with credential material usable to impersonate a user — and if that user happens to be one of your 14 Global Admins, the blast radius isn't one mailbox. It's the entire tenant: every user's email, every SharePoint library, every connected app, every security policy.

This wasn't an isolated patch either. As covered in the roundup on November Patch Tuesday, Microsoft shipped fixes for 1,259 flaws this cycle, including critical bugs across Exchange, SharePoint, Windows Search, and LDAP. Krebs on Security also flagged the Outlook zero-day specifically, noting the scale of this patch cycle as evidence that Microsoft 365 and Windows environments remain under sustained, high-volume attack. Every one of those attack surfaces gets dramatically worse the moment too many accounts hold tenant-wide admin rights. A single phished credential or exploited flaw shouldn't be able to compromise your whole organization — but in a tenant with 14 Global Admins, it absolutely can.

How to Audit Global Admins in Entra ID

You don't need expensive tooling to start. Here's the practical sequence:

1. Pull the current Global Admin list. In the Microsoft Entra admin center, go to Roles & Administrators > Global Administrator and export the full membership list. Do this before you do anything else, so you have a baseline.

2. Identify what each account actually is. For every entry, document: Is this a human? Is it still employed? Is it a service account (like that Xerox scanner)? Is it a break-glass emergency account? You will almost always find accounts nobody can explain — treat those as the highest priority to investigate.

3. Cross-reference against HR/offboarding records. Former employees retaining Global Admin is one of the most common findings in these audits. If your organization doesn't have a formal offboarding checklist, our employee offboarding security checklist walks through exactly what access needs to be pulled and in what order.

4. Map actual job function to minimum required role. Most people flagged as Global Admin only need a scoped role — Exchange Administrator, SharePoint Administrator, User Administrator, or Helpdesk Administrator. Microsoft Entra ID has over 60 built-in roles specifically so you don't have to hand out the keys to everything.

5. Move service accounts to app-only authentication with scoped API permissions instead of interactive Global Admin logins. If you're not sure what your connected apps can currently do, our guide on auditing and revoking M365 OAuth app permissions is a good companion read here.

6. Set up Privileged Identity Management (PIM) if you're on an eligible license tier, so admin roles are time-bound and activated on demand rather than standing 24/7.

7. Document who owns admin credential decisions going forward, so this doesn't silently regrow in six months. We cover building that governance structure in who owns admin credentials.

The Right-Sizing Mindset

Least privilege isn't a one-time cleanup — it's a standing policy. Every new hire, every new vendor integration, every new RMM tool should get the minimum role required for their function, reviewed on a recurring schedule (quarterly is reasonable for most small organizations). Government contractors working toward CMMC Level 1 should treat this audit as foundational, since excessive privilege is one of the first things assessors flag.

The uncomfortable truth from that Reddit thread is that most IT admins don't build these messes — they inherit them. But once you've found 14 Global Admins, the fix isn't complicated. It's just tedious, and it's exactly the kind of tedious work that prevents the kind of breach that isn't tedious at all.

Take Action

Admin sprawl is invisible until an attacker finds it — and this month's patch cycle is a reminder that credential-exposing flaws are being actively exploited in the wild right now. Proactive scanning catches these misconfigurations before attackers do, not after. Oscar Six Security's Radar scan checks your Microsoft 365 environment for exactly this kind of exposure — excessive admin rights, risky app permissions, and more — for a flat $99. Check out Radar and our other solutions.

Focus Forward. We've Got Your Six.

Frequently Asked Questions

How many Global Admins should a small business Microsoft 365 tenant have?

Microsoft recommends two to four Global Admin accounts maximum — enough for redundancy without unnecessary exposure. Most small business tenants should use scoped roles like Exchange Administrator or User Administrator for everything else.

How do I check who has Global Admin access in Microsoft 365?

In the Microsoft Entra admin center, navigate to Roles & Administrators, select Global Administrator, and review the member list. Export this list and cross-reference it against current employment records and known service accounts.

What is the risk of too many Global Admin accounts?

Each Global Admin account is a potential entry point to your entire tenant, including email, files, and security settings. If any one of those accounts is compromised through phishing or an exploited vulnerability like the recent Outlook zero-day, attackers gain full control instead of limited access.

Should service accounts like scanners have Global Admin rights?

No. Service accounts like multifunction printers or scanners should never hold Global Admin privileges; they typically only need a scoped mailbox or application permission to send email. Moving these to app-only authentication with minimal scopes removes a major unmonitored attack surface.

What tool can I use to scan my Microsoft 365 tenant for security gaps?

Oscar Six Security's Radar scan is a $99 assessment designed for small businesses and IT admins to identify misconfigurations like excessive admin privileges, risky OAuth app permissions, and other common M365 exposures. It's a low-cost way to get an outside check before attackers find the gaps first.

Step-by-Step Guide

  1. Export the Global Admin list

    Pull the full current membership of the Global Administrator role in Entra ID before making any changes, so you have a baseline to work from.

  2. Classify every account

    Determine whether each account is a human employee, a former employee, a service account, or a break-glass account, and flag anything that can't be immediately explained.

  3. Cross-reference with HR records

    Check every admin account against current employment status to catch former employees who were never offboarded from privileged roles.

  4. Map roles to minimum required access

    Replace Global Admin with scoped built-in roles like Exchange Administrator, SharePoint Administrator, or Helpdesk Administrator based on each person's actual job function.

  5. Move service accounts to app-only auth

    Reconfigure scanners, printers, and integrations to use scoped API permissions instead of interactive Global Admin logins.

  6. Enable Privileged Identity Management

    If licensing allows, configure PIM so admin roles are activated on-demand and time-bound rather than standing permanently.

  7. Document an ongoing review policy

    Assign clear ownership for admin credential decisions and schedule recurring quarterly reviews to prevent sprawl from regrowing.

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