TechnologyNov 18, 202613 min read

Rubrik for Power Platform: Restore the App, Not the Environment


Image a manufacturer that builds a supply chain app on Power Apps. It pulls from SharePoint and three cloud flows, and planners use it to schedule shipments across global factories. One day, an admin pushes an update by mistake. The app breaks, and the data behind it is corrupted.

Nobody holds a separate copy of just that app. Native recovery either rolls back the entire environment, overwriting everyone else’s work since the last backup, or relies on manual scripts to retrieve a single app or flow. Those scripts are error-prone and need specialist expertise. In the meantime while the app is down, planners cannot schedule, shipments slip and finance cannot close orders.

The data was backed up. The business process was not.

Power Platform has grown to 56 million monthly active users, according to Microsoft. Every Microsoft 365 E3 and E5 user can already build on it. An expense app becomes an approval flow, and the approval flow becomes a dispatch portal. Before long, finance, HR, and supply chain depend on apps that anyone could build and nobody separately protected.

When one Power Platform app breaks, the business process it runs stops with it. Rubrik for Power Platform, now generally available, backs up apps, flows, and Dataverse data together and restores only the component that failed, with its dependencies and records, in place or to another environment.

 

Where Native Recovery Breaks

Microsoft backs up Power Platform at the environment level, and that is also the only level it restores. Recovering one broken app means overwriting everyone’s recent work, detouring through a sandbox, and rebuilding connections afterward, while standalone apps and flows fall outside the backup altogether. 

The limits below show where recovery stalls when a single app, flow, or table goes wrong.

  • Seven days of retention: Minimum is set by default. Maximum available retention is 28 days, managed production only.

  • Whole-environment overwrite: If one app breaks, everyone's recent work gets rolled back.

  • No direct restore to production: You have to switch to sandbox, restore, then switch back.

  • Standalone apps and flows are skipped: Only solution-aware assets are covered.

  • Afterward: Canvas app IDs change, flows turn off, and connections need rebuilding.

  • Long Recovery Window: A full restore can take up to 48 hours in large environments.

As agents change more production data, the ability to restore one app or one table becomes the difference between a fix and a rollback.

 

What Rubrik Covers

Rubrik for Power Platform protects every layer of a business application: the apps people build, the flows that automate them, the Dataverse data underneath, and the dependencies that tie them together. That coverage lets a restore return a working application, whether its assets sit inside a solution or stand alone, and includes:

  • Power Apps: Canvas and model-driven

  • Power Automate: Cloud flows, classic workflows, business process flows

  • Dataverse: Linked tables and relationships, up to 10 levels deep

  • Dependencies: Solutions, connection references, environment variables, permissions

Standalone apps and flows, which native recovery skips, are covered like everything else.

 

How it Works

Rubrik for Power Platform includes three pieces. Rubrik Security Cloud (RSC) acts as the control plane. A Rubrik-managed Azure tenant is the data plane. Your Power Platform environment is the source and the target.

 

Architecture


Connect once: OAuth 2.0. RSC gets a token and calls the Power Platform APIs. Credentials are never stored.

Back up

The image below describes the back up workflow:

1.  Set the policy: One SLA on the environment: every 12 hours, daily, or custom. Every app, flow, and solution inside inherits it. No per-app assignment.

2.  Discover: RSC maps Tenant, Environment, Solution, Component. Every canvas app, cloud flow, and Dataverse-backed component shows up, standalone ones included.

3.  Bundle: Rubrik creates a lightweight solution package inside your environment to group components for backup and restore. It's expected behavior, and we flag it during onboarding.

4.  Write to two stores. Step 4A shows app and flow ZIP packages and file data go to Blob Storage. Setp 4B shows how Dataverse records and metadata go to PostgreSQL, the same approach Rubrik uses for Dynamics 365. That is what makes row-level recovery possible.

5.  Stay current: Rubrik-generated metadata goes to RSC for search and browse. It refreshes between scheduled backups, so apps you add, change, or remove show up without waiting for the next job.

 

Restore

Restore

The image below describes the restore workflow:

1.  Choose what and when: Pick individual canvas apps, cloud flows, or model-driven apps, plus a restore point, in RSC. Restore is always component-level, never environment-level. Up to 100 items per operation.

2.  Choose where: The original environment, any other environment you can access (sandbox, test, another production), or a brand-new environment created in the same workflow.

3.  Choose how much: For model-driven and other Dataverse-backed apps, restore the app plus its Dataverse tables (the default) or the app definition only.

4.  Resolve dependencies: Rubrik discovers connection references, environment variables, and managed dependencies for each app and flow. Step 4A shows how In place, they're already configured and resolve automatically. Step 4B shows how cross-environment, anything Rubrik can't resolve is shown in the restore UI with full detail. Fix it in the Power Platform admin center, hit Refresh in RSC, and Restore activates once everything is clear.

5.  Read from both stores: Apps, flows, and files come from Blob Storage. Dataverse records come from PostgreSQL. A restore that spans both reads from both, then writes to the target.

6.  Restore in order: Rubrik picks the closest snapshot per Dataverse table (within 7 days, falling back to 60) and restores parent tables before child tables so foreign keys hold. Apps come back disabled until you verify and enable them. Nothing runs by accident.

In-place restores keep App IDs and sharing intact.

 

Backup


Locked down: 
Backups are logically air-gapped, outside the Microsoft control plane. Ingested records are hashed, UPDATE and DELETE are revoked, and Retention Lock means no retention cap. Keep them 7+ years. RBAC lets Power Platform admins run their own recoveries while backup admins keep the compliance view.

Same Incident, Two Outcomes

Imagine that a bad script breaks an app and nulls thousands of Dataverse records. Production is down.

What teams do today: Nobody rolls back production—that would wipe out everyone else's work. So the team restores the backup into a sandbox environment, then writes manual scripts to pull the broken app, its flows, and the damaged records back into production. After that, someone recreates connections, re-enables flows, and resets sharing.

That is slow, error-prone work, and it needs a specialist who knows the app, the data model, and the scripting. Every hour of it adds to your RTO. Large environments can take up to 48 hours.

With Rubrik: Search for the app, pick a clean snapshot, restore in place. The app, its dependencies, and its Dataverse data come back together. No sandbox detour, no custom scripts, no specialist on call.

Production stays live and everyone else's work stays put.

 

Part of the Microsoft Estate (Including AI)

Copilot and agents now edit production apps and data faster than anyone can review. Every AI rollout is a bet that a bad change can be undone. Restore only what broke, and the bet gets safer.

Rubrik already protects Exchange, OneDrive, SharePoint, and Teams. Power Apps tie them together. Now it's one console, one recovery, in business order.

Power Apps and flows sign in through Entra ID. Rubrik Identity Resilience (licensed separately) recovers Entra ID and Active Directory first, with clean room recovery and attacker persistence removal.

 

Get started

Related Articles

Blog by This Author