Fix Microsoft 365 SharePoint Sign-In Issues After Domain Change
Question details
Users or administrators cannot access SharePoint or the SharePoint admin center after their Microsoft 365 tenant domain or default user address has been changed.
- Product
- Microsoft 365 / SharePoint
- Device & OS
- not provided
- Scenario
- An administrator recently updated the default domain for a user account within the Microsoft 365 tenant, and the user is attempting to access SharePoint sites or the admin portal.
- Observed behavior
- The system prompts the user to sign in with their old domain address and blocks access to SharePoint sites or the admin portal when using the new domain credentials.
Verify whether the sign-in issue affects a single user or multiple users, and confirm if the affected accounts can successfully access other Microsoft 365 services like Outlook or OneDrive.
Delete and Recreate the Affected User Account
When a domain change causes persistent syncing or sign-in errors for a specific account, recreating the user profile is the most reliable way to restore SharePoint access.
Changing a user's domain should normally not break SharePoint access. However, if backend synchronization issues permanently tie the account's permissions to the old domain, clearing the account and establishing a fresh identity in the tenant resolves the conflict.
Access the Microsoft 365 Admin Center using your global administrator credentials.
Navigate to 'Users' > 'Active users' on the left sidebar and find the user account experiencing SharePoint sign-in issues.
Manually back up any necessary data associated with the account, such as OneDrive files or Exchange mailbox contents, before proceeding.
Select the user and choose the option to delete the account from the tenant, ensuring you remove the associated licenses.
Create a new user account directly with the new domain address, reassign their Microsoft 365 licenses, and migrate the backed-up data to restore full access.
Verify Tenant Sync and Site Access Scope
Determine if the issue is a global tenant configuration problem or an isolated site permission error caused by the domain update.
Boost Your Productivity with WPS Office
While Microsoft 365 tenant issues can cause unexpected downtime, you can keep your local workflow running smoothly. WPS Office is a lightweight, comprehensive office suite that offers an excellent free alternative to Microsoft Office, ensuring your documents, spreadsheets, and presentations are always accessible.
Frequently Asked Questions
Why does SharePoint still ask for my old domain email after a change?
This typically happens due to cached credentials in your browser or a delay in the Microsoft 365 backend syncing the User Principal Name (UPN) change across all active services.
Does changing the SharePoint tenant domain name fix user sign-in errors?
No, changing the overarching SharePoint tenant domain configuration is unlikely to fix an issue that only affects specific user accounts. It is much more effective to troubleshoot the individual user's profile.
How long does a domain change take to sync in Microsoft 365?
While basic sign-in for email might work immediately, it can take up to 24 hours for a domain change to fully propagate and sync permissions across all Microsoft 365 apps, including SharePoint and Teams.
Can I fix this without deleting the user account?
If waiting 24 hours does not resolve the synchronization issue, deleting and recreating the account is often the most reliable official workaround to clear the backend conflict.
