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
Jira Cloud using AD for logins
We need to change the AD username and email, but the existing account is linked to Jira and Confluence.
How can we do this without losing everything the user already has in Jira etc?
Hello @Wallet ,
If you want to change username and email for a managed user then you may want to use the User provisioning REST API. Specifically, depending on your needs, one of the below endpoint should fit your needs:
Updates a user's information in a directory by
userIdvia user attributes. User information is replaced attribute-by-attribute, with the exception of immutable and read-only attributes. Existing values of unspecified attributes are cleaned.
This operation updates a user's information in a directory by
PATCH. Refer to
GET /ServiceProviderConfigfor details on the supported operations.
For further details on this, and to know the other Cloud admin REST APIs, you may also want to review the below links:
I hope this helps.
I just want to confirm, this will allow us to change firstname.lastname@example.org to email@example.com without losing any of their existing data? Across all Atlassian products? Our cloud logins are managed via Microsoft AD, so we are hoping to make users firstname.lastname@example.org and have that change reflected to their Atlassian accounts.
You are very welcome @Wallet ,
Assuming that you use Atlassian Access in order integrate with Microsoft AD for Single Sign On then I can confirm that, as long as the the user identifier does not change, you can update all the other users details.
Also, the User provisioning REST APIs are actually to be used when your Identity provider is not supported, otherwise it would just be enough to update the data in your AD and they will be automatically updated among all the Atlassian Cloud applications you use.
From the Understand user provisioning documentation page:
User provisioning integrates an external user directory with your Atlassian organization. This integration allows you to automatically update the users and groups in your Atlassian organization when you make updates in your identity provider [...]
Supported identity providers
Your user provisioning setup depends on the identity provider you use. Supported identity providers include:
- Okta – Learn how to configure user provisioning with Okta.
- OneLogin – Learn how to configure user provisioning for OneLogin.
- Azure AD – Learn how to configure user provisioning for Azure AD.
- Google Cloud – Learn how to configure user provisioning for Google Cloud.
PingFederate – Learn how to configure user provisioning for PingFederate.
In the future, we may support more identity providers based on customer demand.
If you use another identity provider, you can use the user provisioning API to create your own integration that allows you to manage users and groups.
However, there are also chances that you have already connected your AD to a supported IDP (as described in Configure user provisioning for Active Directory or LDAP) and therefore there is no need to use the APIs:
Please review the below pages and let me know if you have further questions on this:
For further details you may also want to watch: https://www.youtube.com/watch?v=7EQhYz-vApw