<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00006dk4gnSAAOkta Classic EngineUniversal DirectoryAnswered2025-03-31T09:00:15.000Z2019-09-12T14:58:13.000Z2019-10-11T21:31:55.000Z

poj84 (poj84) asked a question.

Active Directory Forest Migrations

Active Directory's ObjectGuid is hard matched to Okta's ExternalID. When a user is moved to a new forest they receive a new ObjectGuid and those 2 attributes no longer match. Both are immutable. How can that match be established again in large enterprise environments where uptime is crucial?


  • 8n9yw (8n9yw)

    so support had no answer for me last week(case still open)

     I found this https://support.okta.com/help/s/article/After-adding-a-second-AD-instance-provisioning-issues-for-Office-365-are-encountered

    was ok answer but with the info made a better answer

    what I did was created Okta attributes for both domain

    Domain-a-immutableID

    domain-b-immutableid

    then wrote expression that is legacy ID exist use it if not use new domain.

    user.domain-a-immutableID != null ? domain-a-immutableID : user.domain-b-imutableid

    (this field is at create only)

    so now user get legacy domain unless it does not exist then they get new domain.

    there is also a powershell to update users Immutable id in O365 so I will get to a migration point where most are in new domain... I will export ID from Okta and run a script to mass update O365 to new domain ID then remove the legacy domain mapping.

    Expand Post
    Selected as Best
  • poj84 (poj84)

    Molly,

    Thank you, however I have an active ticket and we are making progress but I did want to ask if others had the same issue for which they needed a solution. Perhaps more than one way to do things...sort of thing. 🙂

  • flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)

    Thank you for posting on our Community page.

     

    Firstly, you can still match the users even though they don't have the same attribute ( AD-ObjectGuid and Okta's ExternalID ). The users can be matched with a rule that appears under AD settings, at the Match Settings section. The accounts can be matched by email, username or any attribute that is exactly the same on both of the accounts (Okta and AD).

     

    Furthermore, if this is not working, you could open a new case that will be assigned to an engineer for further troubleshooting.

     

    Thank you,

    Flaviu Vrinceanu

    Technical Support Engineer | Okta

    Expand Post
  • poj84 (poj84)

    Flaviu,

     

    Thank you for your reply.

     

    As I mentioned, I do have an open case. I am looking to share my experience for others and gather other ideas.

     

    The matching *is* in fact done by email.

     

    However, when the ObjectGuid of the user changes everything works fine until you change any attribute on the AD side. For example, if I change a user's description, this triggers an "exact match" issue. Of course, Okta refuses to import the change.

     

    Thank you,

     

    Kevin

    Expand Post
  • 8n9yw (8n9yw)

    so support had no answer for me last week(case still open)

     I found this https://support.okta.com/help/s/article/After-adding-a-second-AD-instance-provisioning-issues-for-Office-365-are-encountered

    was ok answer but with the info made a better answer

    what I did was created Okta attributes for both domain

    Domain-a-immutableID

    domain-b-immutableid

    then wrote expression that is legacy ID exist use it if not use new domain.

    user.domain-a-immutableID != null ? domain-a-immutableID : user.domain-b-imutableid

    (this field is at create only)

    so now user get legacy domain unless it does not exist then they get new domain.

    there is also a powershell to update users Immutable id in O365 so I will get to a migration point where most are in new domain... I will export ID from Okta and run a script to mass update O365 to new domain ID then remove the legacy domain mapping.

    Expand Post
    Selected as Best
  • poj84 (poj84)

    In order to change the ImmutableID the domain cannot be federated.

This question is closed.
Loading
Active Directory Forest Migrations