web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Sudden and Significant Increase in DataverseSearch Storage Consumption

(6) ShareShare
ReportReport
Posted on by 19

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:


  1. Are you seeing similar sudden spikes in DataverseSearch usage?


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


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


  4.  

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

 

Thanks,

Alen

Categories:
I have the same question (22)
  • Suggested answer
    DAnny3211 Profile Picture
    11,397 on at

    Hi Allen,

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

    Here are a few thoughts and suggestions:

    1. 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.

    2. 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.
    3. 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.
    4. 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.

    Let me know if this helps, and please mark the response as helpful if it answered your question 😊

    Best regards!

  • Suggested answer
    Nour Abuzaid Profile Picture
    197 on at
    ->Around July 2025, Microsoft rolled out enhanced semantic indexing in
    Dataverse Search → this adds Copilot-style AI indexes even if you don’t use Copilot.

    ->That’s why Prod spiked (auto-enabled) but Test stayed smaller (not yet applied).

    -> These indexes count against database capacity → hence the jump from 3.5 GB → 18 GB.

    What you can do:
    1-In Power Platform Admin Center, check if enhanced search indexing is enabled → turn it off if not needed.
    2-Audit Quick Find views / searchable columns → remove large fields (emails, long text, attachments).
    3-Use Capacity → Consumption per table to identify which tables are blowing up storage.

    Note: cleanup isn’t instant → expect some lag after changes.
  • AZ79 Profile Picture
    19 on at

    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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Siv Sagar Profile Picture

Siv Sagar 93 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 76

#3
Martin Dráb Profile Picture

Martin Dráb 64 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans