Protecting Microsoft Power Platform with Druva
Druva provides cloud-native backup and recovery for Microsoft Power Platform Power BI and Power Apps. This hub article is your single starting point — it maps every available resource to a task, so you always know where to go next, whether you're setting up protection for the first time or recovering critical data.
What Does Druva Protect?
Druva currently supports backup and recovery for Microsoft Power BI workspaces, including reports, datasets, and dataflows, and for Power Apps environments, canvas apps and component library details. Support for additional Power Platform workloads (Power Automate) will be added in future releases.
📌 Before you begin:
Review and complete the Microsoft-side prerequisites required for discovery and backup:
Power BI: Configure the Entra ID security group and grant the group access to Power BI/Fabric Admin APIs.
Power Apps: Complete the Power Apps Backup Prerequisite by registering an Admin Management Application with Microsoft Power Platform.
For an overview and detailed instructions, see Authorizing Tenant Environments for Power Platform Protection.
Make sure you review Supported Data Types and Limitations, Considerations and Known Issues to understand the scope of protection.
Supported Storage Regions
Druva protects Power Platform data by storing backups in the following Microsoft Azure regions:
East US (
eastus)Southeast Asia (
southeastasia)West US 2 (
westus2)Germany West Central (
germanywestcentral)Australia East (
australiaeast)UK South (
uksouth)Central India (
centralindia)
Licensing
One Druva Power Platform backup license gives a user access to backup of Power BI, Power Apps, and Power Automate (when Power Automate is supported). Customers who have Power Platform enabled automatically receive Power Apps in addition to the previously released Power BI workload.
A license is consumed by any unique user who holds a creator role in a non-empty backed-up workspace or environment. The roles that count toward license consumption are:
Power BI workspaces:
Admin
Member
Contributor
Power Apps environments:
Environment Admin
Environment Maker
CoOwner
For more information, see Licensing.
Your Journey at a Glance
Enable Protection → Install & Configure Druva App → Authorize Tenant → Set Backup Profiles → Protect Power BI & Protect Power Apps → Monitor & Manage
Step 1 — Understand and Enable Protection
Start here if you are new to Druva's Power Platform support.
Article | What It Covers |
A high-level look at what Druva protects, the architecture, supported regions, and key capabilities. | |
How to turn on Power Platform protection in the Druva console. | |
Roles and permissions your Microsoft 365 admin account must have before setup. | |
A complete list of Power Platform data types and entities that Druva backs up. |
Step 2 — Install, Configure, and Connect
Set up the Druva app in your Microsoft environment and connect your tenant.
Article | What It Covers |
End-to-end walkthrough for installing the Druva app and completing initial setup. | |
How to deploy the app across your tenant and configure encryption settings. | |
Granting Druva access to your Microsoft tenant and Power Platform environments. | |
A guided tour of the main Power Platform dashboard in the Druva console. |
Step 3a — Protect Power BI
Configure backups for your Power BI workspaces once your environment is connected.
Article | What It Covers |
Understand the Power BI-specific view — workspace list, status, and snapshot data. | |
Overview of backup configuration options available for Power BI workspaces. | |
Step-by-step guide to manually selecting and protecting specific workspaces. | |
Set up automatic backup coverage for new and existing workspaces. | |
View, manage, and delete backup snapshots for Power BI workspaces. | |
How to restore backed-up reports, datasets, and dataflows to Power BI. |
Step 3b — Protect Power Apps
Configure backups for Power Apps environments after Power Platform is connected.
Article | What It Covers |
Environment listing, discovery, search, and filters. | |
Manual vs auto-configuration for environments. | |
Select individual environments and assign a profile. | |
Apply one rule to current and future environments. | |
Environment details, on-demand backup, disable, and delete. | |
Download canvas apps from a snapshot. |
Step 4 — Manage Backup Profiles and Auto-configuration Rule
Backup profiles let you define retention, frequency, and scope of protection — and apply them at scale.
Backup Profiles
Article | What It Covers |
What backup profiles are and how they govern protection settings. | |
How the system default profile works and when it applies. | |
Step-by-step guide to creating a custom backup profile. | |
How to edit an existing profile's settings and retention rules. | |
How to delete a profile and what happens to workspaces assigned to it. | |
Configure how long Druva retains backup snapshots per profile. |
Auto-Configuration Rules
Article | What It Covers |
How auto-configuration rules work and when to use them over manual setup. | |
Create rules to automatically protect workspaces that match defined criteria. | |
Manually trigger a sync to apply rule changes to current workspaces. | |
Update the criteria or assigned profile of an existing rule. | |
Remove a rule and understand the impact on currently protected workspaces. |
Step 5 — Monitor, Audit, and Troubleshoot
Keep your backup environment healthy with ongoing monitoring and proactive alerts.
Article | What It Covers |
Track the status of backup and restore jobs across all Power Platform workloads. | |
Set up alerts for backup failures, missed jobs | |
Review admin activity logs for compliance, governance, and forensic needs. | |
Diagnose and resolve common issues during setup, backup, and restore. | |
Known gaps, platform constraints, and workarounds to be aware of. |