You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We use Microsoft Azure to provide authentication to many of our SaaS products in the cloud. Ideally this would be the way we have our staff authenticate to our cloud-based Jira apps like Jira, Jira Service Desk, and Confluence.
It appears that Atlassian Access is the recommended tool for doing this, but is it required? It does more than we need, so I'm guessing our CIO would rather not pay for an add-on unless it's really required.
Our goal is to provide simple SSO to Atlassian cloud apps. We will have close to 100 licensed users, and around 15,000 employees who will be Service Desk customers. Is it possible for us to just use LDAP or do we actually need to go with Atlassian Access?
For our Cloud product, Atlassian Access is indeed required to use SAML for integrations with Identity Providers (ie: Microsoft Azure), more details can be found here:
For Service Desk customers (portal-only users), there is no SAML feature available at this time, we have a feature request open to cover the specific needs (Like not being able to verify the domain of customers):
*Still* there is a workaround to use the same SAML integration from your internal users to portal-only users, by migrating them to Atlassian account, before that, you would need to change your default application access so these users don't consume a default license, they won't have product licenses, so will not count towards the billing for Atlassian Access, more details on how to migrate users can be seen here:
I hope the information below helps you!
Thank you & kind regards,
Atlassian Cloud Support