Update crossTenantAccessPolicyConfigurationPartner

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.

Update the properties of a partner-specific configuration.

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) Policy.ReadWrite.CrossTenantAccess Not available.
Delegated (personal Microsoft account) Not supported. Not supported.
Application Policy.ReadWrite.CrossTenantAccess Not available.

Important

In delegated scenarios with work or school accounts where the signed-in user is acting on another user, they must be assigned a supported Microsoft Entra role or a custom role with a supported role permission. The following least privileged roles are supported for this operation.

  • Teams Administrator - excluding identity synchronization settings
  • Security Administrator

HTTP request

PATCH /policies/crossTenantAccessPolicy/partners/{id}

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 only the values for properties to update. Existing properties that aren't included in the request body maintain their previous values or are recalculated based on changes to other property values.

The following table specifies the properties that can be updated.

Property Type Description
automaticUserConsentSettings inboundOutboundPolicyConfiguration Determines the partner-specific configuration for automatic user consent settings.
b2bCollaborationInbound crossTenantAccessPolicyB2BSetting Defines your partner-specific configuration for users from other organizations accessing your resources via Microsoft Entra B2B collaboration.
b2bCollaborationOutbound crossTenantAccessPolicyB2BSetting Defines your partner-specific configuration for users in your organization going outbound to access resources in another organization via Microsoft Entra B2B collaboration.
b2bDirectConnectInbound crossTenantAccessPolicyB2BSetting Defines your partner-specific configuration for users from other organizations accessing your resources via Microsoft Entra B2B direct connect.
b2bDirectConnectOutbound crossTenantAccessPolicyB2BSetting Defines your partner-specific configuration for users in your organization going outbound to access resources in another organization via Microsoft Entra B2B direct connect.
inboundTrust crossTenantAccessPolicyInboundTrust Determines the partner-specific configuration for trusting other Conditional Access claims from external Microsoft Entra organizations.
tenantRestrictions crossTenantAccessPolicyTenantRestrictions Defines the default tenant restrictions configuration for users in your organization who access an external organization on your network or devices.

Response

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

Examples

Example 1: Configure inbound trust settings

The following example configures the partner-specific policy by setting the inbound trust settings to accept MFA, compliant, and Microsoft Entra hybrid joined devices from the partner tenant.

Request

The following example shows a request.

PATCH https://graph.microsoft.com/beta/policies/crossTenantAccessPolicy/partners/90e29127-71ad-49c7-9ce8-db3f41ea06f1
Content-Type: application/json

{
  "inboundTrust": {
    "isMfaAccepted": true,
    "isCompliantDeviceAccepted": true,
    "isHybridAzureADJoinedDeviceAccepted": true
  }
}

Response

The following example shows the response.

HTTP/1.1 204 No Content

Example 2: Configure automaticUserConsent settings

The following example configures the partner-specific policy by consenting for B2B collaboration on behalf of your users and accepting admin consent for the users of the partner.

Request

The following example shows a request.

PATCH https://graph.microsoft.com/beta/policies/crossTenantAccessPolicy/partners/90e29127-71ad-49c7-9ce8-db3f41ea06f1
Content-Type: application/json

{
  "automaticUserConsentSettings": {
    "inboundAllowed": true,
    "outboundAllowed": true
  }
}

Response

The following example shows the response.

HTTP/1.1 204 No Content

Example 3: Configure tenant restrictions settings

The following example shows how to configure tenant restrictions settings.

Request

The following example shows a request.

PATCH https://graph.microsoft.com/beta/policies/crossTenantAccessPolicy/partners/90e29127-71ad-49c7-9ce8-db3f41ea06f1
Content-Type: application/json

{
  "tenantRestrictions": {
    "usersAndGroups": {
      "accessType": "allowed",
      "targets": [
        {
          "target": "AllUsers",
          "targetType": "user"
        }
      ]
    },
    "applications": {
      "accessType": "allowed",
      "targets": [
        {
          "target": "Office365",
          "targetType": "application"
        }
      ]
    }
  }
}

Response

The following example shows the response.

HTTP/1.1 204 No Content