• CISO
  • CIO
  • CFO
4 min readBy Rullan Scott TechnologiesLast verified

Who Holds Admin Access to Your Microsoft Tenant?

THE SHORT ANSWER

Open the Partner relationships page in your Microsoft 365 admin center and list every partner with admin roles in your tenant. Microsoft's current model, GDAP, grants time-limited roles that you approve and can remove. Then count your Global Administrators, aiming for fewer than five, and check that your MSP contract says how access ends when you leave.

On this page

A company changed managed service providers two years ago. When a new IT manager opens the admin center, the old provider still appears under partner relationships.

At the same time, the new provider asks for Global Administrator rights "to make onboarding easier." Nobody can say how many people outside the company can change settings in the tenant today.

How do partners get admin access today?

Microsoft's current model is granular delegated admin privileges (GDAP). Microsoft describes it as "granular and time-bound access" that customers "must explicitly grant." Key rules:

  • "The maximum duration of a GDAP relationship is two years." Permanent relationships aren't possible.
  • Since September 25, 2023, new customers get GDAP instead of the older delegated admin privileges (DAP) model. During the transition the two can coexist, so older tenants may still have DAP relationships.
  • A relationship can auto-extend by six months, but "you can't automatically extend a GDAP that has the Microsoft Entra role of Global Administrator."

How do you see and remove partner access?

In the Microsoft 365 admin center, open the Partner relationships page. Select a partner to see its roles. To end access, select the partner, choose Remove roles, and confirm. After that, members of the partner's mapped security group "no longer have access to administer services."

How many Global Administrators should you have?

Microsoft recommends assigning the Global Administrator role "to fewer than five people in your organization." It also recommends two cloud-only emergency access accounts with that role, not assigned to specific individuals, and multifactor authentication for every administrator account. Count partner and service accounts in the total, not just staff.

What should you check?

Access typeWhat to look forWhat to do
Partner relationships (GDAP)Partners you no longer work with, or roles broader than the work needsRemove old partners; narrow roles for current ones
Older DAP relationshipsAny partner access that predates GDAPReplace with GDAP, scoped to the roles needed
Partner user accounts inside your tenantGuest or member accounts created for MSP staffDisable accounts no longer needed
Global AdministratorsMore than four, including service accountsMove people to narrower admin roles
Emergency access accountsNone, or tied to a named personSet up two cloud-only accounts with strong protection

What should your MSP contract say?

A May 2022 joint advisory from the US, UK, Australian, Canadian and New Zealand cyber agencies (AA22-131A) sets out what customers should expect:

  • Contracts should "transparently identify ownership of ICT security roles and responsibilities."
  • Contracts should "require MFA to be enforced on all MSP accounts used to access customer environments."
  • Customers should "Verify, via audits, that MSP accounts are being used for appropriate purposes and activities."
  • Customers should "disable MSP accounts that are no longer managing infrastructure."
  • Organizations should store their most important logs "for at least six months."

The agreement should also cover exit. Make sure it says who owns the admin accounts, how documentation is handed back, and that partner roles are removed on the last day of the contract.

Why does this matter?

An MSP's access reaches every customer it manages. In July 2021, attackers used Kaseya's VSA remote management tool to reach managed service providers "and their downstream customers." Limiting what each partner can do in your tenant limits what an attacker can do through them.

Three checks you can run

CheckWhat a pass looks likeWhat a fail looks like
Does every partner in Partner relationships have a current contract and only the roles it needs?Each relationship matched to a contract and scoped to the workFormer providers still listed, or broad roles nobody can explain
Do you have fewer than five Global Administrators, counting partner and service accounts?Four or fewer, plus two documented emergency access accountsMore than four, or nobody has counted
Does your MSP contract say how admin access is removed and handed back when it ends?Exit steps written into the contract, with a named owner on each sideNo exit terms, or "to be agreed"

Questions we hear

Is GDAP safer than the old delegated admin model?

GDAP is designed around least privilege: access is time-bound, limited to specific roles and approved by the customer. The older DAP model gave much broader standing access. During the transition both can exist, so check your tenant for any DAP relationships that predate GDAP and replace them.

Should our MSP ever have Global Administrator rights?

Rarely, and only for a defined task. Most day-to-day work can be done with narrower roles. Microsoft won't auto-extend a GDAP relationship that includes Global Administrator, so if you grant it, it must be renewed deliberately. That makes it a natural checkpoint to ask whether it's still needed.

What if we remove a partner's access and something breaks?

Agree the change with your current provider and schedule it. Removing roles ends access for that partner's mapped group, so anything they run on your behalf may stop. That is why it should be tested and documented before a contract ends.

How long should we keep logs of MSP activity?

The joint advisory AA22-131A recommends that organizations store their most important logs for at least six months. Those logs are how you check what partner accounts did, and they are often needed when investigating an incident that started some time before it was noticed.

Sources

Take the eight-question Third-Party Risk assessment