<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
0D54z000082hvH3CAIOkta Classic EngineDirectoriesAnswered2022-09-01T16:40:39.000Z2022-08-31T11:38:04.000Z2022-09-01T16:40:39.000Z
  • flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)

    Hi @AndyT.08763 (ManyPets)​,

     

    Thank you for posting on the Okta community page!

     

    My recommendation for your inquiry would be to re-visit the Okta configuration and check where the Office 365 domain name was required in the setup because it will have to be changed with the new one in order to maintain the SSO sync between the apps. Also, I would also re-test the API credentials to make sure that provisioning will still be synched properly as per your organisation needs.

     

    Additionally, if possible, my advise would be to test this on a Okta preview environment by using a test office domain where you create the exact setup that you have in production to test the change of Office 365 tenant name and see if you are encountering any issues.

     

    I hope the above information is useful!

    Expand Post
This question is closed.
Loading
Changing a Microsoft 365 Tenant name