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

[Dirk Hainbach]

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: fritz.mueller@domain.com)

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.

Martin

[Shawn Doyle - ReleaseTEAM]

This article, while a little dated, should have the details you need

https://community.atlassian.com/t5/Jira-questions/JIRA-Confluence-Server-to-Cloud-Migration-Changing-User/qaq-p/609755

If possible, one of the better approaches would be to sync your on-prem AD to Azure AD and then connect Azure to your Atlassian org via Access.