Relation between ObjectGUID, SourceAnchor & ImmutableID in Office 365 Hybrid Environment

Hello,

I have provided you  with a script how to convert the ObjectGUID of AD User to ImmutableID, but I have forgot to explain you the relation between them.

In Hybrid environment with  AD Connect using to sync On-Premise user to Azure AD, with AD Connect set with the default setting:

ad-connect-select-uniquely-identifying-your-users

  1. AD Connect will calculate the source Anchor based on ObjectGUID
  2. AD Connect will also sync the User principal Name using the UserPrincipalName Attribute of the user

Please find the step AD Connect will use to Convert ObjectGUID to ImmutableID:

  1. AD Connect will retreive the User ObjectGUID Attribute through AD Connector
  2. AD Connect will then convert the ObjectGUID to CloudSourceAnchor(in the Metaverse)
  3. AD Connect will then export CloudSourceAnchor(Metaverse) to SourceAnchor(AAD Connector)
  4. The AAD Connector will export SourceAnchor to Azure AD
  5. The SourceAnchor will be saved as ImmutableID Attribute of Azure AD Object.

relation-between-objectguid-sourceanchor-immutableid

I hope this information will help to better understand how your AD Connect is working.

 

Author: John

I m a consultant who love Microsoft Exchange and try to learn as much as possible. so if you have any question related to Exchange please do not hesitate to ask. if I don't know I will know.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s