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 are trying to connect our O365 Accounts with Atlassian Access so that we won't have to create all the accounts from scratch.
Now the question has arisen what will happen to the accounts that already exist.
Some of our project managers are already using some Atlassian products and we don't want to risk any loss or "overwriting" of existing accounts.
Does anyone have any knowledge or has had a similar case?
Do we have to link only the new Accounts needed and give the existing one an invite/ReadCreateWrite-access?
If users already have an Atlassian account with the same address as their Office 365 account, the accounts are "linked" automatically – we link existing accounts and only invite new users if an existing account isn't found for a given email address.
If you're setting up SAML SSO, you shouldn't expect any changes. When you enable SAML, the first time the user logs in, authentication will be delegated to and we will associate the Office 365 user with the existing Atlassian Account.
Our support for SCIM user provisioning allows you to sync user profile details from your identity provider to the existing Atlassian account, but this is only available for Azure AD, not ADFS.