I just wanted to post the most recent update here:
To configure user provisioning for Active Directory or LDAP with your Atlassian organization, you’ll connect your on-premises Active Directory to a supported identity provider. This connection will sync your user’s account details between your identity provider and Atlassian products.
If you're already using Office 365, you should have already synced your users from Active Directory or LDAP to Azure AD. If your organization isn't using Azure AD or another cloud identity provider like Okta, Onelogin, or Idaptive (formerly Centrify), we recommend investigating these products to get the best support integrating identity management with SaaS applications like Atlassian products.
Identity provider setup instructions:
|AD FS||Configure SAML single sign-on with Active Directory Federation Services (AD FS)|
|Bitium||Configuring SAML for Atlassian Cloud|
|Idaptive (formerly Centrify)
|Okta||How to Configure SAML 2.0 for Atlassian Cloud|
You'll need to be logged in to OneLogin to see those pages.
Problem the overall JIRA Server to JIRA Cloud migration get even more expensive with additional new providers plus additional management costs of another service provider. The yearly license cost estimation for JIRA Cloud approx costs 3 times more hard to make a case for the c level.
Hello! We are developing new set of features for the Confluence Cloud Migration Assistant and Jira Cloud Migration Assistant and we’d like to invite our valued Atlassian Community members to help p...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events