How to reduce Dataverse capacity used by Email Analytics entity in Dynamics 365 CRM?

(2) Share

Report

Posted on by AM-07081436-0

Hi all,
We’ve noticed that the Email Analytics entity in our Dataverse environment is consuming a significant amount of storage. This is impacting our overall capacity limits.
Is there a recommended way to reduce or clean up the space occupied by Email Analytics data in CRM?
Some specific questions:

Can this entity's data be deleted or archived safely without affecting core functionality?
Is there a setting to disable Email Engagement or Analytics tracking?
Are there retention policies or system jobs that can be configured to limit this data growth?
Would disabling relationship insights or similar features help?

Any guidance, best practices, or cleanup scripts would be highly appreciated!
Thanks in advance.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

DAnny3211 11,421 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hello,

Thanks for raising this important topic!

The Email Analytics entity can indeed consume a significant amount of Dataverse storage, especially in environments with high email activity and engagement tracking enabled.

Here are a few suggestions to help manage and reduce storage usage:

Disable Email Engagement: If you’re not actively using email tracking features, you can disable Email Engagement under Relationship Insights settings. This will stop new data from being generated.

Retention Policies: Check if there are any system jobs or retention policies that can be configured to automatically delete older analytics data. These may be available via the Power Platform Admin Center or through custom workflows.

Manual Cleanup: You can use Advanced Find or Dataverse API to identify and delete older or unnecessary records from the Email Analytics entity. Be cautious and test in a sandbox first.

Archiving Strategy: Consider exporting older data to an external storage (e.g., Azure Blob Storage or SQL) before deletion, if historical analysis is needed.

Review Relationship Insights: Disabling Relationship Insights or related features like Auto Capture may also help reduce data generation.

Let me know if this helps or if you’d like assistance with a cleanup script or automation strategy.

Was this response helpful? Feel free to mark it as such or reply with more details if needed.

Best regards,
Daniele

Was this reply helpful? Yes No