Edit

Add agentIdentityBlueprint sponsors

Namespace: microsoft.graph

Important

APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.

Add a sponsor to an agentIdentityBlueprint object. Sponsors can include users or groups. Sponsors may not include service principals or agent users.

A single blueprint may have up to 100 sponsors. No more than 5 sponsors may be groups. Only groups with dynamic membership or Microsoft 365 groups are supported as sponsors. Role-assignable groups can't be set as sponsors.

Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.

Permission type Least privileged permission Higher privileged permissions
Delegated (work or school account) Application.ReadWrite.All. Not available.
Delegated (personal Microsoft account) Not supported. Not supported.
Application Application.ReadWrite.All. Not available.

Important

  • A principal who creates a blueprint or blueprint principal is assigned as the owner. Owners can create agent identities and modify only the resources they own, even if they aren't assigned an Agent ID role.
  • For nonowners to call this API in delegated scenarios using work or school accounts, the admin must be assigned a supported Microsoft Entra role. This operation supports the following built-in roles, which provide only the least privilege necessary:
    • Agent ID Administrator.
    • Agent ID Developer - Create agent identity blueprints and blueprint principals.

HTTP request

POST /applications/{id}/microsoft.graph.agentIdentityBlueprint/sponsors/$ref

Request headers

Name Description
Authorization Bearer {token}. Required. Learn more about authentication and authorization.
Content-Type application/json. Required.

Request body

In the request body, supply a reference to the directoryObject object to be added as a sponsor.

Response

If successful, this method returns a 204 No Content response code and a supported directoryObject object in the response body.

Examples

Request

The following example shows a request.

POST https://graph.microsoft.com/beta/applications/{id}/microsoft.graph.agentIdentityBlueprint/sponsors/$ref
Content-Type: application/json

{
  "@odata.id": "https://graph.microsoft.com/beta/directoryObjects/{sponsor-object-id}"
}

Response

The following example shows the response.

HTTP/1.1 204 No Content