Microsoft is updating SharePoint metadata size reporting beginning October 20, 2026, giving administrators a more complete picture of how much metadata their sites are using.
The change affects SharePoint Online, including document libraries and lists. Microsoft says the updated calculation will include document library field data that was not fully reflected in previous reporting.
The underlying 1 TB site metadata limit is not changing. What is changing is how SharePoint calculates and reports usage.
For most organizations, Microsoft expects little or no noticeable impact. However, sites already approaching the 1 TB threshold could see their reported metadata size increase enough to trigger warnings—or, in some cases, prevent new metadata from being added.
What Microsoft Is Changing in SharePoint
The central change is straightforward: SharePoint will use a more complete calculation when reporting site metadata size.
Document library field data will now be included in the calculation, giving administrators a broader view of metadata consumption across their sites.
That distinction matters because a site may appear to have more metadata after the update even though nobody has added new content.
Microsoft says the change does not mean SharePoint will move, delete, or otherwise modify existing content. The difference is in measurement and enforcement rather than a content migration.
The key points are:
- The 1 TB metadata limit remains unchanged.
- Document library field data will be included in metadata calculations.
- Reported metadata usage may increase for some sites.
- Existing content will remain in place and accessible.
- Most organizations are expected to see little or no behavioral change.
- Sites that exceed the limit may be prevented from adding new metadata.
For administrators, the important takeaway is that a higher number in SharePoint’s reporting does not necessarily mean the organization suddenly generated additional metadata. It can reflect the more complete calculation being introduced.
When the SharePoint Update Begins
Microsoft says the worldwide General Availability rollout will begin on October 20, 2026.
There is also a specific provision for sites already identified as being likely to reach or exceed the 1 TB metadata limit.
Those sites will be excluded from the initial rollout, giving organizations additional time to reduce metadata usage before the revised calculation is applied.
That could be particularly relevant for large SharePoint environments where administrators are already monitoring sites close to the threshold.
Who Needs to Pay Attention?
The change is most relevant to organizations with large or heavily used SharePoint sites.
Microsoft identifies several groups that may be affected:
- SharePoint administrators monitoring site storage and metadata usage.
- Organizations with sites near the 1 TB metadata threshold.
- Site owners receiving metadata warnings.
- Users whose actions create or update metadata on sites that reach the limit.
For smaller sites that are comfortably below the threshold, the update is unlikely to create a significant operational issue.
The greater concern is for sites where existing usage has left little room before the 1 TB ceiling.
Why the 1 TB Limit Matters
The limit itself is not new, but the revised reporting could change how close some sites appear to be to it.
A site that previously appeared to have substantial headroom could show a higher metadata figure once document library field data is incorporated.
That becomes important when a site reaches the enforcement threshold.
According to Microsoft’s update, a site that reaches or exceeds the 1 TB metadata limit can be blocked from adding new metadata until its usage is reduced below the limit.
This does not mean the site’s existing content disappears.
Existing content remains accessible, but actions that require additional metadata may be affected while the site is over the limit.
That distinction is important for organizations relying heavily on SharePoint document libraries, lists, and structured metadata.
What Happens When a Site Gets Close to the Limit?
SharePoint will provide warnings when a site approaches the metadata limit.
For sites reaching 80% of the metadata limit, administrators can review a metadata size breakdown through the Storage Metrics page.
That gives IT teams an opportunity to investigate usage before the site reaches the point where new metadata additions are blocked.
The Storage Metrics page should therefore become an important monitoring location for administrators managing larger SharePoint environments.
A warning should not necessarily be treated as an immediate outage risk. Instead, it provides an opportunity to identify what is consuming metadata and determine whether older or unnecessary material can be removed.
What Organizations Can Do Before the Rollout
Microsoft says no action is required for most organizations.
Still, administrators responsible for sites approaching the limit may want to review their current metadata usage before October 20.
Potential cleanup steps include:
- Reviewing the Storage Metrics page for sites at or above 80% of the limit.
- Removing unnecessary list and document library items.
- Deleting older file versions where they are no longer required.
- Identifying and removing duplicate files across lists and libraries.
- Following recommendations contained in SharePoint’s in-product warnings.
- Rechecking Storage Metrics after cleanup activities.
The goal is not to change the 1 TB limit—it is to create enough headroom that the revised calculation does not push a site into enforcement.
Version History Could Be Worth Reviewing
One area administrators may want to examine is older file versions.
Document libraries can accumulate substantial historical data over time, particularly in environments where files are frequently edited.
Microsoft specifically recommends deleting older file versions as one possible way to reduce metadata usage.
Organizations should, of course, consider their retention, legal hold, compliance, and records-management requirements before deleting historical material.
A cleanup exercise should not inadvertently remove information that the organization is required to retain.
Compliance and Retention Considerations
The update also has implications for organizations that use SharePoint as part of their compliance and records-management processes.
Microsoft’s documentation for the change indicates that exceeding the metadata limit can affect actions that add metadata. That means some creation or update operations could be affected if a site is over the limit.
At the same time, the update does not indicate that existing content will be removed or that retention policies and holds are simply being switched off.
The practical issue is operational: a site at or above the threshold may need to reduce usage before users can continue adding new metadata.
Organizations with strict retention requirements should therefore distinguish between cleanup that is permitted and content that must remain protected under applicable policies or holds.
What Administrators Should Watch After October 20
Once the rollout begins, administrators should compare their SharePoint usage reports with previous measurements rather than assuming every increase represents new activity.
A higher reported metadata size may simply reflect the new calculation.
Teams should pay particular attention to:
Reported metadata growth: Is the increase consistent with the newly included document library field data?
Sites approaching 80%: These sites have less room for unexpected increases and should be monitored closely.
Warning messages: SharePoint may identify sites that are approaching or have reached the metadata threshold.
Sites at or above 1 TB: These require more immediate attention because new metadata additions can be blocked.
Post-cleanup measurements: Administrators should return to Storage Metrics after making changes to confirm that usage has fallen.
The Bigger Picture for SharePoint Administrators
The update illustrates why storage monitoring in SharePoint is more than simply tracking the size of uploaded files.
Metadata plays a central role in how organizations classify, organize, search, filter, and manage information. As SharePoint environments grow, the volume of structured information associated with documents and lists can become increasingly important.
A more complete reporting calculation gives administrators a clearer view of that footprint.
The trade-off is that some sites may suddenly appear closer to the existing limit than they did under the previous calculation.
For organizations operating large SharePoint estates, that makes proactive monitoring more useful than waiting for an enforcement message.
What Happens Next?
The first major date to watch is October 20, 2026, when Microsoft’s worldwide rollout is scheduled to begin.
Most organizations are unlikely to need to make changes. The primary concern is concentrated among sites that are already close to the 1 TB metadata limit or have been identified as likely to reach it.
For those environments, the period before rollout provides an opportunity to review Storage Metrics, identify unnecessary data, check version history, and confirm that cleanup activities do not conflict with retention or compliance requirements.
The important point is that SharePoint’s 1 TB metadata limit is staying in place. What changes is the visibility into how much metadata a site actually contains.
As the revised calculation rolls out, administrators may see higher numbers without seeing any corresponding change in their content. The sites that matter most will be those where that reporting adjustment moves usage close to—or beyond—the existing limit.
Extra posts:
Interactive web site using SharePoint Communication Site for your company 
SharePoint FAQ Content Update Flow Is Being Retired: What Authors Need to Know 
Branding Your SharePoint Site for Your Organization 
Collaborate with Guests in a SharePoint Online Site A Complete Guide 
SharePoint 2013 Workflow Retirement: What It Means for Your Business Create SharePoint Online Site from SharePoint Online Admin