Microsoft Purview Cloud Attachment Hold Preservation Delayed to December 2026

This is the third set of dates the item has carried, so a forecast of "November" should be read loosely.

What Microsoft says the feature will do​

The roadmap description says the feature enables cloud attachment preservation for users put on infinite hold so that file versions shared are preserved across any OneDrive or SharePoint site. Microsoft also says it is a new capability which is different from the existing capability of applying label to cloud attachments and links present in OneDrive and SharePoint and shared in Exchange, Teams, Viva Engage and Copilot.

That last sentence matters most. Microsoft is describing a separate preservation mechanism. It is not presenting this as a new setting inside the retention-label feature Purview administrators already use.

The roadmap does not define "infinite hold." It does not say whether the term means an eDiscovery case hold, Litigation Hold, an indefinite retention policy, or something new. Until Microsoft publishes documentation, treat it as roadmap wording rather than a technical term with a known meaning.

Summary: For users on "infinite hold," Purview is expected to keep the version of a file that was shared, wherever in OneDrive or SharePoint it lives. Microsoft presents this as separate from today's label-based method.

Why cloud attachments are hard to preserve​

A traditional email attachment is a copy of the file, frozen at the moment it was sent. A cloud attachment is a link to a live file that people can keep editing.

Microsoft's retention documentation describes cloud attachments as embedded links to files that users share. They can appear in Outlook emails and in Teams or Viva Engage messages, and Microsoft 365 Copilot and Copilot Chat interactions can reference them. If the file changes after the message is sent, someone reviewing the message later may open a different document from the one the recipient saw. A spreadsheet sent on Monday and quietly edited on Wednesday is a real problem in a lawsuit.

Purview's current answer is retention labels. Microsoft's eDiscovery (Premium) documentation says organizations can use Microsoft Purview retention labels to preserve the version of a document at the time when it was shared as a cloud attachment. Administrators create a retention label, choose the option apply the label to cloud attachments, and then automatically apply the label to documents stored in SharePoint and OneDrive.

According to Microsoft's SharePoint and OneDrive retention documentation, the current method works like this:

• When the label is applied automatically, it goes on a copy of the shared file, and that copy is stored in the site's Preservation Hold library.
• If the original file is edited and shared again, a new copy is saved and labeled as a new version.
• If the file is shared again without edits, the labeled date on the existing copy is updated, which restarts the retention period. For this reason Microsoft recommends starting the retention period from the date the item is labeled.
• The copy is typically created within an hour of sharing.
• If a user deletes or moves the original before the copy exists, files in locations covered by the auto-labeling policy are copied into the Preservation Hold library automatically, with a temporary one-day retention period.
• Exception: items in archived sites (Microsoft 365 Archive) are not retained by an auto-apply cloud attachment policy.

Records manager Joanne Klein summarized the design: the retention label applies only to the version of the file that's being shared or referenced and does not apply to the message it was shared from.

Summary: Purview can already keep shared versions, but only through an auto-apply retention label policy that someone has to design, scope and maintain. The roadmap item describes a hold-based approach instead.

Why a hold-based option could matter​

The label method is built for records management and runs on a retention schedule. Legal holds are tied to specific people and cases and are released when an administrator decides.

Microsoft's eDiscovery documentation says content on hold stays preserved until you release the hold in the case, remove a location, or delete the hold policy. Holds can cover user mailboxes and OneDrive sites, as well as the SharePoint and OneDrive sites connected to Teams and Microsoft 365 groups.

The difficulty is that a custodian (a person whose data is under hold) often shares files stored in someone else's OneDrive or on a team site that isn't part of the case. The roadmap's phrase "across any OneDrive or SharePoint site" suggests the feature is meant to close that gap: hold the person, and keep what they shared wherever the file lives.

That reading is an inference from the roadmap description. Microsoft has not published capture rules, how preserved versions are retrieved, licensing, storage effects, or configuration steps for this feature.

A practical example (illustrative, not a documented scenario): a finance analyst is placed under hold during a contract dispute. Last quarter she shared a pricing workbook from a department team site that is not in the case. A procurement colleague later rewrote half the tabs. Today, preserving the version she sent depends on whether an auto-apply cloud attachment label already covered that site. The roadmap item suggests a future where the hold on her alone is enough.

There is already one related item in Purview. Microsoft's hold troubleshooting guide lists a cld prefix in Exchange InPlaceHolds values, identified as a Cloud attachment hold, which is cleared from eDiscovery case hold policies. Nothing Microsoft has published links that prefix to roadmap item 493752, so don't assume they are the same thing.

Three sets of dates for one feature​

The listing's history should make anyone wary of planning around the new dates:

The M365 Admin tracker recorded the original listing as Release date August CY2025Preview date: July CY2025 with a creation date of May 27, 2025. Microsoft's own release communications feed later showed the item with "February CY2026","June CY2026", "493752". Planet Technologies' roadmap roundup in October 2025 also tagged it June 2026.

By December, general availability will have moved back about 16 months from the original target. Microsoft's roadmap page says its dates are estimates and that all information is subject to change. Slips are common on the Microsoft 365 roadmap, but repeated slips on a preservation feature suggest Microsoft is still working out how to do it reliably at scale. Since preservation features have to work every time to be useful, a delay is preferable to a rushed release.

What administrators should do now​

There are no setup steps to publish yet, and none should be invented. These steps rely only on documented, generally available behavior:

• Don't wait for 493752. If your organization needs shared versions preserved today, the supported option is an auto-apply retention label with the cloud attachments option, scoped to the SharePoint and OneDrive locations involved.
• Start retention from the labeling date. Microsoft recommends this because re-sharing an unchanged file resets the labeled date.
• Turn on versioning. Microsoft notes that new content is not copied to the Preservation Hold library the first time it is edited, and that versioning must be on to retain every version of a file.
• Remember that archived sites are excluded. Auto-apply cloud attachment retention does not cover items in archived sites.
• Watch export sizes. Collecting linked cloud attachments in eDiscovery exports makes the results larger and contains more items.
• Don't touch the Preservation Hold library by hand. Microsoft says editing, moving or deleting automatically retained files there is not supported. Use eDiscovery and other compliance tools to get at them.
• Note the cloud scope. The roadmap lists only Worldwide (Standard Multi-Tenant). GCC, GCC High, DoD and sovereign cloud tenants should not expect this feature in the same timeframe.

Open questions​

The roadmap entry does not answer the questions compliance teams will ask first:

• What counts as "infinite hold," and does it include eDiscovery case holds, Litigation Hold, or both?
• Does preservation capture only files shared after the hold starts, or earlier versions too?
• Where are preserved copies stored, and whose OneDrive storage quota pays for them?
• How do preserved versions appear in eDiscovery collections and review sets?
• What licenses are required?

Microsoft will likely answer these in Message Center posts and Learn documentation when the preview starts. Until then, this is a promising entry on a roadmap whose dates have already moved twice.

Bottom line: Purview's planned hold-based preservation of cloud attachments could make it much simpler to keep the file versions a custodian shared, without depending on carefully scoped retention labels. The feature is still in development, Microsoft has published few details, and it has already missed two release targets. Plan with the retention-label method that exists today.

Update: Purview cloud-attachment preservation slips to 2027 (October 5, 2026)​

Microsoft has again delayed roadmap item 493752. The Purview feature is now listed for preview in March 2027 and general availability in May 2027, replacing the previously stated November and December 2026 targets.

The roadmap still labels the feature “In development” for the web in Worldwide Standard Multi-Tenant tenants. Its description is unchanged: Microsoft intends to preserve versions of cloud files shared by users placed on “infinite hold,” across any OneDrive or SharePoint site, through a mechanism separate from retention labels.

For compliance teams, this is another reason not to plan around the hold-based capability. The supported retention-label approach remains the practical option for preserving shared cloud-file versions today.