Your IT provider is Global Administrator: how to review partner access in Microsoft 365
Key takeaways
- An IT provider can be an administrator in your Microsoft 365 tenant in three ways: through the legacy DAP model, through GDAP, or through its own accounts in your directory. You should know about all three.
- DAP gives the partner the Global Administrator role with no end date. Microsoft has not granted DAP to new customers since 25 September 2023, but older relationships may still exist.
- GDAP is limited to a maximum of two years and contains only the roles you approved. Relationships that include Global Administrator cannot be extended automatically.
- You can see which partners hold which roles in the Microsoft 365 admin center under Settings > Partner relationships. These assignments do not appear in the role lists of the Entra admin center.
- The contract should cover named accounts, MFA, time-limited privileges, access to logs and a defined offboarding process.
Most mid-sized companies have Microsoft 365 run by an external IT provider. That makes sense: few businesses with 80 employees need their own administrator. It also means that people outside your company hold the keys to mailboxes, files and user accounts. This article shows how to make that access visible, reduce it to what is needed and secure it in the contract. It complements our general article on how to tell whether your IT provider runs Microsoft 365 securely.
In which ways can your IT provider hold admin rights?
There are three technical routes, and many tenants have more than one in place at the same time.
| Route | How it is created | Rights | Duration | Where you see it |
|---|---|---|---|---|
| DAP (delegated admin privileges) | When a cloud solution provider (CSP) set you up as a customer, automatically until September 2023 | Global Administrator and Helpdesk Administrator | no end date, until either side revokes it | Microsoft 365 admin center > Settings > Partner relationships |
| GDAP (granular delegated admin privileges) | The partner sends a request, a Global Administrator in your tenant approves it | only the Entra roles requested | 1 to 730 days | same page, details per relationship |
| Own accounts in your tenant | The provider creates an account such as [email protected], or is invited as a guest | any role assigned | no end date | Entra admin center > Roles and administrators |
With DAP and GDAP, technicians sign in with accounts from the provider’s own tenant. They therefore do not appear in your user list. With own accounts it is the other way round: they are visible, but often not tied to an individual. Microsoft explicitly recommends against shared administrator accounts.
What is the difference between DAP and GDAP?
DAP is all or nothing. Once a customer accepts the invitation, the partner can give the Global Administrator role for that tenant to as many of its own staff as it likes. As the customer, you have no say in that; you can only grant or revoke DAP. Microsoft gives exactly these two properties as the reason for retiring DAP: the privileges are very high and last indefinitely. That makes providers an attractive target, because one compromised partner opens the door to many customers.
GDAP changes three things:
- Roles instead of full access. Each relationship contains a list of Entra roles, such as Helpdesk Administrator or Exchange Administrator. Global Administrator is possible but no longer the default.
- Time limits. A GDAP relationship runs for at most 730 days. The partner can turn on automatic extension by six months at a time; for relationships that include Global Administrator this is not possible.
- Assignment to groups. The partner assigns the roles to security groups in its own tenant. It can use Privileged Identity Management (PIM) for these groups, so technicians activate high privileges only on request and for a short time.
“We use GDAP” is not a sufficient answer on its own. For newly created customers, Microsoft sets up a default GDAP relationship that, depending on the partner type, contains several roles, including Privileged Role Administrator and Privileged Authentication Administrator. The first can assign further roles, the second can reset sign-in methods, including those of administrators. In effect, both come close to Global Administrator. What matters is which roles the relationship contains.
Where can you see which partners have access to your tenant?
Sign in with an account that holds the Global Administrator role.
- Open Partner relationships. In the Microsoft 365 admin center under Settings > Partner relationships, you see every partner, the relationship type and the roles. If the Roles column shows Global Administrator for a reseller relationship, DAP is still in place. Selecting a partner shows the individual GDAP roles and the end date.
- Do not rely on the Entra admin center. Roles granted through DAP or GDAP cannot be found in the role lists of the Entra admin center, through PowerShell or through Microsoft Graph. Microsoft explicitly points customers to the Partner relationships page instead. The Entra admin center and the Azure portal also have a “Delegated administration” page that flags existing relationships.
- Look for the provider’s own accounts. In the Entra admin center under Roles and administrators > Global Administrator, you see all directly assigned accounts. Watch for accounts without a person’s name and for guest accounts from your provider’s domain.
- Review sign-ins. In the sign-in logs in the Entra admin center, filter the “Cross tenant access type” column to “Service provider”. This shows when partners signed in and to which applications.
If you send the sign-in logs to a Log Analytics workspace or to Microsoft Sentinel through a diagnostic setting, this query gives an overview of the last 30 days:
union SigninLogs, AADNonInteractiveUserSignInLogs
| where TimeGenerated > ago(30d)
| where CrossTenantAccessType == "serviceProvider"
| summarize SignIns = count(), Latest = max(TimeGenerated)
by HomeTenantId, AppDisplayName
| order by SignIns desc
Microsoft recommends reviewing partner privileges quarterly. Put a fixed date in the calendar and document the result.
Which roles does your IT provider actually need?
That depends on what the contract says it does. For typical tasks in a mid-sized company, much less privileged roles than Global Administrator are enough:
| Task | Suitable role |
|---|---|
| Reset passwords of regular users | Helpdesk Administrator |
| Create users and groups | User Administrator |
| Assign licences | License Administrator |
| Open support cases with Microsoft | Service Support Administrator |
| Manage mailboxes and distribution lists | Exchange Administrator |
| Manage devices and policies in Intune | Intune Administrator |
| Review configuration without changing it | Global Reader |
Global Administrator belongs in a separate, short GDAP relationship for a specific project, such as a migration, and should expire afterwards. Microsoft itself advises partners to request Global Administrator only on a time-limited basis and in agreement with the customer. Some of the roles above are powerful too: an Exchange Administrator can, for example, grant themselves access to mailboxes. Each role should therefore have a stated reason in the contract.
Why are permanent Global Administrator accounts a supply chain risk?
An IT provider serves many customers with the same tools and often the same technicians. Whoever compromises the provider reaches every customer whose tenant is permanently open to it. In assessments we often see the same patterns: a shared “admin@…” account whose password sits in the provider’s password manager, MFA on a company phone used by several technicians, and no record of which person changed what and when. When a technician leaves the provider, in the worst case they still know a valid password.
For management this is not purely a technical matter. Organisations covered by Germany’s NIS2 implementation must address supply chain security, including relationships with their direct suppliers and service providers, under § 30(2) no. 4 of the BSI Act (BSIG). Even without NIS2 obligations, cyber insurers and large customers increasingly ask who has administrative access. A list of partner access with roles and end dates answers that question in minutes.
What should you agree with your IT provider in the contract?
These points belong in the contract or in an annex to the service description:
- Named access. Administrative access is through GDAP or through personal, named accounts. Shared accounts are excluded. The provider keeps a current list of the people with access.
- Role list with justification. The GDAP roles are written into the contract. Global Administrator is granted only for a named project and for a limited time.
- MFA and time-limited privileges. All technicians sign in with phishing-resistant MFA. High-privilege roles are activated through PIM only when needed. In your own tenant, you can target Conditional Access policies specifically at the external user type “Service provider users”.
- Logs and reporting. Logs stay in your tenant and you have read access at all times. The provider reports regularly on administrative changes.
- Incidents at the provider. If the provider itself is attacked, it informs you within an agreed period, even if it is not yet clear whether your tenant is affected.
- Offboarding. When a technician leaves, they are removed from the security groups within an agreed period. At the end of the contract, GDAP relationships are terminated, own accounts deleted and emergency access credentials reset.
- Right to audit. You may review the access yourself or have a third party do so.
A reputable provider will not object to these points, because they protect the provider too: clear roles and logs show who changed what if there is ever a dispute.
Next step
If you want to know which privileged roles and partner access exist in your tenant, our security assessment checks this at a fixed price, as an independent second opinion alongside your provider. The subsequent hardening of roles, PIM and Conditional Access is described on our Microsoft 365 hardening page.
Frequently asked questions
Can I remove DAP without stopping my provider from working?
Yes, provided a GDAP relationship with the necessary roles is in place first. Under Settings > Partner relationships, select the partner and choose “Remove roles”. The reseller relationship and your licences are not affected. The partner can still order licences on your behalf afterwards. If you do not want that, raise it with them directly.
What happens when a GDAP relationship expires?
Technicians in the assigned security groups lose access; your subscriptions continue unchanged. You and the partner receive email notifications before expiry. An expired relationship cannot be reactivated; the partner has to request a new one.
Can my provider read my email?
With Global Administrator or Exchange Administrator, they can grant themselves access to mailboxes. Whether anyone has assigned mailbox permissions is recorded in the audit log in Microsoft Purview. If you limit the roles and review the logs, you do not have to rely on assurances.
How often should I review partner access?
Microsoft recommends a quarterly review. A review is also worthwhile whenever your contact at the provider changes and before every contract renewal.
Book an introductory call