Our OneDrive sync folders on client PCs include the company's full legal name, which contributes to long-path problems. We'd like to shorten the company-name portion of the local OneDrive path. Older guidance suggested changing the organization name in the Microsoft 365 admin center, but that option no longer appears to be available and seems to have been replaced by a legal-entity-change request. Before starting that process, is it genuinely required, or is there a supported alternative for changing the OneDrive folder name?
3 Answers
There is a technically possible manual workaround, but it is risky and not ideal at scale. Close OneDrive, update the stored paths in the relevant local OneDrive settings folder, rename the synced folders, and then update the corresponding paths under the current user’s OneDrive account registry settings before restarting OneDrive. Every path has to match exactly, so test carefully and keep backups. For many users, a tenant-level rename or supported policy is safer, although users may still need to unlink and resync.
The company name may only account for a few characters, so you should also tackle deeply nested folders and overly long file names. SharePoint and OneDrive are particularly sensitive to deep structures; reorganizing content into separate document libraries can help. That said, unusually long legal names can make the path problem much worse, so addressing both issues is reasonable.
That makes sense. We’re planning to reduce the depth and shorten file names as well, but changing the company-name portion would be a useful second step.
A tenant rename is the cleaner long-term approach when the existing name contains special characters or is genuinely excessive. It can take up to a couple of weeks, and you may see a mixture of old and new names during the transition. Once completed, users may need to reconnect or resync OneDrive, but the result is more maintainable than manually changing every workstation.
There may also be a policy for assigning a custom OneDrive sync-folder name. It would be worth checking whether that policy is available in your current Microsoft 365 configuration before editing client files or the registry.