Druva protects your Microsoft Dynamics 365 environments—including Sales and Customer Service data in Dataverse—with automated backups, granular restore, and optional data-exception alerting.
📝NOTE: Druva for Microsoft Dynamics 365 data protection requires an Enterprise license. To enable the workload for your account, contact support or sales. For license parameters, backup frequency, retention, and supported storage regions, see Getting Started with Microsoft Dynamics 365 Data Protection.
1. Understand the Product and Business Value
Start with why teams adopt Druva for Dynamics 365 and how it fits next to native options:
Introduction to Microsoft Dynamics 365 Data Protection: Problems Druva solves—retention beyond native limits, granular recovery, compliance posture, data-exception awareness, and air-gapped backups.
2. Know What Is Protected
Map backup scope before you design backup sets or recovery expectations:
Protected Data in Microsoft Dynamics 365: Entities, records, relationships, and metadata Druva can back up, including selective versus complete entity coverage.
3. License, Enable, and Meet Prerequisites
Confirm account activation, licensing, regions, and Microsoft-side requirements before you install the app:
Getting Started with Microsoft Dynamics 365 Data Protection: Enterprise license parameters, supported storage regions, and the end-to-end path from installation through monitoring.
Permissions required for Microsoft Dynamics 365: API permissions Druva needs for backup and restore operations.
Configure Backup for Microsoft Dynamics 365 (Prerequisites): Dynamics 365 license, environment membership, System Administrator role, prerequisite banner behavior, and considerations that block backup or restore until resolved.
4. Install, Register, and Configure Backups
Connect your tenant, define backup sets, and align encryption with your security policy:
Configure Backup for Microsoft Dynamics 365: Install the Druva app, register the tenant, review discovered environments, create and manage backup sets, run manual backups, and configure data exception rules.
Enterprise Key Management (BYOK): Customer-managed encryption options; scheduled backups may depend on key management choices described in Getting Started.
5. Use the Console Day to Day
Navigate the workload after configuration to see environments, backup sets, and job activity:
Microsoft Dynamics 365 Overview page: Environment listing, backup set overview, and how to move between key console areas.
Microsoft Dynamics 365 Jobs page: Filter and review backup, restore, and download jobs, including status and job details.
6. Restore, Download, and Validate Recovery
Recover in place, to another environment, or via download, and understand platform constraints that affect outcomes:
Restoring and Downloading Microsoft Dynamics 365 Data: Restore metadata, entities, or settings; download data; ordering constraints and important notes (for example option sets on cross-environment restore).
7. Reports
Track Dynamics 365 backup, restore, and license activity:
Microsoft Dynamics 365 Backup Activity Report: Backup activity over a selected period and customizable report fields.
Microsoft Dynamics 365 Restore Activity Report: Restore activity over a selected period and customizable report fields.
Microsoft Dynamics 365 License Consumption Report: Weekly and monthly license consumption reporting.
8. Monitor, FAQ, Alerts, and Release Notes
Keep operations healthy, answer questions, and stay updated:
Microsoft Dynamics 365 Backup and Restore FAQs: Enablement, Druva roles, permissions, manual backups, and other frequent topics.
Endpoints & SaaS Apps Alerts: Alert catalog entries relevant to Dynamics 365 (backup failures, restore status, license usage, data exceptions).
Manage Druva Administrators: Which administrators can manage Dynamics 365 protection in Druva.
Release Notes - Microsoft Dynamics 365: Latest fixes and features; earlier releases at Archived Release Notes - 2025.