I'm trying to migrate all the users from one verified domain inside of Atlassian to another verified domain. Both domain are completely different in name. So users now have the old domain in their emails and I want to move them to the new domain.
Do you know what steps to follow to move users from one domain to another without losing their records of tickets and everything and without creating second accounts with the new domain?
In the middle of all this, the log-in for users is through SSO through Azure AD from Microsoft. And I tested one account inside of Microsoft, switching their email domain to the new email domain inside of Microsoft Admin Center and then that user tried to use the Atlassian SSO and this is what it showed:
"Sorry, we detected an email change that is not supported by your organization's authentication policy. Please log in with a email address that matches your account."
What do I have to do to auto sync the account for Atlassian SSO? Should I switch the email domain for users accounts in M365 and re add the SSO? But then this error will show up as their email would be different to their accounts in Atlassian.
Any ideas how would this work without creating new accounts in Atlassian for each users with the new domain?
(old question, but in case someone lands here)
The other answer completely misunderstands the question.
The issue is about users changing their email domain, not about moving the jira product account to a new domain or organization.
According to
To change the email addresses, the new domain needs to be verified.
Then, you need to _manually_ update the user's email address.. for each user... (seriously??)
I guess that once the email address has been updated under Managed accounts, it will then match with the address provided by AzureAD / EntraID and users will be able to login normally
On this other answer from 2019,
they say not to edit the email addresses under Managed Accounts. SSO should update the user email addresses automatically on the next login, as long as :
> check the attribute mapping for the SAML-SSO setup. The Azure attribute (UPN or mail) that is mapped to the "Unique User Identifier (Name ID)" will be the value that will trigger the change into Atlassian
Hi @Flavia Maroney,
Welcome to Atlassian community :)
Regarding to moving to another company domain, you can try:
Regarding to SSO problem, you can try contact Atlassian support - https://support.atlassian.com/ for more help.
Pavel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.