Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,971
Community Members
 
Community Events
176
Community Groups

User Provisioning with SCIM on existing SAML account/users

I am considering to use SCIM to provision users  from our Azure Active Directory. 

But what happens with the existing users? We have set up SAML SSO already and lots of users are already created.

What happens if SCIM is set up and  user@corporate.com is added to a azuread group and is set for provisioning to Atlassian, but user@corporate.com already exists in Atlassian as a managed account? 

1 answer

1 vote

Hi Martin,

You should not have any problems with the scenario you have described. Please see the following section from the Atlassian Access user provisioning documentation

 

If your Atlassian organization already has existing users:

  • And the identity provider has a user with the same email address as a user in your organization, we'll create a link between both user accounts. Going forward, you can only make changes to the user's account from your identity provider.
  • And the identity provider doesn't have a user with the same email address as a user in your organzation, the user's access remains the same and you can still manage that user from your Atlassian organization.

 

Thanks,

Narmada Jayasankar

Lead Product Manager

Atlassian Access

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events