SharePoint site about to hit 1000GB metadata threshold

Question

SharePoint site about to hit 1000GB metadata threshold

Justin Graham 0

Hi,

Our site has accumulated 985GB of meta data across 3 SharePoint lists. It is now about to hit the limit in a few weeks and we are unsure what to do. The lists hold historic data which is still in use today for checking purposes. The lists have a large number of columns. when it moves into this list we trim off the version history. so its purely the weight of the historical data over the large number of columns it has. We are unsure what do to about this meta data, and when the limit is reach what problems we are facing here. Can Microsoft provide us with any help?

Thanks,

Justin

Joel Plaut 0 Reputation points MVP

2026-09-02T02:21:37.2733333+00:00
@Justin Graham The three lists are already close to the SharePoint Online site metadata limit:

List 1: 1.62M items / 536 GB metadata

List 2: 515K items / 370 GB metadata

List 3: 229K items / 64 GB metadata

One area that stands out is List 2. Although it contains significantly fewer items than List 1, it consumes a large portion of the metadata capacity. This suggests that the metadata footprint may be influenced by the list design and stored properties, not only the number of records.

I would recommend approaching this in three steps:

Identify the metadata contributors

Review the lists at column and workload level:

Column types and usage.

Lookup, Person, Managed Metadata, and multi-value fields.

Version history growth.

Attachments.

Automated updates from Power Automate or integrations.

Reporting/search dependencies.

The objective is to understand which components are creating the highest metadata consumption.

Review the current information model

For long-running historical lists, review whether the current structure is still suitable.

Questions to consider:

Are historical records using the same metadata model as active business records?

Are all columns required for historical lookup?

Are reporting requirements driving unnecessary metadata storage?

Can some historical attributes be preserved in a simplified reference model?

The goal is not simply reducing columns, but ensuring the schema matches the business purpose.

Validate a target design before making large changes

Before moving millions of items or deleting metadata:

Select a representative data sample.

Apply the proposed design changes.

Measure metadata reduction.

Validate Power Apps, Power Automate, Power BI, search, and compliance requirements.

A possible future-state pattern could be:

Operational Data → Historical Reference → Archive

where active workloads remain optimized, while older information remains available through a controlled historical model.

Given the current consumption level, a detailed assessment of List 2 and its metadata composition would help identify the main contributors to the higher metadata footprint and determine whether schema optimization, lifecycle redesign, or data restructuring is the most suitable remediation approach.

Hope this provides a different way to approach the issue.

1 answer

Your answer

Answer 1

Dear @Justin Graham,

I hope you’re having a good day.

Thank you for providing the details.

Based on your description, this appears to be a very large SharePoint Online deployment with several historical lists that remain actively referenced and contain a significant number of columns.

Microsoft has documentation describing situations where a site is approaching or has reached the metadata limit, and the warning is typically surfaced through the site's Storage Metrics page.

To better understand your situation, could you clarify how the reported 985GB metadata value was obtained? For example, was it reported through Storage Metrics, provided by Microsoft Support, or generated by another reporting tool?

In the meantime, there are several areas that may be worth reviewing:

Evaluate whether older historical records can be archived to a separate site or archive solution while remaining available for reference.
Review the list schema and determine whether any columns are no longer required.
Consider whether large historical datasets can be distributed across multiple lists or sites rather than continuing to grow within the same location.
Depending on your retention and reporting requirements, consider partitioning historical data by year, archive period, or business area to help manage future growth.
Verify that version history retention remains appropriately configured and that unnecessary versions are not being retained.

Given the scale of the environment you described, I would strongly recommend opening a Microsoft Support ticket before the threshold is reached. While the Microsoft Q&A forum can provide general guidance, the support team can perform a tenant-specific assessment of your environment, including:

Reviewing the affected site and lists in detail.
Validating the reported metadata usage and growth trend.
Identifying which lists, libraries, columns, or design patterns are contributing most to the metadata footprint.
Assessing potential risks specific to your site architecture and workload.
Providing recommendations tailored to your environment, such as archival strategies, list/site partitioning, schema optimization, or other design changes where appropriate.

Because the impact of approaching a service limit can depend on the specific configuration and usage patterns of a site, a support case is the best way to obtain an accurate analysis and guidance based on your actual environment rather than general recommendations.

You can raise support ticket from Microsoft 365 Admin Center>Support>Help & Support.

For reference:  Get support | Microsoft Docs  

User's image

I hope this information helps point you in the right direction. If you run into any issues while trying the steps, or if something still doesn’t feel quite right, please don’t hesitate to reach out again. I’ll do my best to support you however I can.

Looking forward to hearing back from you with any updates or additional details.

Warm regards,

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Justin Graham 0 Reputation points

2026-07-07T12:09:59.99+00:00

Hi,

Thank you for your response. in answer to your question, we are not completely sure but are strongest suspicion is that its purely the weight of the historical data (going back 4+ years) over the large number of columns it has.

As of last week:

List 1 has... Metadata Size (GB) of 536.1 / List Items of 1,623,071 / List Columns of 79

List 2 has... Metadata Size (GB) of 370.1 / List Items of 515,650 / List Columns of 117

List 3 has... Metadata Size (GB) of 64.6 / List Items of 229,431 / List Columns of 66

and these 3 lists are on one SharePoint site.
Justin Graham 0 Reputation points

2026-07-07T12:10:31.61+00:00

Hi,

Thank you for your response. in answer to your question, we are not completely sure but are strongest suspicion is that its purely the weight of the historical data (going back 4+ years) over the large number of columns it has.

As of last week:

List 1 has... Metadata Size (GB) of 536.1 / List Items of 1,623,071 / List Columns of 79

List 2 has... Metadata Size (GB) of 370.1 / List Items of 515,650 / List Columns of 117

List 3 has... Metadata Size (GB) of 64.6 / List Items of 229,431 / List Columns of 66

and these 3 lists are on one SharePoint site.