Microsoft Entra ID
General

User Source Of Authority Configure

In brief

The article now describes contacts as Outlook items, retains the required Contacts-OnPremisesSyncBehavior.ReadWrite.All permission, and uses a generic contact PATCH example. Detailed SOA read, transfer, verification, PowerShell, sovereign-cloud, and contact cmdlet guidance was removed.

What Entra admins need to know

Administrators managing contact SOA should follow the revised example and permission guidance when using the article.

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.

  1. Verify that the user appears in the Microsoft Entra admin center as a synced user.

  2. Use Microsoft Graph API to transfer the SOA of the user object (isCloudManaged=true). Open Microsoft Graph Explorer and sign in as a Hybrid Administrator. Alternatively, use Microsoft Graph PowerShell to perform the following operations with the cmdlets linked in Related content.

  1. Let's check the existing SOA status. We didn’t update the SOA yet, so the isCloudManaged attribute value should be false. Replace the {ID} in the following examples with the object ID of your user. For more information about this API, see Get onPremisesSyncBehavior. /graph/api/onpremisessyncbehavior-update

Configure Contact SOA

You can're also able to transfer the SOA of organizational contacts synchronized from AD DS to Microsoft Entra ID. Theseof users using the examples provided in this article. Contacts are directory objects accessed through /contacts, not personal contactsitems in a user's Outlook mailbox.

Use Graph Explorer or Microsoft Graph PowerShell to readpeople and update contact SOA. Microsoft Graph Explorer isn't supported in Azure China. For PowerShell, use the contact cmdlets in the Microsoft.Graph.Identity.DirectoryManagement module and connect 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 object ID of your synchronized organizational contact.organizations you communicate with. The following HTTP examples useare of how you would transfer the global cloud endpoint. For another cloud, use its Microsoft Graph endpoint.SOA of contacts.

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

    GET https://graph.microsoft.com/v1.0/contacts/{ID}/onPremisesSyncBehavior?$select=isCloudManaged
    
  2. 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
    }
    
  3. 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…