Notifications
Announcements
No record found.
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:
Are you seeing similar sudden spikes in DataverseSearch usage?
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
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:
Storage Optimization Tips
Microsoft Guidance
Let me know if this helps, and please mark the response as helpful if it answered your question 😊
Best regards!
Hi @Nour Abuzaid,
Thanks for your help. When you say:
1 – In Power Platform Admin Center, check if enhanced search indexing is enabled → turn it off if not needed.
By “enhanced search indexing,” do you mean the Dataverse Search section (see screenshot)?
From what I can tell, that option only lets you disable the search bar entirely. We’d like to keep the search functionality, but continue using the older Global Search instead of the Copilot-style AI indexes.
Is there another setting where only the AI indexing can be disabled, while keeping Global Search available?
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Siv Sagar 93 Super User 2025 Season 2
#ManoVerse 76
Martin Dráb 64 Most Valuable Professional