• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 113 subscribers
  • Views 780 views
  • Users 0 members are here
Options
Related

Hard match of User OBjectGuid from on Prem to immutable ID in cloud

rubarman
8 months ago

Hi,

I have 2 AD domain which uses same M365 tenant. The source anchor is ObjectGuid.After I migrate User from Source to Target domain I cannot sync ObjectGuid to target account  as it is unique.So , I want to match the ObjectGuid from newly created target user to immutable id in cloud user object which was originally in place in cloud. Does quest take care of byte conversion while populating ObjectGUID in immutable id in cloud user object

Parents
  • 0 7 months ago

    You need to change the source anchor attribute to MsdsConsistancyGuid.  Microsoft changed the default source anchor a long time ago. I want to say march 2018. The logic MS implemented was If the MsdsConsistancyGuid is blank the the objectguid value is coped to the MsdsConsistancyGuid. So the change is uneventful. The value come in if you have to migrate and maintain connection to the replicated object in Azure, now Entra ID. 

Reply
  • 0 7 months ago

    You need to change the source anchor attribute to MsdsConsistancyGuid.  Microsoft changed the default source anchor a long time ago. I want to say march 2018. The logic MS implemented was If the MsdsConsistancyGuid is blank the the objectguid value is coped to the MsdsConsistancyGuid. So the change is uneventful. The value come in if you have to migrate and maintain connection to the replicated object in Azure, now Entra ID. 

Children