Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
429874

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions we saw
  • Seen 3 Apr 2025 April 2025 → early May 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated April 3, 2025: We have updated the rollout timeline below. We are now one month away from this change taking effect.

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).

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.

What changed

Between archive captures, newest first
    • Services Microsoft OneDrive → OneDrive for Business
    • Services OneDrive for Business → Microsoft OneDrive

    Updated February 28,April 3, 2025: Reminder - thisWe have updated the rollout is coming up soon.   timeline below. We are now one month away from this change taking effect. We're removing the EnableAllOcsiClients OneDrive group policy in the Microsoft 365 admin … Availability (Worldwide, GCC, GCC High, DoD): We will be rolling out in April 2025.early May 2025 (previously April). How this will affect your organization: With OCSI enabled for all tenants, …

  1. Updated October 31, 2024: We have updated the content. Thank you for your patience. February 28, 2025: Reminder - this rollout is coming up soon.   We're removing the EnableAllOcsiClients OneDrive group policy in the Microsoft 365 admin …

    • Tags User impact, Admin impact → Updated message, User impact, Admin impact

    Updated October 31, 2024: We have updated the 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 … of conflicts can work properly for end users. Before this rollout, tenants havehad the option to disable thethis feature with a GPO, and when they disable the GPO, existing Office features like autosave, … user collab, and merging in the case of conflicts of Office files.   Autosave is a feature that end users will see in Word, Excel, …

  2. CLONE GALLATIN + AIRGAP We're removing the EnableAllOcsiClients OneDrive group policy in the Microsoft 365 admin …

  3. · first version seen

Learn more

Links from the notice and their documentation checks

No related announcements were found in the saved public history. Check the source for newer announcements.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 23:13 UTC · 274 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 461/469 current