Fix OneDrive Folder Showing Old Organization Name After Rename
Question details
The local Windows sync folder for OneDrive continues to display the old organization name even after the name was successfully updated in the Microsoft 365 admin center.
- Product
- OneDrive and SharePoint
- Device & OS
- Windows
- Scenario
- An administrator changed the organization name in Microsoft 365, and users expect their local Windows File Explorer sync folders to reflect this new name automatically.
- Observed behavior
- The local synced folder name remains stuck on the old organization name. Troubleshooting steps like unlinking accounts, clearing cache, editing Windows credentials, and even testing on a brand new computer failed to update the folder name.
Verify with your Microsoft 365 administrator that the organization name change was successfully saved in the admin center, and ensure all your local files are fully synced to the cloud before making any account changes.
Allow Propagation Time and Reconnect to a New Path
Organization name changes require time to propagate across Microsoft's servers. Waiting a few days and then reconnecting your account to a fresh local path is the most effective way to force the update.
Changes made in the Microsoft 365 admin center are not instantaneous. The old organization name often remains cached locally and on the server side for several days.
It is crucial that you do not manually rename the local folder in File Explorer while synchronization is active, as this will cause syncing errors and file conflicts.
Click the OneDrive cloud icon in your Windows taskbar, click the gear icon (Help & Settings), select 'Settings', navigate to the 'Account' tab, and click 'Unlink this PC'.
Leave the account disconnected for several days to allow the organization name change to fully propagate across Microsoft's backend systems.
Sign back into the OneDrive sync client. When prompted to choose a folder location, select a slightly different local path to force Windows to create a fresh directory with the updated organization name.
Open a Microsoft 365 Service Request
If the folder name still has not updated after waiting several days and reconnecting, the issue must be escalated to Microsoft support for backend resolution.
Switch to WPS Office for a Seamless, Hassle-Free Cloud Experience
If you are tired of complex Microsoft 365 sync delays and administrator-level troubleshooting, consider switching to WPS Office. It provides a lightweight, free alternative with reliable built-in cloud storage that seamlessly handles file synchronization without complicated backend propagation issues.
- 1. Download the Application: Visit the official WPS website and download the free WPS Office suite for your Windows PC.
- 2. Sign In to WPS Cloud: Launch the application and create a free account to instantly activate your dedicated cloud storage.
- 3. Save and Sync: Save your documents directly to WPS Cloud to enjoy automatic, hassle-free synchronization without worrying about complex tenant settings.

Frequently Asked Questions
How long does it take for a Microsoft 365 organization name change to update locally?
It typically takes several days for an organization name change to propagate fully across all Microsoft 365 servers and reflect in the local OneDrive or SharePoint sync clients.
Can I manually rename the OneDrive folder in Windows File Explorer?
No, you should never manually rename the synced folder while the OneDrive client is actively running. Doing so can break the sync connection, cause data conflicts, and lead to missing files.
Why does reconnecting my account immediately not fix the folder name?
If you reconnect your account immediately after the administrator changes the organization name, the old name is likely still cached on Microsoft's backend servers. You must wait for the propagation period to finish before re-establishing the connection.
Will clearing the OneDrive cache resolve organization name sync issues?
Generally, no. Clearing the local cache, resetting the OneDrive app, or even using a new computer will not fix the issue if the new name has not finished propagating through Microsoft's servers.




