Configuring SSO using Microsoft Entra ID

[King]

I have a question regarding configuring SSO using Microsoft Entra ID. 

Thanks to the Atlassian comprehensive document, I can do it without a problem. However, we want to confirm a few things before implementing it. 

We have been using Atlassian for years and want to use SSO using Azure AD. We want to minimise the disruption as much as possible. 

The questions are: 

1. Will it affect the existing users? How can we map users after provisioning it in Entra ID?
2. Can we do it in stages? i.e. Test it on a group of users before deploying it to everyone in the organisation. 

Any advice is much appreciated. 

[Alexis Robert · Accepted solution]

Hi @King , 

happy to answer your questions here. 

1. The mapping between existing users and users coming from Azure AD is done automatically by Atlassian Access, using the email address as a unique key. So, if your users have the same email in Azure AD and their Atlassian account (that should be the case) then it's completely transparent to them
2. Yes you can. You should be able to assign only a few users to the Atlassian Cloud app in Azure AD if you want to do some testing first. This is explained in the Microsoft documentation, in section "Assign the Microsoft Entra test user".

Let me know if this helps, 

--Alexis

[King]

Hi @Alexis Robert 

Thank you for your response. 

If you don't mind, I'll ask another question. Is there a risk of disruption for the current user? 

I went through the documentation, and it's a straightforward process. However, this is my first time implementing this, so I want to minimise the disruption as much as possible. 

Is there anything I should keep in mind when I start doing this?

Any advice will be much appreciated. 

[Alexis Robert]

Hi @King , 

this is completely transparent for the users, as nothing changes for them until you add them to a policy that forces SSO. 

It's all done on the backend as Access will link users coming from Entra to the local directory.

--Alexis