Fix a OneDrive URL Showing an Old Name and Returning a 404 Error
Question details
The OneDrive link on Office.com points to a URL containing a former user name, resulting in a 404 error after a user's surname was changed.

- Product
- Microsoft 365 OneDrive
- Device & OS
- not provided
- Scenario
- Accessing OneDrive from the Office.com portal after an account's surname has been updated by administration.
- Observed behavior
- The root OneDrive URL fails to synchronize with the new name. Clicking the link returns a 404 error, and removing old email aliases does not resolve the issue. Manually typing the new name into the URL works temporarily.
Ensure you have global administrator privileges in the Microsoft 365 tenant, as resolving this backend synchronization issue requires opening an official support ticket.
Contact Microsoft Support via the Microsoft 365 Admin Center
This is a tenant-level SharePoint Online and OneDrive synchronization issue that requires Microsoft's backend engineering team to repair the URL manually.
Standard administrator actions, such as removing old email aliases or updating user profiles, typically cannot force the OneDrive personal site URL to update after a name change.
A global administrator must submit a formal service request so that the Microsoft team can force a site rename or correct the synchronization mismatch in the tenant.
Log in to Office.com with your global administrator credentials, open the app launcher, and select the 'Admin' center icon.
On the left-hand navigation menu of the Admin center, click on 'Support' and then select 'Help & support'.
Type a brief description of the OneDrive URL 404 error resulting from a surname change. Follow the prompts to select 'Contact support' and submit a formal ticket for backend repair.

Contact Microsoft Support by Phone
Use this method if you are unable to access the Microsoft 365 Admin portal to open a web ticket but still have tenant administrator authority.
Manually Edit the URL (Temporary Workaround)
Use this method to urgently access files while waiting for Microsoft to resolve the permanent URL synchronization issue.
Switch to WPS Office for a Hassle-Free Experience
If complex backend sync issues like persistent 404 errors in Microsoft 365 disrupt your daily workflow, consider switching to WPS Office. As a free, lightweight, and highly compatible Office alternative, WPS Office allows you to manage documents seamlessly across local drives and third-party clouds without relying on rigid tenant administration structures.
- 1. Download WPS Office: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install and Launch: Run the installer to complete the setup, then open WPS Office to view its intuitive workspace.
- 3. Open Office Files Directly: Drag and drop your existing Microsoft Office files into the application to edit them effortlessly without format loss.

Frequently Asked Questions
Why does my OneDrive URL still show my old name after changing it?
In Microsoft 365, a user's personal OneDrive site URL is generated based on their initial username. When a surname or username changes, the SharePoint/OneDrive backend often fails to synchronize the new name automatically, resulting in the portal pointing to an outdated, non-existent URL.
Will removing my old email aliases fix the OneDrive 404 error?
No. Removing former email aliases from the Exchange admin center typically does not resolve this issue. The SharePoint and OneDrive URL structure is handled separately from email aliases, and fixing it requires a backend synchronization trigger from Microsoft.
How long does it take for Microsoft to fix the OneDrive URL synchronization issue?
Once a global administrator opens a ticket with Microsoft 365 support, it can take anywhere from a few hours to a couple of days for the backend engineering team to manually repair the tenant synchronization and restore access to the correct URL.
Can standard users fix the 404 error themselves?
No, standard users do not have the required administrative permissions to submit a backend repair ticket to Microsoft. Users experiencing this problem must document the error and contact their internal IT department for assistance.




