Dataverse long term data retention overview (preview)

[This topic is pre-release documentation and is subject to change.]

Microsoft Dataverse supports custom retention policies to securely retain unlimited data long term in a cost-efficient way. While Dataverse can support your business growth with no limit on active data, you might want to consider moving inactive data to the Dataverse long term retention store.


  • This is a preview feature.
  • Preview features aren’t meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.
  • For public preview, only non-production environments are allowed for previewing the long-term data retention feature. Production and Dataverse for Teams environments can't be used with this feature.
  • No additional Power Platform licensing requirement is required to experience this feature during the preview. However, there will be a licensing requirement once the feature is generally available.
  • Pricing information for long term data retention will be available at general availability.

Watch this video to learn about Dataverse long term data retention.

Business application data lifecycle

Consider the business application data lifecycle in three stages. First active data, which over time transitions to inactive data, and finally transitions to deleted data.

Business application data lifecycle diagram

Stage Description
1. Active data Data is readily available and transformed via apps.
Accessed across all application workflows.
Also referred to as live data.
2. Inactive data Data is immutable and read-only.
Is stored in long term retention.
Has limited access. Retained for compliance, audit, and legal discovery.
3. Deleted data Permanently deleted. Data lifecycle is completed.

Dataverse delivers native platform support for long term retention of data. It allows organizations to get immediate and ongoing benefits:

  • Securely retain the historical application data long term for audit, legal, and regulatory requirements.
  • Access the read-only data for limited inquiry purposes.
  • Reduce database capacity consumed.
  • Avoid IT investments required to build and maintain custom solutions for long term retention of historical application data.

How it works

Application admins set up custom policies for a table with criterion to retain data long term. The retained data is never moved out of Dataverse, it's stored in a Dataverse managed data lake. The data is always secured with Dataverse security backed by Azure Active Directory.


  • Once data is retained in the Dataverse long term (inactive) store it can't be moved back to the Dataverse live (active) data store.
  • Customers using self-managed encryption key (BYOK) should be aware that long term retained data in the Azure data lake is encrypted with Microsoft managed key. Consider migrating to customer managed key. More information: Migrate bring-your-own-key environments to customer-managed key
  • When a retention policy is run, the process makes API requests in Microsoft Power Platform. These requests are counted towards the existing API requests available with your plan. More information: Requests limits and allocations

Dataverse provides read-only access to the retained data via:

  • Advanced Find within an application.
  • Power Automate cloud flow.
  • Dataverse OData APIs for custom screens.

Types of data retained long term

Dataverse standard (except system) tables, custom tables, along with attachments, can be retained in Dataverse long term storage.


Currently, audit, elastic tables, and images aren't supported for long term retention.

Admins set retention policies on tables when the application maker has enabled long term retention for the table. When a maker enables retention on a parent root table, it also enables retention for all child tables.

Long term data retention and existing delete action and plugins

All the existing delete action cascade relationships and plugins for tables are executed when a data retention policy is run on the table.

More information: Long-term data retention

Storage capacity reports

With Dataverse long term retention, data is never moved out of Dataverse. The reported capacity in the existing Power Platform admin reports includes both live (active) and retained (inactive) data in GBs.

  • Database capacity details reported:

    • Database capacity reported is the sum of the live and retained data. The overall database capacity consumed is reduced depending on the proportion of the data rows retained during a policy run.
  • Notice that the policy run will take 72 to 96 hours to complete and there will be an additional 24 hours afterward for the database capacity reports to appear.

  • When available, the reports display two entries for a table that has been enabled for long term retention:

    • Table, such as Case1 or Contact.
    • Table-Retained, such as Case-Retained and Contact-Retained.

    1 The case table requires a Dynamics 365 app, such as Dynamics 365 Service.

  • File capacity details reported:

    • If there are associated file attachments retained long term, the file capacity reflects the sum of the live and retained data. There will be no reduction or savings observed with file capacity after running a retention policy, which involved file attachments.

Log capacity reports aren't currently available.

Viewing the capacity reports

Imagine a non-production scenario where all the live data for the case and contacts tables are retained with Dataverse long term retention. After the long term retention policy is successfully completed, there are entries for Case-Retained and Contact-Retained in the report. The reduction in database capacity consumed depends on the number of rows and column data types involved in the retention process.

Storage capacity report that includes retained table data


  • If the tables are not visible in the report, export the view to an Excel worksheet by selecting the three vertical bars on the top right of the capacity report, and then select Download all tables.
  • If a table commonly has associated child tables, the capacity reports also display the child table-retained GB size.

For more information about capacity reports, go to New Microsoft Dataverse storage capacity.

Solution aware retention policies

Dataverse retention policies are solution aware. Dataverse retention policies added to a solution are known as solution-aware retention policies. You can add multiple retention policies to a single solution. Retention policies are added to an unmanaged solution. This helps makers follow application lifecycle management (ALM) best practices when working with Dataverse retention policies.

When you include your retention policies in a solution, their definitions become portable, making it easier to move them from one environment to another, saving time required to create the retention policy. For example, you first develop a solution containing a retention policy in a development or sandbox environment. You then move that retention policy to a pre-production environment to test and validate that the solution works well and is ready for production. After testing is completed, the admin imports the solution into the production environment.


  • The data retained by retention policies isn't portable as part of solutions, only the retention policy definitions are. You must run the retention policy in an environment to retain the data in Dataverse long term storage.
  • Only retention policies created in Power Platform environments can be solution-aware.

You create a solution before you add a retention policy to it. Exporting and importing solutions containing retention policies is the same as with other solution components.

For more information about solutions and solution components, go to Solutions overview.

Next steps

Set a data retention policy for a table
Share your ideas