Find reason for huge increase in Dataverse capacity

(1) Share

Report

Posted on by ConnorD365Insight

How can I find out exactly what is behind a large increase in Dataverse capacity? For example, see the screen shots below regarding an increase that occurred. It was found to be primarily related to the Dataverse Search table but there is no reporting available that indicates what actually was behind the increase. Outside of the already existing capacity reporting available in the PPAC, how can we find out what happened? There was no increase in user activity, there were no dev, test, implementation of any solutions during this time. How do we get to the root cause of this increase?

Before:

After increase:

I have the same question (3)

All responses (2)

Answers (0)

Suggested answer

wolenberg_ 1,013 Moderator on at

Like (1)

Report

Find reason for huge increase in Dataverse capacity

Hello , just FYI the screenshots that you putted are not fully loaded in the comments section, So we can't see it.

But anyways I have an idea wich can be the issue.

Root Cause: Enhanced Semantic Indexing

Starting around mid-2025, Microsoft began rolling out enhanced semantic indexing for Dataverse Search. Even if you didn’t explicitly enable Copilot features, this indexing may have been automatically activated in your environment to support future AI-powered experiences like Copilot Studio, Sales Copilot, A and others B.

This change:

• Adds AI-style indexes to your Dataverse Search table.
• Increases storage usage significantly — some users reported jumps from 3.5 GB to 18 GB in production A environments.
• May not affect test environments if the rollout hasn’t reached them yet.

How to Investigate Further

1. Check Feature Rollout Timing

• Visit the Microsoft 365 Message Center and look for posts about Dataverse Search enhancements around April–July 2025.
• Confirm if your environment was part of the rollout.

2. Compare Environments

• If you have a test or dev environment cloned from production, compare the Dataverse Search table size.
• If the test environment is smaller, it likely hasn’t received the enhanced indexing yet.

3. Review Search Configuration

• Go to Power Platform Admin Center (PPAC) → Environment → Settings → Product → Features.
• Look for Dataverse Search settings:
⁠◦ You may be able to disable enhanced indexing if not needed.
⁠◦ Note: Disabling may affect Copilot and global search experiences.

4. Use Telemetry Tools

• Consider using Microsoft Power Platform telemetry via Azure Monitor or Application Insights (if enabled).
• These tools can help trace which tables or operations triggered indexing changes.

5. Open a Microsoft Support Ticket

• If the increase is unexplained and persistent, Microsoft support can provide backend diagnostics not visible in PPAC.

Remember:
Even if Copilot features aren’t actively used, Dataverse Search indexing may still run to prepare for future AI experiences. You can manage this proactively by adjusting search settings or limiting searchable columns.

If this answer helped you or could help others in the community, feel free to give it a like or kudo — it helps surface useful solutions for everyone!

Was this reply helpful? Yes No
ConnorD365Insight 13 on at

Like (0)

Report

Find reason for huge increase in Dataverse capacity

@wolenberg_- Thank you for your reply. Trying again here to attach the images.

Was this reply helpful? Yes No