AI agents have moved from pilot to production. According to Microsoft, more than 80% of Fortune 500 companies now use active AI agents built with low-code or no-code tools. These agents answer employee questions, route approvals, and surface insights from business systems. When one is deleted or misconfigured, the process it runs stops with it.
Today, Druva is extending AI Resilience to the agents themselves. We're introducing Druva Agent Recovery, starting with Copilot Studio Agents, now in Limited Availability. Organizations can restore an individual Copilot Studio agent from an available recovery point, without rolling back the entire environment it lives in.
This launch also extends protection to the Power Apps and Power Automate flows agents depend on, and brings Druva intelligence into the Microsoft AI tools your teams already use. Here's what's new:
- Copilot Studio Agent backup and recovery (Limited Availability): Restore an individual agent from a recovery point, independent of its environment
- Power Apps protection (General Availability): Back up and restore the apps agents and teams rely on
- Power Automate protection (Limited Availability): Back up and restore the flows agents call
- Druva Integration with Azure SRE Agent (General Availability): Druva protection and recovery context inside Azure investigations
- Druva Agent for Microsoft 365 Copilot (General Availability): Guided protection troubleshooting in Microsoft 365 Copilot and Teams
Why it matters: Agents reach production faster than teams can recover them
A Copilot Studio agent isn't a single object. It brings together instructions, knowledge sources, topics, tools, and connections. When an administrator accidentally deletes it, a maker changes its instructions, or a compromised account alters its behavior, recovering means recreating each of those pieces, reconnecting applications, and retesting before it returns to production.
That can take hours or days, and business processes have to wait. Picture an agent that gives sales leaders pipeline insights from Salesforce opportunity data. The underlying data is fine, but the agent stops working, and leaders lose visibility until someone rebuilds it.
Microsoft provides established tools for managing Power Platform environments and agents, and each serves an important purpose. They just solve different problems than recovering one agent:
- Environment backup and restore overwrites the selected target environment rather than recovering a single agent. Backups are configured per environment, with limited retention.
- Solution export and import support moving agents between environments and managing change. It can be automated, but it only covers agents and dependencies that have been added to a solution, which is hard to standardize when makers create new agents every day.
- Microsoft Agent 365 is an enterprise control plane to discover, observe, govern, and secure agents. It isn't designed for backup and recovery.
As agent adoption grows, organizations need the same thing for agents that they already expect for email, files, and SaaS data: an independent, policy-driven way back.
Copilot Studio Agent backup and recovery: A fast way back when an agent fails
Copilot Studio Agent backup and recovery is the first capability in Druva Agent Recovery, part of Druva AI Resilience. It gives organizations scheduled, policy-based backups of customer-built Copilot Studio agents and the ability to recover an individual agent to a known recovery point. Backups are stored independently in the Druva Resilience Cloud, outside the source Power Platform environment.
1) Discover agents, automatically
Makers create new agents every day, and admins can't protect what they can't see. Druva discovers supported Copilot Studio agents across your registered Power Platform environments and shows details such as agent name, environment, owner, and last modified date, alongside each agent's backup status.
2) Protect agents with policy, not manual exports
Instead of depending on every maker to add every agent to a solution and export it, administrators apply backup policies that protect agents on a schedule, with customizable retention. Protection scales as agent adoption grows.
3) Recover one agent, not the whole environment
When an agent is deleted, misconfigured during an update, or altered by an unauthorized change, administrators select an available recovery point and restore the affected agent, including one that has been deleted. The apps, flows, and other agents in the environment keep running. Because recovery points are stored outside the Microsoft environment, teams can restore an agent after a compromised account or unauthorized change.
Druva restores the agent's supported configuration, including its instructions, topics, knowledge configuration, and tool references. Connections need to be reauthenticated, and publishing may require additional steps before the agent is fully back in service. This release covers customer-built agents. It doesn’t include marketplace agents.
4) Protect what agents depend on
An agent is only as useful as the data and applications it works with. Druva already protects many of them, including Microsoft 365, Microsoft 365 Copilot Chat, Microsoft Entra ID, Dynamics 365, and Salesforce. Each workload has its own independent recovery points, so teams can recover only what’s affected: the agent, the underlying data or applications, or both.
Power Apps and Power Automate: Protect the apps and flows agents rely on
Copilot Studio agents rarely work alone. They call Power Automate flows to take action and sit alongside the Power Apps that teams use every day. And Power Platform keeps growing: it has 56 million monthly active users, up 27% year over year.
Yet many organizations still protect these assets with manual exports and ad hoc solution downloads. Those approaches are hard to scale, miss dependencies, and leave teams rebuilding apps and flow logic by hand after an incident.
With this launch, Druva for Microsoft Power Platform extends beyond Power BI to protect Power Apps (General Availability) and Power Automate flows (Limited Availability), alongside Copilot Studio agents.
What you get
- Automated discovery: Druva automatically detects Power Apps applications and Power Automate flows across your tenant.
- Policy-driven backups: Scheduled, point-in-time backups with customizable retention that extends beyond native limits.
- Granular recovery: Restore a specific app or an individual flow without rebuilding entire solution packages from scratch.
- Air-gapped, immutable storage: Backups are isolated from the primary Microsoft tenant, helping protect against ransomware, bad deployments, and insider threats.
The result is one place to protect the low-code assets the business runs on: the reports, the apps, the flows, and now the agents.
Druva Integration with Azure SRE Agent: Recovery-aware Azure operations
Microsoft Azure SRE Agent helps DevOps and CloudOps teams investigate incidents, diagnose problems, and keep their environments running. But knowing what went wrong is only part of the job.
Imagine an Azure workload starts failing after an infrastructure change. Azure SRE Agent can help identify what changed and recommend a fix. Before acting, though, the team still needs answers to a few questions. Is the workload protected? Did its latest backup succeed? What recovery points are available? Today, that usually means switching to a separate data protection console in the middle of an incident.
Now generally available, the Druva Integration with Azure SRE Agent brings those answers into the investigation. Customers add Druva MCP as a custom MCP server in Azure SRE Agent, which can then use Druva backup health, protection status, failed-job diagnostics, and recovery points as context in any investigation. It extends Azure SRE Agent rather than introducing another standalone agent, so teams don't have to change how they work.
What teams can do
- Check protection status as part of an Azure operational investigation.
- Investigate backup failures with relevant Druva diagnostics to determine next steps.
- Find protection gaps by correlating Azure resources with Druva-protected workloads.
- Assess recovery options by retrieving available recovery points before making changes or during an incident.
- Act on findings, with Azure SRE Agent suggesting and taking next steps based on Druva context.
Azure SRE Agent helps teams understand what's happening and how to respond. Druva adds the protection and recovery context to make those decisions with confidence.
Druva Agent for Microsoft 365 Copilot: Turn backup intelligence into guided investigation and action
Backup administrators face a constant stream of alerts, reports, and metrics across workloads. Finding the root cause of a failure often means navigating several dashboards, correlating individual alerts, and digging through documentation before anyone has worked out the business impact.
The Druva Agent for Microsoft 365 Copilot brings Druva backup intelligence directly into Microsoft 365 Copilot and Microsoft Teams. Built on Copilot's declarative agent framework and installed from the Agent Store, it combines Druva-specific instructions, curated Druva product and troubleshooting knowledge, and integrated actions through Druva APIs.
What the agent does
- Prioritize by business impact: Copilot correlates Druva backup intelligence with Microsoft 365 signals, such as affected users and groups, so administrators know which issues to tackle first.
- Simplify investigation: Get a consolidated view of backup health, see resources at risk, and group related failures to uncover common causes instead of chasing individual alerts.
- Resolve faster: Receive recommended fixes grounded in Druva documentation, and run supported, non-destructive actions, such as retrying failed backups, without leaving Copilot.
- Collaborate in Teams: Share protection insights and coordinate troubleshooting in Teams conversations, and turn findings into summaries, draft tickets, and follow-ups.
Alerts tell administrators what failed. The Druva Agent helps them understand why, who it affects, and what to do next, without leaving Copilot or Teams.
Final thoughts: AI Resilience, now for your agents
AI agents are now embedded in core business operations, which makes resilience essential to keeping the business running when something goes wrong. Druva Agent Recovery aims to help organizations recover an agent's configuration, its activity, and the data it depends on. Copilot Studio Agent Backup and Recovery is the first step toward that vision.
Druva already protects your Microsoft 365 data, Microsoft 365 Copilot Chat conversations, and the work AI creates. Now it protects the agents putting that data to work, along with the apps and flows they rely on, all through the fully managed Druva Resilience Cloud.
Ready to learn more?
- Read the Copilot Studio Agent datasheet
- Explore Druva for Microsoft Power Platform
- See Druva's protection for Microsoft and Azure
- Visit Druva at Microsoft Ignite, Booth #5328 — Book a meeting time here!