Dynamics Community Forum Thread Details

Sudden and Significant Increase in DataverseSearch Storage Consumption

Hi everyone,

Has anyone else recently seen a sharp increase in DataverseSearch (formerly RelevanceSearch) storage usage in their environments?

In our case:

Starting in July 2025, DataverseSearch storage in Production grew from ~3.5 GB to ~18 GB in just a few weeks.
Our Test environment (a recent clone of Production with identical configuration, quick-find views, and searchable columns) is only ~5 GB.
We are not using Copilot Studio, and we haven’t added any files or Dataverse knowledge sources.
Microsoft support says this is due to changes in how Copilot search data is indexed and stored, but I can’t reconcile this with the difference between our Prod and Test usage. Apparently this changed happened around July 7th.

Questions for the community:

Have you been able to identify specific tables, fields, or features that are driving the increase?

Have you found any effective ways to reduce the storage without losing important functionality?

Any insights, telemetry, or experiences would be greatly appreciated.

Thanks,

Alen

Categories:

Hi Allen,

Thanks for sharing your experience—this is a very relevant concern.

Yes, Others Are Seeing It Too
You're not alone. Several organizations have reported a sharp increase in DataverseSearch storage starting around early July 2023, likely tied to backend changes in Copilot indexing, even if Copilot Studio isn’t actively used.
Production vs. Test Discrepancy
The difference between your Prod and Test environments could be due to:
- User activity: More frequent searches in Prod may trigger deeper indexing.
- Telemetry and usage patterns: Copilot-related services may still run in the background in Prod.
- Data freshness: Test environments often have stale or less frequently accessed data.
Storage Optimization Tips
- Review searchable columns and quick-find views—remove fields that aren’t critical.
- Use Dataverse analytics to identify high-impact tables.
- Consider disabling search on large tables that don’t need it.
Microsoft Guidance
- Microsoft may release updated documentation or tooling to help manage this. Keep an eye on the Power Platform Admin Center and release notes.