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!


Migrate Server to Cloud, add Atlassian Access, change from local AD to Azure-AD, what is the preferr


Hi community,

in the next months, I plan to migrate our server-based instances of Jira, Bitbucket, Confluence to the Atlassian Cloud. I read already the one ore the other document, but I have a bit specific use-case, I like to share, hoping someone did that already earlier.
It is related to the User and Group Management.

Today (Atlassian Server):
We use an on-premisis Windows Active Directory (LDAPauth - read only, local groups) to perform the User Authentication. (Example of AD User is:   fmueller)

Future (Atlassian Cloud):
We like to make use of the Azure-AD User Authentication (SSO), which we already have in place for other applications. Azure-AD and AD are not in sync. We like to get rid of the AD.
(Example of Azure-AD user is:

It's clear, that we need to get the Atlassian Access product for the cloud applications, and to make the connection between Microsoft Azure-AD and Atlassian Access, there are documents how to do that.

My question is about the best sequence in the migration process.
Shall we change our server product user directory configuration to Azure-AD based user ..., upfront to the content migration?

Looking forward for your feedback.




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events