nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Any best practice pointers on updating user logins due to domain change?

Andy Gladstone

Good day fellow Confluence Cloud Admins!

My company recently underwent a rebrand and as a result our users now all have new email addresses. Since the rebrand, many users that formerly signed in to our Atlassian Cloud instance with usernameolddomain.com have been trying to log in with usernamenewdomain.com. This has caused a lot of pain for users and admins.

Is there a best practice anyone can share around how we can update all user logins to the new usernamenewdomain.com email addresses?

Caveats/Details:

We are on Cloud Premium.
After the rebrand we did install Entra to be able to manage accounts, so that is currently in play in our environment.
We have Guard Premium installed.

Looking forward to your guidance and assistance!

Comments

Bhaskar_omxpep

@Andy Gladstone

indeed changing domains is a very painful task. I am currently working on the same scenario. below is the approach which i have taken and was able to successfully complete is for one of my client as part of Cloud Migration.

Post Migration of all the Data along with Users with Old domain

DNS Verify both the domains (old & new) in source instance.
DNS verify New domain in Target System
In Source system used manual Claim and in Target Automatic Claim
Configured Entra SSO in Target instance
Written a python Script to change email address of all the managed accounts using User management API
Executed the script with Org Admin API key in Source Instance

This will change the Email address with new domain and flow into Target Instance.

Finally enabled Auto Provisioning of users in target system.

Note: this requires some downtime of the system. If users keep using old email to login to target instance post script execution then the accounts will switch back to old domain. that's why we need downtime.

Hope this helps you

Andy Gladstone

@Bhaskar this is a bit of overkill based on my use case, which is just getting all users in a current system to update their domains. But the principal is the same, and the suggestion of using the User Management API to run a script is a good one.

I've accepted your answer.

Thank you!

Juan Pablo Gorgati

Hi @Andy Gladstone , I have a client who is in a similar situation to yours (I think so): they are changing the domain of their email addresses, staying on the same instance (there's no migration), but the new domain will be managed from a new Azure AD. Could you summarize the steps that worked for you, if your situation was similar? I'm a bit confused by @Bhaskar's answer, which also implies a migration.