Key Points
- Microsoft has replaced DAP with GDAP, which gives MSPs least-privilege, time-bound access that the customer approves and that aligns with zero trust principles.
- Use Microsoft 365 Lighthouse to centralize GDAP management across tenants and reduce manual overhead.
- Assign built-in Entra roles to security groups to enforce least-privilege role-based access control (RBAC) and avoid unnecessary use of Global Admin accounts.
- Deploy GDAP templates with expiry policies to standardize access durations and reduce long-lived elevated sessions.
- Automate tracking and governance using Microsoft Graph API, PowerShell, or integrated RMM tools to maintain visibility and compliance.
- Conduct regular GDAP access audits during quarterly business reviews (QBRs) to remove stale privileges and confirm role relevance.
This guide explains how to build a clean delegated access model for client tenant management. Setting up granular delegated admin privileges (GDAP) in Microsoft 365 is a necessity for IT teams and managed service providers (MSPs) that manage multiple tenants. GDAP helps mitigate the risks present in legacy delegated administrative privileges (DAP) by avoiding blanket Global Admin access to customer tenants, instead using least-privilege access that recognizes zero trust best practices.
Maintain real-time security tracking and administrative visibility across every managed tenant.
What is the difference between DAP and GDAP?
DAP gave partners Global Admin–level access to a customer tenant with no expiry date, which made it a cybersecurity concern. Microsoft replaced it with GDAP, which gives partners specific Microsoft Entra roles for a fixed period, approved by the customer.
| Attribute | DAP | GDAP |
| Access scope | Global Admin–level access to the customer tenant | Specific Microsoft Entra roles, set per customer relationship |
| Duration | No expiry | Up to two years, with optional auto-extend of 180 days |
| Customer approval | Not role-specific | Customer approves each request and its roles |
| Who gets access | Partner users in the Admin agents group | Partner users in security groups you map to approved roles |
| Expiry tracking | Not applicable | GDAP relationship analytics and the Expiring Granular Relationships page in Partner Center |
| Availability | Not available with new reseller relationships since October 10, 2023 | Default for new customers |
Prerequisites for Microsoft Partners moving from DAP to GDAP
You need the following to start using GDAP with client Microsoft 365 tenants:
- A cloud solution provider (CSP) relationship with each customer as an indirect reseller, indirect provider, or direct bill partner
- The Admin agent role in Partner Center, which is required to create GDAP relationship requests
- A security group in your Microsoft Entra tenant for each technician tier or workload
- Working knowledge of Microsoft Entra ID (formerly Azure AD) roles and Conditional Access, including how to exclude service provider users from policies that block external access
- Optional: Microsoft 365 Lighthouse for GDAP templates and multi-tenant management
- Optional: a Microsoft Entra ID P2 license to create just-in-time access policies in Lighthouse
- Optional: PowerShell and/or Microsoft Graph API access for automation
A GDAP or DAP relationship is a prerequisite for fully onboarding a customer to Lighthouse, so create the GDAP relationship first. Lighthouse can then set up GDAP templates, but you can also create relationships in Partner Center or with the Partner Center APIs, which is the better route when you need to create many relationships at once.
Is DAP still available, and how do you move to GDAP?
Microsoft stopped offering DAP with new reseller relationships on October 10, 2023, and now grants a default GDAP relationship when a partner creates a new customer. Microsoft’s Partner Center documentation still describes DAP and GDAP coexisting during the transition, with GDAP permissions taking precedence, so some customers may still have a DAP relationship.
If a customer still has DAP, follow this order to remove it:
- Create a GDAP relationship for both Microsoft 365 and Azure.
- Assign Microsoft Entra roles to security groups for both Microsoft 365 and Azure.
- Confirm that GDAP takes precedence and that your technicians can complete their work.
- Remove DAP.
Follow the order exactly for customers with Azure subscriptions. If you remove DAP first or move only Microsoft 365 to GDAP, you can lose access to the customer’s Azure subscriptions.
Building your GDAP access model
A clean granular delegated access model reduces exposure to cybersecurity threats by supporting zero trust principles as well as demonstrates security awareness and operational maturity to your clients.
To build a GDAP access model:
- Define the tasks you perform for each client and group them by technician tier or workload.
- Create a security group in your Microsoft Entra tenant for each tier or workload.
- Choose the least privileged built-in role for each task, using Microsoft’s least privileged roles by task reference.
- Send a GDAP relationship request from Partner Center or assign a Lighthouse GDAP template, with a clear relationship name and the shortest duration that fits the work.
- Ask the customer to approve the request and then assign the approved roles to your security groups.
- Add just-in-time (JIT) access for high-privilege groups and enable auto-extend only on relationships that don’t include Global Administrator.
- Track expiry dates with GDAP relationship analytics and review the model every quarter.
Apply zero trust controls, automated patch compliance, and real-time threat detection from a single console.
Apply role-based access controls (RBAC)
GDAP uses Microsoft Entra built-in roles, so you build granularity with security groups rather than custom roles. Create a security group for each technician tier or workload (such as helpdesk, Intune, or Exchange) and map each group to the least privileged built-in roles for that work. Microsoft publishes the least privileged role for each admin task, which makes a good starting point for your baseline.
Microsoft also recommends removing technicians from the Admin agent role and placing them in GDAP security groups only so they can administer services without managing the customer’s subscriptions. Avoid Global Administrator wherever possible, and when a task requires it, request it as a time-bound role.
Delegate with templates and expiry policies
Predefine the expected duration that delegated sessions should last and use GDAP templates in Lighthouse to standardize access configurations.
A GDAP relationship can last up to two years, and every role in a relationship shares the same expiration date. To give different tasks different durations, create separate GDAP relationships, such as a short one for project work and a longer one for day-to-day support roles. Enable auto-extend to renew a relationship by 180 days at a time until you disable it.
Turning on auto-extend for an active relationship doesn’t require new customer consent, but auto-extend isn’t available for any relationship that includes the Global Administrator role, so keep that role in its own short-lived relationship. A request that the customer doesn’t act on expires after 90 days.
For high-privilege roles, add JIT access. Lighthouse can create a JIT access policy for a security group, which requires a Microsoft Entra ID P2 license, so technicians request the role only when they need it and hold it only for the approved window.
Automate tracking and governance
You should maintain oversight over all delegated access requests and sessions by exporting this data to CSV using Microsoft Graph or PowerShell. You can then create dashboard views for all of your tenants and delegated roles, including permissions and dates. Automated alerts can also be created from this data, so that you can be alerted if a GDAP link is due to expire and needs to be renewed.
These kinds of custom automations can be achieved using a remote monitoring and management (RMM) tool that integrates with Microsoft 365 and supports custom scripting, dashboards, and notifications.
Review and audit your delegated access model regularly
You should regularly review your GDAP model, confirming the following for each delegated role/relationship:
- That each role and relationship is still in use
- That each role is aligned with a current scope of work
- That each is recorded and reviewed by the relevant stakeholders
Unused or stale relationships should be proactively removed. Reviewing your GDAP strategy can be performed as part of your MSP’s quarterly business reviews (QBRs) with clients.
How NinjaOne fits alongside GDAP
Securing multi-tenant environments requires full oversight of all delegated privileges and ensuring that delegated access cannot be used as a vector for attack. This is best done using granular, scoped permissions that recognize the principle of least privilege, combined with time-limits.
GDAP controls who can administer a customer’s Microsoft 365 tenant. NinjaOne RMM covers the other side of client management, giving MSPs one console to monitor, patch, and secure the endpoints in each client environment. Used together, GDAP limits tenant-level access to the roles and time frames each customer approved, while the NinjaOne platform keeps device-level work visible and consistent across clients. NinjaOne also integrates with CrowdStrike, which provides the threat detection.
By taking a considered, structured approach to delegated access in Microsoft 365, you can uphold and enhance client trust as well as ensure administrative sessions are only used for their intended purpose.

