Microsoft Entra ID
Provisioning

User Source Of Authority Configure

In brief

The article adds Microsoft Graph API and PowerShell examples for transferring the source of authority (SOA) for organizational contacts synchronized from AD DS, including permissions, verification, and sovereign-cloud guidance.

What Entra admins need to know

Administrators can follow the documented commands and required `Contacts-OnPremisesSyncBehavior.ReadWrite.All` permission to manage contact SOA.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Configure Contact SOA

You're can also able to transfer the SOA of organizational contacts synchronized from AD DS to Microsoft Entra ID. These are directory objects accessed through /contacts, not personal contacts in a user's Outlook mailbox.

Use Graph Explorer or Microsoft Graph PowerShell to read and update contact SOA. Microsoft Graph Explorer isn't supported in this article. Contacts are itemsAzure China. For PowerShell, use the contact cmdlets in Outlook where you can organizethe Microsoft.Graph.Identity.DirectoryManagement module and save information aboutconnect with -Environment China. For other sovereign clouds, use -Environment USGov or -Environment USGovDoD as appropriate. See Microsoft Graph PowerShell cloud authentication.

Use Microsoft Graph API

Replace {ID} with the people and organizations you communicate with.object ID of your synchronized organizational contact. The following HTTP examples are of how you would transferuse the global cloud endpoint. For another cloud, use its Microsoft Graph endpoint.

  1. Read the existing SOA of contacts.state. Before transfer, isCloudManaged is false:

    To confirm the contact SOA is cloud managed, you run the following API call:

    GET https://graph.microsoft.com/v1.0/contacts/{ID}/onPremisesSyncBehavior?$select=isCloudManaged
    

    To update the cloud-managed contact, you can make the following API call:

       PATCH https://graph.microsoft.com/v1.0/contacts/{ID}/
          {
            "DisplayName": "Contact Name Updated"
          }
    

    Related content

    • How to audit and monitor User Source of Authority (SOA) in Microsoft Entra ID
      GET https://graph.microsoft.com/v1.0/contacts/{ID}/onPremisesSyncBehavior?$select=isCloudManaged
      
    • Transfer contact SOA to the cloud by setting isCloudManaged to true:

      PATCH https://graph.microsoft.com/v1.0/contacts/{ID}/onPremisesSyncBehavior
      Content-Type: application/json
      
      {
          "isCloudManaged": true
      }
      
    • Repeat the GET request to verify that isCloudManaged is true.

Use Microsoft Graph PowerShell

The following example reads, transfers, and verifies contact SOA in Azure China. Replace <tenant-id> and <contact-object-id> with your tenant and organizational contact IDs. For the global cloud, omit -Environment China.

Import-Module Microsoft.Graph.Identity.DirectoryManagement

Connect-MgGraph -TenantId "<tenant-id>" -Environment China -Scopes "Contacts-OnPremisesSyncBehavior.ReadWrite.All"

$contactId = "<contact-object-id>"
Get-MgContactOnPremiseSyncBehavior -OrgContactId $contactId -Property "isCloudManaged"

Update-MgContactOnPremiseSyncBehavior -OrgContactId $contactId -BodyParameter @{ isCloudManaged = $true }

Get-MgContactOnPremiseSyncBehavior -OrgContactId $contactId -Property "isCloudManaged"

Verify that the final result shows IsCloudManaged as True. See the contact cmdlet references in Related content.

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…