#Backup for Dataverse

Dataverse is the underlying data platform for both Dynamics 365 and Power Platform. Data can be created from many Microsoft services, but AvePoint protection depends on where the data is stored and whether it is accessible through supported Microsoft APIs.

This article explains what data is stored in Dataverse, what Cloud Backup for Dynamics 365 protects, and what is outside the scope of Dataverse backup.

#What data is stored in Dataverse

#Dataverse tables and entities

Dataverse stores structured business data in tables, also called entities, together with metadata such as relationships, permissions, and schema definitions. Dataverse storage is divided into three core types:

• Database storage
  Structured business data, including rows, columns, relationships, and metadata

• File storage
  Attachments and other unstructured files associated with Dataverse records

• Log storage
  Audit logs, change tracking, and system logs

Dataverse runs on Azure and serves as the common data layer for Dynamics 365 and Power Platform applications.

#How Dataverse data is created

Data in Dataverse can be created or updated by multiple Microsoft services.

#Dynamics 365 apps

Dynamics 365 applications such as Sales, Customer Service, and Field Service store their core business records directly in Dataverse. For these workloads, Dataverse is the primary data store.

#Power Platform

Power Platform can also create or update data in Dataverse, including through:

• Power Apps, including model-driven apps and canvas apps that use Dataverse
• Power Pages
• Power Automate flows that write to Dataverse tables

In these scenarios, Power Platform provides the application experience, but Dataverse remains the data store.

#What “Power Platform generated data” means

The phrase Power Platform generated data is often misunderstood.

In this context, it usually refers to:

• Dataverse tables created as part of a Power Platform solution
• Records written to Dataverse by Power Apps or Power Automate flows

It does not refer to:

• Power Apps app definitions
• Power Automate flows
• Power Pages site configuration
• Power BI reports or datasets
• Data stored in external systems that Power Platform connects to (such as SharePoint, OneDrive, SQL, or third-party services)

If data is stored outside Dataverse, it is not Dataverse data, even if a Power Platform application reads from it, writes to it, or references it.

#What AvePoint backs up in Dataverse

Cloud Backup for Dynamics 365 protects Dataverse data that is accessible through supported Dynamics 365 and Dataverse APIs.

#What is supported

Cloud Backup for Dynamics 365 protects:

• Dataverse tables and records
• Data created by Dynamics 365 apps
• Data written to Dataverse by Power Platform apps and flows
• Data written to Dataverse by Planner Premium
• Associated Dataverse metadata (such as relationships), where supported by Microsoft APIs

If the data is stored in Dataverse, it is generally in scope for Dataverse backup. For detailed support information, see supported entities list.

#What is not supported

The following items are not backed up as part of Dataverse backup:

• Dataverse for Teams
• Power Apps app definitions and configurations
• Power Automate flows
• Power Pages site configuration
• Solution packages
• Power BI assets, including report files (.pbix), datasets, and report configuration
• Data stored outside Dataverse, even if referenced by Power Platform, such as SharePoint lists or libraries, OneDrive content, external databases or storage, and virtual tables that reference external systems without storing data in Dataverse

#Known limitations and exclusions

Backup coverage is subject to:

• Microsoft Dataverse API limits and throttling
• Service protection limits enforced by Microsoft
• Licensing and capacity constraints at the tenant level

These limitations apply regardless of whether the data was created through Dynamics 365 or Power Platform.

See Microsoft documentation:
https://learn.microsoft.com/power-apps/maker/data-platform/api-limits-overview

#How Dataverse data is backed up

Cloud Backup for Dynamics 365 backs up Dataverse data through supported Dynamics 365 and Dataverse APIs.

Key points:

• Backups run automatically on a scheduled basis
• Data is captured at the Dataverse layer, regardless of which supported application created it
• Restores are performed back into Dataverse and preserve supported metadata and relationships
• API limits may affect backup throughput or frequency in large or high-activity environments

#Which AvePoint product protects which data

#Dataverse data

Protected by: Cloud Backup for Dynamics 365

Cloud Backup for Dynamics 365 protects Dataverse itself, including:

• Dataverse tables and records
• Data created by Dynamics 365 apps
• Data created by Power Platform apps when Dataverse is the underlying data store

#Power Platform apps and configurations

Power Platform application assets are not Dataverse data and are not included in Dataverse backup. This includes:

• Power Apps app definitions
• Power BI reports
• Power Automate flows
• Power Pages configuration
• Solution files

Dataverse backup protects data stored in Dataverse. It does not protect application definitions or configuration artifacts.

#FAQs

#Is everything in Dataverse backed up?

No. Cloud Backup for Dynamics 365 protects Dataverse data that is accessible through supported Microsoft APIs. Some scenarios, such as Dataverse for Teams and externally referenced data, are not supported.

#Is Dataverse logic backed up?

Partially. Logic stored as Dataverse data or metadata can be included when Microsoft APIs expose it as part of the protected Dataverse content. Power Platform application logic, such as apps, flows, workflows, and configuration, is not backed up as part of Dataverse backup.

#If it is created in Power Platform, is it automatically protected?

Not always.

• Data written into Dataverse is protected by Cloud Backup for Dynamics 365.
• Apps, flows, reports, and configurations are not Dataverse data and are not included.
• Some assets may be protected by other AvePoint products, such as Cloud Backup for Microsoft 365, depending on where they are stored.

#Where does this data live, and why does that matter?

The storage location determines:

• Which Microsoft APIs are used
• Which AvePoint product applies
• What limitations or exclusions exist

Understanding whether data lives in Dataverse, SharePoint, OneDrive, Power BI, or an external system is essential for applying the correct backup product and understanding what is or is not protected.