PabelM.40600 (Customer) asked a question.
My current Okta tenant has a lot of "Skeleton's in the closet" for configs, app settings, rules, AD delegation, groups, mfa setup, etc. I am curious if anyone in the community has experience with the following scenario:
Instances:
Okta-instance1: CompanyABC.okta.com
Okta-instance2: CompanyABC2.okta.com
Current State:
80+ apps
450 users
Goal:
-Setup Okta-instance2 with the proper config, not ad delegated, Okta verify instead of other MFA, etc.
-Invite users one a time (we don't like big bang here).
-Pick a cutover weekend and move all apps over.
-Have Okta support delete okta-instance-1 and change the name to okta-instance-2.
Issues:
-I would still need to big bang all 80+ apps that we currently have in Okta-instance1.
-Not sure if the Sign-On URL's/Metadata URL's change again after going from Okta-instance2 to Okta-instance1.
Is there anything else I need to consider here?
Anyone have luck in a similar endeavor?
I'm curious if the "lemon is worth the squeeze".
Hi @PabelM.40600 (Customer) , Thank you for reaching out to the Okta Community!
Renaming the Okta org would imply reconfiguring all apps, so depending on your use case, requirements and resources, like you said it might not be "worth the squeeze".
Check the following doc for other implications around org renaming:
https://support.okta.com/help/s/article/Renaming-Your-Okta-Subdomain
User migration might be manageable with an Org2Org implementation as it supports Provisioning:
https://help.okta.com/en-us/Content/Topics/Provisioning/org2org/org2org-main.htm
We'll definitely leave this question open for Community members input as well, in case someone attempted somethings similar.
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Community members help others by clicking Like or Select as Best on responses. Try it today.