Updated April 3, 2025:October 31, 2024: We have updated the rollout timeline below. We are now one month away from this change taking effect.content. Thank you for your patience.
We're removing the EnableAllOcsiClients OneDrive group policy in the Microsoft 365 admin center. OCSI is the coordination between office and OneDrive for syncing office documents to the cloud.
This message is associated with Microsoft 365 Roadmap ID 429874.
How this will affect your organization:
After this rollout, the EnableAllOcsiClients group policy will be removed, and Microsoft Office and Microsoft OneDrive will be able to communicate smoothly to ensure existing Office features like autosave, version history, real time user collaboration, and merging in the case of conflicts can work properly for end users.
Before this rollout, tenants had the option to disable this feature with a GPO, and when they disable the GPO, existing Office features like autosave, version history, real time user collaboration, and merging in the case of conflicts cannot work properly.
When this will happen:
General Availability (Worldwide, GCC, GCC High, DoD): We will be rolling out in early May 2025 (previously April).April 2025.
How this will affect your organization:
With OCSI enabled for all tenants, end users will be able to take advantage of features such as autosave, real time user collab, and merging in the case of conflicts of Office files. Autosave is a feature that end users will see in Word, Excel, and PowerPoint files; it is a toggle at the top left of the file header that will ensure that even if the user does not manually save a file, the file will be saved automatically to OneDrive and SharePoint. With real time user collaboration, different users can collaborate on the same file at the same time. Version history allows users to see when and who made changes to a file and provides the ability to restore to a previous version of the file within the Office app. If there are conflicts within a file that does not require user input, Office will merge the conflicts and ensure that the Office file is up to date with the latest changes. If user input is required to merge conflicts, Office will show the merge conflicts and prompt the user to choose which edits to prioritize.
What you need to do to prepare:
This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change, especially if the policy is disabled, educate them about autosave, real time user collab, and merging in the case of M365 application conflicts, and update any relevant documentation.
For more information, see Allow users to choose how to handle Office file sync conflicts.