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.
Cheers,
Daniel
Just what we were looking for, thanks Daniel!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.