Switch from Azure to Okta

[Mary Wilson]

Hi All,

I know the switch from Azure to Okta should be trivial, but my organization is pretty risk adverse, so would prefer to test out the Okta configuration in an environment that will not affect our production cloud users.  We're wondering if we can spin up a dev instance of Atlassian Access and configure with Okta to test that config as to not affect our prod Atlassian Cloud users.

Or, does someone have a better method of testing the configuration, or suggestions on how to migrate from Azure to Okta with the least impact to our users.

THANKS!

[Ed Letifov _TechTime - New Zealand_ · Accepted solution]

Atlassian Access identifies that a user needs to be send to IdP based on their email domain. There can be only one instance of Atlassian Access "managing" users from a particular domain. As such you can't have a TEST instance for your PROD domain.

If you are able to test with another domain – you can simply create a TEST organisation in your PROD instance Access, verify that other domain there, and configure SAML integration with OKTA.

So if a user uses an email from your PROD domain they will be sent to Azure AD. If they use the test one – to OKTA.

Obviously you can also create a completely independent TEST instance of Atlassian Access for this TEST organisation...

[Mary Wilson]

exactly what i needed to know.  thanks Ed!