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
Our identity provider is Azure AD and we are currently using "Continue with Microsoft" to login to our accounts. I believe this is an oAuth integration.
Would we see any benefit in using the more expensive SAML integration?
Ideally we are looking to lock down accounts to only use Azure AD for authentication to our tenant.
Hi Sean, welcome to the Community!
With the social login options (Continue with Microsoft), it's possible to reset the password on your local Atlassian account (at id.atlassian.com) and have an Atlassian-specific password. You're not locked in to always signing in with "Continue with Microsoft".
Using Atlassian Access and configuring it with SAML back to Azure AD ensures that accounts must sign in through Azure. If you want to enforce MFA or conditional access policies, this is the route to go.