General availability: Simplified disaster recovery for VMware machines using Azure Site Recovery
Today we’re officially announcing the general availability of a simpler, more reliable, and modernized way to protect your VMware virtual machines using Azure Site Recovery, for recovering quickly from disasters. We are now offering these enhancements:
Stateless ASR replication appliance
The configuration server and its on-premises components have been converted into a stateless ASR replication appliance. This simplifies discovery and failback process by introducing the option to select any appliance without needing to set up any master target server or process server.
Automatic upgrades for ASR replication appliance and mobility agent
A big deal breaker with the classic architecture was manually updating various configuration server components and mobility service. To simplify things we now support automatic upgrades – as soon as an update arrives, all the appliance components and mobility service will be updated automatically and that too, out of business hours.
Additionally, for automatic upgrades, the machine’s root/admin credentials will not be required anymore and will be required only for the initial installation.
Easier scale management
The appliance is now a single unit of management and all its components have been converted into micro-services which are hosted on Azure. This will not only make the troubleshooting much easier, but scale management will also become much smoother. To scale out an appliance, just set up another appliance and voila, it is done.
High availability for appliances
Appliance resiliency has also been a highly asked about topic and we have that covered too. With the modernized architecture, you don’t need to take regular backups of your appliance anymore – just spin up another appliance and switch all your machines to the new appliance. The replicated items will be switched to the new appliance, without going through complete replication again.
With this release, we will also support disaster recovery of physical machines along with private endpoints and managed identity support.
Learn more about the modernized architecture and move to the modernized experience now.
Published on:
Learn moreRelated posts
Give your Foundry Agent Custom Tools with MCP Servers on Azure Functions
Learn how to connect your MCP server hosted on Azure Functions to Microsoft Foundry agents. This post covers authentication options and setup ...
Scalable AI with Azure Cosmos DB: Tredence Intelligent Document Processing (IDP) | March 2026
Azure Cosmos DB enables scalable AI-driven document processing, addressing one of the biggest barriers to operational scale in today’s enterpr...
Announcing the end of support for Node.js 20.x in the Azure SDK for JavaScript
After July 9, 2026, the Azure SDK for JavaScript will no longer support Node.js 20.x. Upgrade to an Active Node.js Long Term Support (LTS) ver...
MCP Apps on Azure Functions: Quickstart with TypeScript
Learn how to build and deploy MCP (Model Context Protocol) apps on Azure Functions using TypeScript. This guide covers MCP tools, resources, l...
Setting up Power BI Version Control with Azure Dev Ops
In this blog post is a way set up version control for Power BI semantic models (and reports) using the PBIP (Power BI Project) format, Azure D...
Azure Developer CLI (azd) – March 2026: Run and Debug AI Agents Locally, GitHub Copilot Integration, & Container App Jobs
Run, invoke, and monitor AI agents locally or in Microsoft Foundry with the new azd AI agent extension commands. Plus GitHub Copilot-powered p...
Writing Azure service-related unit tests with Docker using Spring Cloud Azure
This post shows how to write Azure service-related unit tests with Docker using Spring Cloud Azure. The post Writing Azure service-related uni...
Azure SDK Release (March 2026)
Azure SDK releases every month. In this post, you find this month's highlights and release notes. The post Azure SDK Release (March 2026) appe...
Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed
The option to specify client ID and secret when creating Azure ACS principals will be removed. Users must adopt the system-generated client ID...