Microsoft 365 Retention Policies sit at the core of compliance, governance, and information lifecycle management.

But in large environments, several fundamental limitations still make them difficult to manage safely and at scale.

Based on operating Retention Policies across 100,000+ SharePoint sites, two issues stand out as persistent risks that Microsoft should address urgently.

1. No Export Capability for Retention Policy Scope

In Microsoft Purview, administrators can see which SharePoint sites are included in a Retention Policy—but cannot export that list.

This is a surprising gap:

• Adaptive Scopes UI already supports export
• Large tenants require offline review and audit
• Policy validation at scale becomes impractical

Real-world impact

Without export, the only option is scripting:

• Enumerate every site in the tenant
• Query retention assignments individually
• Map GUIDs back to policy names

At 100k+ sites, this takes hours of runtime and significant compute—just to answer a basic governance question:
“Which sites are in this policy?”

Recommendation to Microsoft

Add an Export option to the Retention Policy scope UI (parity with Adaptive Scopes).
This would immediately improve auditability and reduce operational overhead.

2. Retention Scope Includes Teams Channel Sites Without Lifecycle Alignment

The “SharePoint classic and communication sites” retention scope currently includes Teams Channel Sites.

This creates governance and compliance gaps because Channel Sites are tightly coupled to Teams—but retention and deletion behavior is not.

Problem 1: Orphaned Channel Sites

When a Team is deleted:

• Channel Sites remain
• Even if the Team had no retention
• Ownership becomes unclear

Large tenants accumulate orphaned sites requiring manual identification and cleanup.

Problem 2: Residual Access to Sensitive Content

Users assume deleting a Team removes all content.

But Channel Sites persist, and previous permissions often remain.

This creates:

• Unexpected data exposure
• Compliance risk
• Legal risk

This is not an edge case—it affects every Microsoft 365 tenant using Teams.

Recommendation to Microsoft

• Exclude Channel Sites from generic SharePoint retention scopes
• Align Channel Site lifecycle with Teams lifecycle
• Or provide admin controls to enforce deletion linkage

Compliance tooling must respect the architectural coupling between Teams and SharePoint.

Why These Gaps Matter

Retention Policies are among the most critical controls in Microsoft 365.

Yet today they still lack:

• Exportable scope visibility
• Proper handling of Teams-connected sites

At enterprise scale, these are not inconveniences—they are governance risks.

---

Final Thoughts

Microsoft 365 Retention is powerful—but still operationally fragile in large tenants.

For organisations managing tens or hundreds of thousands of sites, current limitations create unnecessary complexity and compliance exposure.

Microsoft should prioritise:

• Exportable policy scopes
• Teams-aligned Channel Site retention

These are foundational improvements that would immediately increase trust and manageability in Microsoft 365 compliance tooling.