<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
0D54z00008dkGl0CAEOkta Classic EngineSingle Sign-OnAnswered2023-01-11T20:14:39.000Z2023-01-10T10:19:35.000Z2023-01-11T20:14:39.000Z
Company re-brand advice for changing Okta usernames and M365

Good Morning, 

 

I'm hoping someone will be able to help advise me on how best to change Okta usernames and M365 in the next few weeks in line with a company re-brand. 

 

The company is re-branding and would like all systems to be changed so they are using the new domain for consistency with the new brand. 

 

They use M365 and Okta does all the wonderful work to provision users and authenticates users. They'd like everyone's Okta usernames to be changed to the new domain (this is currently set up in 365 as a subdomain) and everyone to be using the new domain as a primary email address in M365. The current domain being used will then become an alias for everyone in 365. After the change, the new domain will be used to create all new future users.

 

I know we've got a bit of manual work ahead of us for a lot of the SaaS apps but the changes I'm most nervous about are changing Okta and M365. I've looked at the multiple federations for the M365 guide but I'll be honest, I'm a bit confused and not sure if that's what we want. We just want to swap things over completely but without any data loss risk and ensure minimal downtime. 

 

Is anyone able to offer some advice on this? 


This question is closed.
Loading
Company re-brand advice for changing Okta usernames and M365