Blog Post

Microsoft Sentinel Blog
2 MIN READ

How Granular Delegated Admin Privileges (GDAP) allows Sentinel customers to delegate access

Yossi Basha's avatar
Yossi Basha
Icon for Microsoft rankMicrosoft
Mar 20, 2026

Empowering MSSPs and multi-tenant organizations with simplified delegated access: in Public Preview April 16th 2026

Simplifying Defender SIEM and XDR delegated access

As Microsoft Sentinel and Defender converge into a unified experience, organizations face a fundamental challenge: the lack of a scalable, comprehensive, delegated access model that works seamlessly across Entra ID and Sentinel’s Azure Resource Manage creating a significant barrier for Managed Security Service Providers (MSSPs) and large enterprises with complex multi-tenant structures.

Extending GDAP beyond CSPs: a strategic solution

In response to these challenges, we have developed an extension to GDAP that makes it available to all Sentinel and Defender customers, including non-CSP organizations. This expansion enables both MSSPs and customers with multi-tenant organizational structures to establish secure, granular delegated access relationships directly through the Microsoft Defender portal. This is now available in public preview.

The GDAP extension aligns with zero-trust security principles through a three-way handshake model requiring explicit mutual consent between governing and governed tenants before any relationship is established. This consent-based approach enhances transparency and accountability, reducing risks associated with broad, uncontrolled permissions. By integrating with Microsoft Defender, GDAP enables advanced threat detection and response capabilities across tenant boundaries while maintaining granular permission management through Entra ID roles and Unified RBAC custom permissions.

Delivering unified management of delegated access across SIEM and XDR

With GDAP, customers gain a truly unified way to manage access across both Microsoft Sentinel and Defender—using a single, consistent delegated access model for SIEM and XDR. For Sentinel customers, this brings parity with the Azure portal experience: where delegated access was previously managed through Azure Lighthouse, it can now be handled directly in the Defender portal using GDAP. More importantly, for organizations running SIEM and XDR together, GDAP eliminates the need to switch between portals—allowing teams to view, manage, and govern security access from one centralized experience. The result is simpler administration, reduced operational friction, and a more cohesive way to secure multi-tenant environments at scale.

How GDAP for non-CSPs works: the three-step handshake

The GDAP handshake model implements a security-first approach through three distinct steps, each requiring explicit approval to prevent unauthorized access.

Step 1 begins with the governed tenant initiating the relationship, allowing the governing tenant to request GDAP access.

Step 2 shifts control to the governing tenant, which creates and sends a delegated access request with specific requested permissions through the multi-tenant organization (MTO) portal.

Step 3 returns to the governed tenant for final approval.

The approach provides customers with complete visibility and control over who can access their security data and with what permissions, while giving MSSPs a streamlined, Microsoft-supported mechanism for managing delegated relationships at scale.

Step 4 assigns Sentinel permissions.

In Azure resource management, assign governing tenant’s groups with Sentinel workspaces permissions (in the governed tenant), selecting the governing tenant’s security groups used in the created relationship.

 

Learn more here: Configure delegated access with governance relationships for multitenant organizations - Unified se…

Updated Apr 16, 2026
Version 5.0

14 Comments

  • Jess_Chappel's avatar
    Jess_Chappel
    Copper Contributor

    Which tenant types is this in public preview for? Commercial? GCC Moderate? GCC High?

    • Saggie's avatar
      Saggie
      Icon for Microsoft rankMicrosoft

      At the moment, only Commercial clouds are supported.

      • magosta91's avatar
        magosta91
        Copper Contributor

        is there a timetable for when this will in public preview for general audiences? Our team really want to test and lab this out with our Production tenant and our development tenant. Is there any documentation that will be published for this as well? Some additional guidance for MSSPs?

         

  • louee123's avatar
    louee123
    Copper Contributor

    Any concrete date for when this will be rolling out? Some of our more eager customers are getting frustrated that we still manage their Sentinel implementations via the Azure Portal primarily 😅

    Access via GDAP gives me the temporary user that can't see Log Analytics Workspaces and the delegated permissions via Lighthouse don't cover the Entra ID permissions required to manage it from the Defender Portal (or am i missing something else?)

      • Jordan Mills's avatar
        Jordan Mills
        Brass Contributor

        It seems to be broken.  Attempts to send an invitation just return an immediate error:

        Failed to send invitation request

        Failed to send governance invitation.

  • Patsy's avatar
    Patsy
    Copper Contributor

    This is great, and timing is spot on. Been trying to solution for this last few weeks. Meaning for existing CSPs, same process to establish the relationship, but GDAP permissions will become available as part of the UBAC in defender?

     

    • Saggie's avatar
      Saggie
      Icon for Microsoft rankMicrosoft

      URBAC in defender support for GDAP is planned in the roadmap :) no firm date yet. 

      • thy's avatar
        thy
        Copper Contributor

        The integration of Sentinel into the Defender portal and its new controllability via GDAP is welcome news for MSSP vendors. However, with the transition to the Defender portal, MSSPs will likely be required by customers to implement appropriate access controls for the Defender solution as well. Therefore, could you please clarify the schedule for making URBAC compatible with GDAP? MSSPs need to explain the authentication and authorization mechanisms to their customers and determine whether to use Entra B2B or GDAP. Once the authentication and authorization mechanism has been implemented and the migration to the Defender portal is complete, it will be difficult to change the authentication and authorization mechanism. Therefore, we would prefer that the Sentinel portal’s EOL be postponed until GDAP+URBAC is released and MSSPs are able to support it.