(Updated) SharePoint Embedded apps can now archive containers to reduce storage costs and improve Copilot results [MC1215074]

Message ID: MC1215074 (Updated)

Updated February 4, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Non-Microsoft SharePoint Embedded applications now support container archival. This feature helps organizations reduce storage costs by up to 75% by moving large or inactive content to low-cost storage tiers. It also improves Copilot search relevance by prioritizing active content and reducing noise from outdated data.

[When this will happen:]

• Public Preview: Rollout will begin in early February 2026 and is expected to complete by mid-March 2026 (previously late February).

[How this affects your organization:]

Who is affected: Admins managing SharePoint Embedded applications and developers integrating with SharePoint Embedded APIs.

What will happen:

• New Graph APIs will be available to archive and unarchive containers, enabling integration with your application workflows.



• SharePoint Admin Center will include options to archive and reactivate containers alongside existing container management capabilities.
• Archival support is OFF by default. To enable this functionality, you must opt in using a PowerShell cmdlet.

[What you can do to prepare:]

• Enable archival support by running the appropriate PowerShell cmdlet:  
  • For a new container type: Use New-SPOContainerType with the parameter -IsArchiveEnabled. Learn more: New-SPOContainerType (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn.
  • For an existing container type: Use Set-SPOContainerType with the parameter -IsArchiveEnabled. Learn more: Set-SPOContainerType (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn.
• Update your application to handle archived container status and display appropriate messaging to end users.
• Optionally, expose archival and reactivation options in your application interface.
• Review documentation for Graph API integration and PowerShell cmdlet usage.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft

<<< [MC1215074] Archive
Tooltip: View earlier revisions of this post

Latest Posts