Update multiTenantOrganizationJoinRequestRecord

Namespace: microsoft.graph

Join a multitenant organization, after the owner of the multitenant organization has added your tenant to the multitenant organization as pending.

Before a tenant added to a multitenant organization can participate in the multitenant organization, the administrator of the joining tenant must submit a join request.

To allow for asynchronous processing, you must wait up to 2 hours before joining a multitenant organization is completed.

This API is available in the following national cloud deployments.

Global service US Government L4 US Government L5 (DOD) China operated by 21Vianet

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 permissions Higher privileged permissions
Delegated (work or school account) MultiTenantOrganization.ReadWrite.All Not available.
Delegated (personal Microsoft account) Not supported. Not supported.
Application MultiTenantOrganization.ReadWrite.All Not available.

The signed-in user must also be assigned at least the Security Administrator directory role.

HTTP request

PATCH /tenantRelationships/multiTenantOrganization/joinRequest

Request headers

Name Description
Authorization Bearer {token}. Required.
Content-Type application/json. Required.

Request body

In the request body, supply only the values for properties that should be updated. Existing properties that aren't included in the request body maintains their previous values or be recalculated based on changes to other property values.

The following table specifies the properties that can be updated.

Property Type Description
addedByTenantId String Tenant ID of the Microsoft Entra tenant that added the current tenant to the multitenant organization. To reset a failed join request, set addedByTenantId to 00000000-0000-0000-0000-000000000000. Required.

Response

If successful, this method returns a 204 No Content response code.

A join request might be unsuccessful. The following are some scenarios:

  • The joining tenant has not been added to the multitenant organization by its owner.
  • The owner or joiner tenant exceeds the maximum number of internal users per tenant.
  • The multitenant organization would exceed the maximum number of tenants.
  • The joining tenant is already part of a different multitenant organization.

Examples

Example 1: Join a multitenant organization

The following example shows a request by the current tenant to join a multitenant organization. It can take a few minutes for the join to complete. If the join succeeds, the state of the tenant is changed to active.

Request

PATCH https://graph.microsoft.com/v1.0/tenantRelationships/multiTenantOrganization/joinRequest
Content-Type: application/json

{
    "addedByTenantId": "1fd6544e-e994-4de2-9f1b-787b51c7d325"
}

Response

HTTP/1.1 204 No Content

Example 2: Reset a failed join request

The following example shows a request by the current tenant to reset a failed join request. To reset a failed join request, set addedByTenantId to 00000000-0000-0000-0000-000000000000.

Request

PATCH https://graph.microsoft.com/v1.0/tenantRelationships/multiTenantOrganization/joinRequest
Content-Type: application/json

{
    "addedByTenantId": "00000000-0000-0000-0000-000000000000"
}

Response

HTTP/1.1 204 No Content