What Druva announced
The announcement also adds Power Apps and Power Automate to Druva's existing Power BI support. It brings three things for Microsoft admins:
- Agent Recovery for Copilot Studio agents.
- Power Apps and Power Automate backup.
- Two integrations that put Druva backup data inside Microsoft AI tools: Azure SRE Agent and Microsoft 365 Copilot.
The pitch is recovery granularity. Druva says it keeps a recovery point ready for each protected agent, so teams can recover individual agents without starting over. The alternative, in Druva's framing, is restoring a whole environment or rebuilding an agent by hand.
Copilot Studio agent backup
Druva says the feature does three things:
- Discovery: It automatically discovers Copilot Studio agents across Power Platform environments as employees build them.
- Protection: It runs scheduled, policy-based backups that Druva describes as immutable. They are stored in Druva's Resilience Cloud and give each agent a version history.
- Recovery: It restores a single agent and its configuration without rolling back the whole Power Platform environment.
Druva's release leaves out several details admins would want before relying on this:
- Backup frequency.
- Retention periods.
- Recovery-time targets.
- Exactly which agent components are captured.
- Pricing.
- How discovery handles permissions.
"Immutable" describes the backup copies. It does not mean every dependency of a restored agent comes back with it. Druva itself notes that Copilot Studio agents depend on connected applications, flows, data, and identities. Test a restore and check the connectors, credentials and data sources before you call it done.
Power Apps and Power Automate
Druva says teams can restore individual apps or flows from air-gapped, immutable backups, without rebuilding them or rolling back the environment.
Druva's product documentation gives some scope for Power Apps. It lists support for Power BI workspaces (reports, datasets and dataflows) and for Power Apps environments, canvas apps and component library details. Prerequisites include registering an Admin Management Application with Microsoft Power Platform. That documentation was indexed about 48 days before this writing. It says Power Automate support would come in future releases, so check it against the new announcement.
Druva's earlier roadmap points the same way. In April it said Power Apps and Power Automate support would arrive later this year. The November announcement delivers that, but only partly.
Integrations inside Microsoft tools
Azure SRE Agent. Druva says the SRE Agent can read Druva backup health, protection status, recovery points and failed-job diagnostics. It then correlates them with Azure operational data to flag unprotected workloads and suggest or take next steps.
Microsoft describes Azure SRE Agent as an AI-powered operations teammate that automates triage and runs governed mitigations. Its documentation also covers connectors and role management. The release doesn't say which actions the integration can take on its own, or what approvals and permissions apply. Check those before enabling it.
Druva Agent for Microsoft 365 Copilot. It is delivered through the Agent Store and works in Copilot and Teams. Druva says it offers:
- A consolidated backup-health view.
- Grouped failure analysis.
- Remediation guidance.
- Visibility into which users and groups are affected.
- The ability to retry failed backups from Copilot.
The release doesn't cover licensing prerequisites, required admin roles or audit trails. Letting an AI agent retry backup jobs is convenient, but you should know who can invoke it and what gets logged.
Availability
| Capability | Status per Druva |
|---|---|
| Power Apps protection | Generally available |
| Druva Agent for Microsoft 365 Copilot | Generally available |
| Azure SRE Agent integration | End of November 2026 |
| Copilot Studio Agent Backup & Recovery | Limited availability |
| Power Automate protection | Limited availability |
The headline feature, Copilot Studio agent recovery, is not generally available yet. Druva's release gives no eligibility criteria or date for wider release. Druva's own documentation for Copilot Chat protection, dated August 2026, shows the pattern. It says limited-availability features may be enabled on request, can change, or may become separately priced.
Claims to treat carefully
- "First" claims. Druva calls both Microsoft integrations the first of their kind. I found no independent confirmation of either.
- The 80% statistic. The release attributes a figure to Microsoft that more than 80% of Fortune 500 companies use low-code or no-code AI agents. It gives no source.
- "End to end." The release says Druva protects Copilot Studio agents and their workflows end to end. With Power Automate still in limited availability, that overstates today's coverage.
This also isn't the first Druva move into Copilot. In July it launched AI Resilience with new Copilot support. The November announcement extends that line from chat data to the agents themselves.
What admins should do
- Inventory Copilot Studio agents and the Power Apps and flows they rely on, and note owners.
- If you already use Druva, ask your account team about limited-availability enrollment and its terms.
- Run a restore test on a non-critical agent and check connections, permissions and data after recovery.
- Before enabling either Microsoft AI integration, ask about permissions, approval controls and logging.
- Revisit these details after Microsoft Ignite on November 17–20, where Druva says it will demo at booth 5328.
This announcement is useful mainly because it shows Power Platform agents becoming something to back up. Vendors will claim they can restore them. Until the limited-availability features reach general availability, the proof is a restore test in your own tenant.