Blog
GDAP, Partner Center and Lighthouse: what each one governs in a multi-tenant practice
Learn what GDAP, Partner Center, Azure Lighthouse and Microsoft 365 Lighthouse govern, and how to manage renewals across 20 to 100 tenants.
Nerdio is Microsoft’s 2026 Americas ISV Partner of the Year Get the story
Blog
Learn what GDAP, Partner Center, Azure Lighthouse and Microsoft 365 Lighthouse govern, and how to manage renewals across 20 to 100 tenants.
Table of Contents
If a technician at your managed service provider (MSP) learns on Tuesday that a client's granular delegated admin privileges (GDAP) relationship expired, the customer's Global Administrator must approve a new request because expired relationships can't be restored.
Lockouts like that come from managing four separate control layers as one. GDAP and Azure Lighthouse are decoupled delegated-access paths, according to Microsoft's GDAP FAQ. Microsoft 365 Lighthouse covers Microsoft 365 services, and Partner Center holds the commercial relationship and the GDAP request flow. Each layer needs its own owner and its own renewal check before the next expiry notice.
This guide is for MSP owners and practice leads running a multi-tenant Microsoft 365 practice of 20 to 100 tenants under the Cloud Solution Provider (CSP) program. It maps what each layer governs, where its permissions live, and what to check before GDAP renewals come due.
GDAP gives CSP partners least-privileged, time-bound access to a customer's tenant that the customer must explicitly grant. Microsoft's GDAP introduction calls it a security feature that follows the Zero Trust protocol.
The Microsoft Entra delegated administration primer explains how that access works in practice. Your technicians use the same Entra roles as the customer’s own administrators. Those roles are assigned to security groups in your CSP tenant, which is why your technicians don’t need user accounts in the customer tenant.
The predecessor, delegated admin privileges (DAP), gave the Admin Agent group standing Global Administrator in every customer tenant until revoked. Microsoft's GDAP migration FAQ says DAP "is susceptible to security attacks due to its longevity and high privileged access."
In October 2021, Microsoft reported NOBELIUM targeting delegated administrative privileges at cloud service providers and MSPs. Microsoft notified over 140 resellers and technology service providers and said as many as 14 had been compromised. That attack history is the operational case for replacing standing Global Administrator access with narrower, time-bound roles.
Since October 10, 2023, new customers created in Partner Center get Default GDAP instead of DAP. The GDAP FAQ says GDAP will "eventually" replace DAP without giving a retirement date, so DAP may linger in older tenants until you remove it.
Every GDAP relationship carries the same four fields, and the choices you make at request time determine what you can do later without going back to the customer.
Each relationship request sets four things:
Together, these settings define how long the relationship lasts, which roles it carries, and whether it extends. Approved roles map to security groups, up to 100 per customer.
Picking the right roles up front is what keeps technicians out of Global Administrator by default. Microsoft's role guidance by task suggests these tier-1 defaults:
This role split gives tier-1 technicians task-specific access without defaulting to Global Administrator. The GDAP FAQ advises against swapping Global Administrator for every available role, and relationships containing Global Administrator can't auto-extend.
Microsoft supports Privileged Identity Management (PIM) on GDAP security groups in your partner tenant, so technicians can elevate just in time and lose the role automatically. Microsoft 365 Lighthouse's Delegated access page includes a capability to set up just-in-time (JIT) access.
The Partner Center import in Nerdio Manager for MSP includes a "Select GDAP State" filter showing which customers already have an active relationship.
A reseller relationship, which the customer accepts through an invitation link in the Microsoft 365 admin center, lets you purchase. Managing the service takes a separate admin relationship. GDAP isn't required to fulfill orders, and terminating GDAP doesn't end the reseller relationship.
An Admin Agent submits the GDAP request from the customer's Admin relationships page. The customer's Global Administrator approves it. Per Microsoft's GDAP migration FAQ, acceptance writes a cross-tenant access policy into the customer tenant that only the GDAP service principal can modify.
A pending request can't be terminated by the partner and expires after 90 days of customer inaction. After approval, Partner Center becomes a set of links. Under GDAP, you do the work in the workload's portal, such as Intune.
Partner Center's security requirements make multifactor authentication (MFA) mandatory for every user in the partner tenant, with no exclusions, and non-compliance can cost you customer tenant access. From April 2026, all app+user calls to Partner Center application programming interfaces (APIs) require MFA. Any custom integration or PowerShell automation must use the Secure Application Model.
Azure Lighthouse and Microsoft 365 Lighthouse share a name but govern different planes.
Azure Lighthouse lets your tenant manage a customer's Azure subscriptions and resource groups through Azure role-based access control (RBAC), without accounts in the customer tenant. A Microsoft Tech Community post scopes it to the Azure Resource Manager control plane, with no Entra directory roles and no reach into Microsoft 365 or data planes.
Microsoft's Cloud Adoption Framework recommends using Azure Lighthouse for admin-on-behalf-of (AOBO) access in many support scenarios. With AOBO, any user with the Admin Agent role in your partner tenant gets access to the Azure subscriptions you create through CSP. AOBO can't split that access into separate groups by customer or assign different roles to different groups.
For GDAP, the GDAP FAQ recommends a security group such as "Azure Managers" nested under the Admin Agent group, which grants Owner RBAC on the customer's subscriptions with only a low directory role.
Microsoft's Azure Virtual Desktop FAQ defines Azure Lighthouse's scope for Azure Virtual Desktop management. Cross-tenant user management remains outside that scope, so user work still requires signing in to the customer's Entra ID.
Nerdio Manager extends these Microsoft capabilities with multi-tenant management from one console across client environments.
When CSP partners manage Microsoft 365 across customers, they can use Microsoft 365 Lighthouse as a free standalone portal to aggregate device compliance, risky users, Secure Score, and alerts. Microsoft requires two permission layers. Lighthouse RBAC in your partner tenant controls who can use the portal, while Entra roles delivered through GDAP control what customer data they see.
Microsoft's Requirements page lists four conditions for full functionality:
Tenants that miss any condition get limited experiences, such as GDAP setup, user search, and service health. A Microsoft 365 Lighthouse blog post notes that "the full value of Lighthouse is realized through products such as Microsoft 365 Business Premium." Lighthouse also has a Delegated access page that assigns reusable GDAP templates by support tier and shows nearest expiry.
Some MSPs also run the CyberDrain Improved Partner Portal (CIPP), an open-source multi-tenant tool, alongside Microsoft 365 Lighthouse. CIPP connects to customer tenants through GDAP and uses scoped Microsoft Graph permissions. The roles in each relationship still decide what CIPP can reach in that client's tenant.
Azure resource work runs through Azure Lighthouse or the Azure Managers group, while Microsoft 365 work runs through GDAP Entra roles. These layers remain separate.
Relationship renewals, baseline drift, and retiring APIs all land on the same calendar, and once you pass about 50 tenants, keeping them in sync by hand stops being realistic.
If you onboarded tenants in waves over the last two years, their relationships now come due in waves too, each on its own date. Every GDAP relationship has one expiration date for all its roles, and a missed expiry becomes a customer-approval event. Auto-extend adds six months at a time without new consent, though not for Global Administrator relationships.
In Partner Center, the Expiring Granular Relationships page in the Customers workspace lets Admin Agents turn auto-extend on or off for up to 25 relationships at a time, according to Microsoft's guide to extending GDAP. With auto-extend off, Partner Center sends expiry notices 30 days, 7 days, and 1 day before a relationship expires. Microsoft's Lighthouse team wrote: "With this granularity comes complexity in managing the right roles for the right customer and your agents."
The GDAP FAQ also notes that guest accounts don't work with GDAP, and a partner user can't hold both a GDAP role and a guest account. It recommends removing agents from the Admin Agent role and leaving them only in GDAP security groups, allowing them to administer but not purchase. That means support-tier group design across dozens of customer relationships, within the 100-group-per-customer cap.
Role design isn't the only thing that drifts over time. Policy baselines do too, and Microsoft 365 Lighthouse's handling of them has its own trade-offs.
Microsoft 365 Lighthouse baselines deploy core policies across tenants and report drifted settings. Assigning a new baseline overwrites tenant customizations such as task dismissals and user exclusions, which must be re-entered per tenant.
With Solution Baselines, Nerdio Manager extends this Microsoft foundation by configuring baselines across Defender for Endpoint, Entra ID, Exchange Online, Intune, and Teams and assigning them to accounts. You then detect and review configuration drift across those accounts.
Baseline maintenance isn't the only lifecycle work on the calendar. Older Microsoft APIs and modules are also being retired:
For an MSP, those retirement dates put scripts built on the older APIs and modules on the same operating calendar as relationship renewals.
Keeping relationships, baselines, and scripts current across 50 tenants by hand is where a multi-tenant management layer earns its place.
A September 2025 release refactored how Nerdio Manager's Partner Center integration processes large bulk GDAP requests. After onboarding, most Nerdio Manager actions run on behalf of its app registration in the customer tenant rather than a technician's user permissions. GDAP requests raised through Nerdio Manager carry Name, Auto-Extend, and Duration in days fields.
Nerdio Manager's RBAC narrows each technician's view by assigning only the permissions that technician needs. Cross-tenant license right-sizing runs alongside baseline management, which matters when a client has excess Business Premium seats relative to the people signing in.
Nerdio's onboarding estimates put tenant access and security setup at 4 hours DIY versus 1 hour with Nerdio Manager. The 3-hour difference across 50 tenants is 150 technician hours on access and security setup alone.
For the practice owner, the decision is which layer owns each permission and who owns its renewal. A technician hitting a Tuesday permissions error because a GDAP relationship expired is the immediate symptom of treating four separate control layers as one.
To prevent that lockout from becoming another customer-approval event, run this check against every tenant before renewals come due.
| Layer | What it governs | Where permissions live | What to check |
| Partner Center | Reseller relationship and GDAP requests | Partner tenant (Admin Agent) | Relationship status, Global Administrator inclusion, and auto-extend setting |
| GDAP | Entra roles in each customer tenant | Security groups in your partner tenant | Tier-1 roles match assigned tasks; an Azure Managers group nested under Admin Agents provides AOBO subscription access |
| Azure Lighthouse | Azure RBAC on subscriptions and resource groups | Your tenant, via delegated authorizations | Unaffected if the GDAP path is blocked; no Microsoft 365 reach |
| Microsoft 365 Lighthouse | Cross-tenant views and baseline deployment | Lighthouse RBAC plus GDAP roles | Which tenants meet eligibility |
An MSP running 20 to 100 tenants can prevent repeat lockouts by mapping the four layers separately and running GDAP renewals ahead of the 30-day notice.
A cross-tenant GDAP state view makes relationship status visible before renewal work starts. Explore Nerdio Manager for MSP to see its Microsoft 365 management across client tenants, or try the self-guided demo.
GDAP, or granular delegated admin privileges, gives CSP partners least-privileged, time-bound access to a customer's tenant. An Admin Agent requests it in Partner Center, and the customer's Global Administrator approves it.
DAP gave the Admin Agent group standing Global Administrator until revoked; GDAP grants specific Entra roles for up to two years. Where both exist, GDAP takes precedence, so a DAP Global Administrator paired with a GDAP Global Reader yields only Global Reader.
GDAP delivers Entra directory roles inside the customer tenant; Azure Lighthouse delivers Azure RBAC on subscriptions and resource groups. Microsoft's GDAP FAQ calls them decoupled parallel paths, and Azure Lighthouse never reaches Microsoft 365 workloads.
A GDAP request can set a duration from 1 to 730 days, and auto-extend adds six months at a time without new customer consent. Relationships containing Global Administrator can't auto-extend, and expired relationships can't be restored.
Learn more about Nerdio Manager