Granular delegated admin privileges (GDAP) API overview

Namespace: microsoft.graph

As part of the Microsoft Partner Center ecosystem, Microsoft partners in the Cloud Solution Provider, Value Added Reseller, or Advisor programs can perform administrative operations on their customer tenants to help manage the customer's services, for example, Microsoft Entra ID and Microsoft 365. This capability previously allowed partners to assume a Global Administrator role in the customer tenant indefinitely, creating potential security exposures and limiting market potential.

Granular delegated admin privileges (GDAP) provide partners with least-privileged access to their customer tenants following the Zero Trust cybersecurity model. Through GDAP, partners configure and request granular and time-bound access to their customers' environments, and customers must explicitly grant this least-privileged access to partners. In addition, partners must request specific roles for customer tenant administration for a definite amount of time. This control eliminates the need for partners to have the Global Administrator role in their customer's tenant but rather, they now have lesser privileged permissions that they absolutely need for delegated administrative tasks.

For more information about GDAP, see:

• Introduction to granular delegated admin privileges (GDAP)
• Least-privileged roles by task

GDAP workflow

Lifecycle of a GDAP relationship

The following diagram shows the status of the Delegated Admin relationship transitions.

1. Create delegatedAdminRelationship
2. Update delegatedAdminRelationship
3. Create delegatedAdminRelationshipRequest (action: lockForApproval)
4. Create delegatedAdminRelationshipRequest (action: terminate)

After running the Create delegatedAdminRelationshipRequest API with the lockForApproval action, build the customer invitation link by using the following URI template, where {adminRelationshipID} is the ID of admin relationship request.

https://admin.microsoft.com/AdminPortal/Home#/partners/invitation/granularAdminRelationships/{adminRelationshipID}

Send the invitation link to the customer for them to approve the GDAP request. For example, https://admin.microsoft.com/AdminPortal/Home#/partners/invitation/granularAdminRelationships/5d027261-d21f-4aa9-b7db-7fa1f56fb163-8777b240-c6f0-4469-9e98-a3205431b836 is an invitation link, where 5d027261-d21f-4aa9-b7db-7fa1f56fb163-8777b240-c6f0-4469-9e98-a3205431b836 is the admin relationship request ID. After the customer approves the GDAP request, the GDAP relationship will transition to an active state.

To finalize the workflow for enabling admin on behalf of (AOBO) management of the customer's tenant, proceed by creating a new access assignment for the delegated admin relationship by using the Create accessAssignments API.

Lifecycle of a GDAP relationship access assignment

The delegated admin access assignment goes through the status transitions shown in the following diagram.

1. Create delegatedAdminAccessAssignment
2. Delete delegatedAdminAccessAssignment

Use cases for GDAP APIs

This section describes the ways that Microsoft partners can use the GDAP APIs to programmatically manage delegated admin relationships for their customers.

Delegated admin relationship

Delegated admin relationship request

Role assignments

Long-running operations

Delegated admin customers

Permissions

To manage delegated admin relationships, the calling principal must be in the partner tenant and be granted the appropriate granular delegated admin privileges permissions.

Zero Trust

This feature helps organizations to align their identities with the three guiding principles of a Zero Trust architecture:

• Verify explicitly
• Use least privilege
• Assume breach

To find out more about Zero Trust and other ways to align your organization to the guiding principles, see the Zero Trust Guidance Center.

Related content

• Introduction to granular delegated admin privileges (GDAP)