Direct answer: the Veeam Backup for Microsoft 365 v8 documentation reviewed on August 21, 2026 lists Microsoft Exchange, SharePoint, OneDrive, and Teams data. It does not list Dynamics 365 or Microsoft Dataverse as protected workloads. Do not assume that buying Veeam Backup for Microsoft 365 protects Dynamics data. Require Veeam or a service provider to identify a separate generally available product and contractual scope if Dynamics protection is being proposed.
Dynamics 365 is not simply another Microsoft 365 workload. Many Dynamics applications store business data in Dataverse environments, while some application data, analytics, integrations, secrets, or connected services can sit outside the core Dataverse database. A recovery plan must start with the application and environment inventory rather than the Microsoft brand name.
Available Protection Routes
| Route | Documented scope | Best fit to investigate | Critical evidence gap |
|---|---|---|---|
| Power Platform native backup | Automatic environment backups for environments with a database, plus supported manual backup and environment restore operations. | Short-window operational rollback and recovery within Power Platform administration. | Default retention is seven days; production managed environments can be configured up to 28 days. Confirm environment and application exclusions. |
| Veeam Backup for Microsoft 365 | Official v8 introduction lists Exchange, SharePoint, OneDrive, and Teams, not Dynamics 365 or Dataverse. | M365 protection alongside a separately solved Dynamics requirement. | No documented Dataverse protection path was found in the reviewed product documentation. |
| Purpose-built Dynamics service | Varies by vendor. Commvault, for example, publishes a current Dynamics 365 backup offering. | Longer retention, SaaS operation, or Dynamics-specific recovery beyond the native window. | Table, relationship, attachment, solution, audit, application-service, and restore-destination fidelity must be demonstrated. |
| Controlled API export | Buyer-designed extraction through supported Dataverse APIs or data services. | Portability, analytics copies, or requirements not met by a packaged backup product. | An export is not automatically a restorable backup; schema, relationships, security, attachments, and replay order become buyer responsibilities. |
What Native Backup Actually Means
Microsoft documents automatic backups for Power Platform environments that have a database. The default retention for production and nonproduction environments is seven days. For production managed environments, administrators can set 7, 14, 21, or 28 days. Manual backups can be created for production, sandbox, Teams, and developer environments, but not the default environment. Microsoft also states that downloading a database backup for offline use is not supported.
Environment restore is valuable, but it is different from selecting one damaged business record and restoring it in place. The target must meet Microsoft's environment and capacity rules, and application-specific documentation may identify data or services that do not return through a standard Dataverse environment restore. Record those exclusions for Sales, Customer Service, Field Service, Customer Insights, or any other deployed application.
Recovery Requirements Matrix
| Layer | Examples | Acceptance test |
|---|---|---|
| Business records | Accounts, contacts, opportunities, cases, activities, and custom tables | Recover selected records without breaking required references |
| Relationships and ownership | Lookups, activity parties, business units, teams, owners, and sharing | Verify identifiers, references, ownership, and access after recovery |
| Files and history | Notes, attachments, file columns, audit data, and timeline content | Recover content and prove which history is included or excluded |
| Application configuration | Solutions, forms, views, workflows, plug-ins, apps, and flows | Open the restored application and execute a representative process |
| External dependencies | Customer Insights data, secrets, connectors, data lakes, and integrations | Reconnect safely and reconcile data created during the recovery window |
Run a Dynamics Recovery Exercise
- Inventory environments and applications. Record type, managed status, region, database, installed Dynamics apps, storage, integrations, and owner.
- Classify recovery scenarios. Separate one-record deletion, bulk data corruption, failed customization, compromised integration, and full environment loss.
- Map each data layer. Identify Dataverse tables, relationships, files, audit data, solutions, flows, application services, and external stores.
- Select a safe target. Confirm target-environment, capacity, policy, region, and production-to-sandbox requirements in current Microsoft documentation.
- Restore and reconcile. Validate business records and application behavior, then account for transactions created after the selected restore point.
- Record evidence. Keep timings, operator steps, exclusions, errors, broken references, reconnection work, and business-owner acceptance.
Worked Example: Sales Data Corruption
A faulty integration updates 20,000 opportunity records and related contacts. The business detects the problem three days later. A native environment restore point is still within the documented seven-day default window, but restoring the full environment can also roll back valid changes made after the selected point.
The recovery team first stops the integration and preserves evidence. It compares three paths: full environment restore to an approved target followed by validation; targeted repair from an independently captured export; or a third-party object-level recovery if the contracted product supports the affected tables and relationships. The chosen path must preserve account, contact, opportunity, activity, owner, and custom-table references. "The records are present" is not sufficient if sales processes, permissions, or integration checkpoints are broken.
API Extraction Without Misstating Throttling
Dataverse enforces entitlement and service-protection limits. HTTP 429 means the service is rate-limiting requests; it is not a timeout. More threads do not inherently prevent throttling and may make it worse. A controlled exporter should minimize unnecessary requests, use supported pagination or change-tracking patterns, limit concurrency, honor server retry guidance, checkpoint progress, and expose incomplete tables. Review the separate Microsoft Graph backup guide for M365 workloads, but do not apply Graph assumptions to Dataverse without verification.
Verification Checklist
- The proposed product expressly names Dynamics 365 or Dataverse in current official documentation and the contract.
- Native retention is recorded for every environment type and managed-environment setting.
- Restore targets, capacity, region, enterprise policies, and application-specific exclusions are documented.
- Tables, relationships, activities, attachments, audit data, solutions, flows, and external services have recovery paths.
- API exports respect service-protection limits and are proven restorable rather than merely downloadable.
- The recovery exercise includes post-restore reconciliation and business-owner acceptance.
Where North Brook Vault Fits
North Brook Vault does not currently back up or restore Dynamics 365 or Dataverse. It must not be shortlisted for that requirement. It can be evaluated separately for supported Exchange, OneDrive, SharePoint, and Teams-related objects when an organization needs an M365 service alongside its Dynamics strategy. Current North Brook gaps also include no native Object Lock configuration, no OneDrive file-version-history capture, no Teams message restore, no export, and no compliance report. Review the M365 backup shortlist and service responsibility model for that separate decision.
Official Sources
- Veeam Backup for Microsoft 365 v8 introduction; accessed August 21, 2026.
- Microsoft Power Platform: back up and restore environments; accessed August 21, 2026.
- Microsoft Dataverse API limits overview; accessed August 21, 2026.
- Microsoft Dataverse query throttling; accessed August 21, 2026.
- Commvault Microsoft Dynamics 365 Backup; accessed August 21, 2026.