Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Switch from Azure to Okta

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.


1 answer

1 accepted

2 votes
Answer accepted
Ed Letifov _TechTime - New Zealand_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 26, 2020

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...

exactly what i needed to know.  thanks Ed!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events