GDAP, Azure Lighthouse or an enterprise app? Least-privilege access to customer tenants
Reviewed by ContraForce
Security Delivery · Tech article · Advanced · 5 min read
How GDAP, Azure Lighthouse and admin-consented Entra ID enterprise apps each give an MSSP access to customer tenants, where each stops, and how to keep that access small and time-bound.
You've just signed a 400-seat manufacturer that runs Microsoft Sentinel and Defender XDR. Your analysts need to work their Sentinel incidents. Your detection engineers need to edit analytics rules now and then. Your help desk will sometimes need to reset a compromised user's password. And the tooling your SOC uses needs to read and update incidents without anyone signed in.
Microsoft gives you three ways to get that access, and they aren't interchangeable. Each covers different work, with different limits and a different audit trail.
What are the three access paths?
- GDAP (granular delegated admin privileges): a Partner Center relationship that gives users in your partner tenant Microsoft Entra roles in the customer's tenant, through security groups, for a set period.
- Azure Lighthouse: the customer delegates a subscription, or resource groups in it, to your managing tenant. Users, groups or service principals in your tenant get Azure built-in roles on those resources.
- A multitenant Entra ID enterprise application: an app registered in its home tenant gets a service principal in the customer's tenant when an admin there consents, with the permissions that admin granted.
What does GDAP cover, and where does it stop?
GDAP grants Microsoft Entra roles. You request a relationship that lists the roles, the customer approves it, and you assign the roles to security groups in your tenant. Members of those groups then sign in to the customer's tenant.
It is time-bound by design. Microsoft caps a relationship at two years, with no permanent option. Auto extend adds six months at a time until it's turned off, but not for relationships that include Global Administrator. Unanswered requests expire after 90 days.
Request roles by task. Microsoft's role guidance names Password Administrator as the least-privileged role for resetting a non-admin's password, and Privileged Authentication Administrator for privileged admins. It advises against replacing Global Administrator with every other Entra role, and suggests a time-bound Global Administrator role only to work around known issues. Put Privileged Identity Management (PIM) on GDAP security groups so people elevate just in time and lose the role automatically.
What does Azure Lighthouse cover, and where does it stop?
Lighthouse is for Azure resources, and Microsoft's guidance for MSSPs managing Sentinel across tenants is built on it. You onboard each customer subscription and assign roles such as Microsoft Sentinel Reader, Responder or Contributor to groups in your tenant. Customer data and costs stay in the customer's tenant.
Lighthouse supports Azure built-in roles only, not custom roles. Owner isn't supported, nor are roles with DataActions, and User Access Administrator can only assign roles to managed identities. Lighthouse users never sign in to the customer's tenant and hold no Entra permissions there, so identity work such as a password reset is out of reach.
For time-bound access, use eligible authorizations. They use PIM, which needs a Microsoft Entra ID Governance license in your managing tenant. Activation lasts from 30 minutes to 8 hours, can require MFA and up to 10 approvers, and can't be given to service principals. Each one needs a permanent Reader authorization for the same principal. Also include the Managed Services Registration Assignment Delete Role, so your side can remove the delegation.
What does a consented enterprise application cover?
An enterprise app is how software, not a person, gets access. Delegated permissions act for a signed-in user and can't reach anything that user couldn't. Application permissions run with no user present, reach everything the permission covers, and only an admin can consent to them.
Consent to Microsoft Graph application permissions needs at least Privileged Role Administrator. Cloud Application Administrator and Application Administrator can grant everything else. Microsoft calls tenant-wide consent a sensitive operation, so judge each app by its permission list, not the vendor's description.
For the consent roles and the review steps, see Microsoft's guide to granting tenant-wide admin consent.
Which path fits which job?
For the manufacturer, it maps out like this:
- Analysts working Sentinel incidents: Lighthouse, with Microsoft Sentinel Responder assigned to your analyst group.
- Detection engineers editing analytics rules: Lighthouse, with Microsoft Sentinel Contributor as an eligible authorization.
- Help desk resetting a non-admin user's password: GDAP, with Password Administrator on a PIM-enabled security group.
- Tooling that reads and updates incidents unattended: an enterprise app with the narrowest application permissions its publisher documents.
Each path is removed separately
Microsoft describes GDAP and Lighthouse as decoupled, parallel paths: removing one doesn't affect the other. Consented apps are separate again. When a customer leaves, end the GDAP relationship, remove the Lighthouse delegation and remove the enterprise apps, and confirm each one is gone.
How do you audit each path?
For Lighthouse, the customer's Azure Activity log records the actions your users take on delegated resources, with the user's name but not their tenant or role. The portal shows 90 days, and the customer can store it longer. PIM activations appear in your tenant's audit log and in the customer's activity log.
For GDAP, Partner Center activity logs show when a customer removes a relationship, and the Expiring Granular Relationships page tracks upcoming expiries.
For enterprise apps, the Enterprise applications page in the customer's tenant shows each app's granted permissions, user consents and sign-in information.
Microsoft lists what customers can see in Monitor service provider activity.
A least-privilege checklist for each new customer
- List the jobs your team does in this tenant and pick a path for each.
- Request GDAP roles by task from the role guidance. Leave Global Administrator out unless a documented issue needs it, and then only for a limited time.
- Assign GDAP roles and Lighthouse authorizations to security groups rather than individual accounts, wherever you can.
- Put PIM on GDAP groups that hold password or authentication roles.
- Make write roles such as Microsoft Sentinel Contributor eligible authorizations, with MFA required, and pair each with a permanent Reader authorization.
- Include the Managed Services Registration Assignment Delete Role in every Lighthouse delegation.
- Read every enterprise app's permission list before consent. Have the customer's Privileged Role Administrator activate the role for the consent, then deactivate it.
- Decide whether auto extend is on for each relationship, and record the expiry date.
- Agree Activity log retention with the customer, and set alerts for critical operations.
- Write the offboarding steps for all three paths when you onboard the customer.
How does ContraForce connect to a customer tenant?
ContraForce connects through purpose-built enterprise applications in the customer's Entra ID tenant, each with only the permissions its function needs. Two core applications are needed for every deployment. The rest are consented per module from the workspace's Modules tab, so you only grant permissions for the capabilities you use. Because they use app-only Microsoft Graph permissions, consent needs a Global Administrator or Privileged Role Administrator, and the docs recommend activating that role just in time with PIM.
Consenting the Microsoft Sentinel module also sets up an Azure Lighthouse delegation and incident-streaming resources in the customer's subscription, which needs Subscription Owner.
The full list of applications, app IDs and permissions is in the Enterprise Application Permissions guide.
What the Sentinel module deploys, and the prerequisites, are in the Microsoft Sentinel Module Deployment guide.
Keep learning
- Getting started: connect your first customer workspace. Pre-onboard a customer in the Workspace Center, send the invite, have their admin grant the core and module consents, then confirm the workspace is live with the onboarding checklist.
- Controlling Microsoft Sentinel costs across customer workspaces. How to keep Microsoft Sentinel spend under control in each customer workspace: table tiers, commitment tiers, retention, ingestion-time filtering, free data sources and usage monitoring.
- Writing incident response SOPs that analysts and AI agents can both follow. A structure for incident response SOPs that analysts and AI agents can follow the same way: decisions as explicit conditions, per-customer exceptions, versioning and a suspicious sign-in example.
Sources
- Microsoft Learn, GDAP frequently asked questions, verified 2026-11-20
- Microsoft Learn, GDAP role guidance, verified 2026-11-20
- Microsoft Learn, Tenants, users, and roles in Azure Lighthouse scenarios, verified 2026-11-20
- Microsoft Learn, Create eligible authorizations (Azure Lighthouse), verified 2026-11-20
- Microsoft Learn, Manage Microsoft Sentinel workspaces at scale, verified 2026-11-20
- ContraForce Docs, Enterprise Application Permissions and App IDs, verified 2026-11-20