Azure Site Recovery Doesnt work

Hello DevOps BackendTeam

Thank you for posting your query on Microsoft Q&A platform.

We are looking into your issue and will keep you posted updates.

• Which type of Site Recovery replication are you using (Azure-to-Azure, Hyper-V, VMware)?
• What is the OS and version of the VM, and have you confirmed the Site Recovery extension (mobility service) is installed and running on it?

Thanks,

Suchitra.

Hello @DevOps BackendTeam@DevOps BackendTeam Thanks for sharing the screenshots. Based on what’s visible, this is a known Azure Site Recovery (ASR) failure pattern and not something you can fix purely from the VM blade.

You are hitting two different ASR errors, but they stem from the same root problem:

Error ID 539 “The requested action couldn't be performed by the Replication Provider.”

This is a generic ASR orchestration failure. It means:

• The ASR backend provider failed while creating the protection intent
• Azure portal cannot surface the real underlying exception to the user

Error ID 28157 “Protection intent deployment failed for VM …”

This confirms that:

• The Protection Intent ARM deployment failed
• ASR never reached the stage of agent-based replication

This is not a guest OS / agent issue, and not something retrying will fix.

This specific combination (539 + 28157) commonly occurs when one of the following is true:

• Stale / partially created ASR protection intent
• Corrupted replication provider metadata in the vault
• Previous failed enable‑replication attempt that wasn’t cleaned up
• Vault‑level backend issue (cannot be resolved from portal UI)

Please try below workarounds as a resolution:

Step 1: Disable protection cleanly (if visible)

From Recovery Services Vault:

1. Go to Replicated items
2. Select the VM
3. Click Disable replication
4. Choose Stop replication (do NOT delete data)

If the VM is not visible under replicated items, skip this step.

Step 2: Remove the stale protection intent

In the Recovery Services Vault:

1. Go to Disaster recovery → Site Recovery infrastructure
2. Check:
   • Fabric
     • Protection containers
       • Replication policies

Ensure no orphaned entries reference the VM.

This step matters because protection intent is an ARM resource, not just a VM setting.

Step 3: Re‑enable protection from the VAULT (not the VM)

This is critical and do NOT enable replication from:

• VM → Disaster Recovery blade

Instead:

1. Open Recovery Services Vault
2. Go to Replicated items
3. Click + Enable replication
4. Select:
   • Source region
     • Target region
       • Policy
         • VM

This forces a fresh protection intent deployment.

If it still fails at this point please do let us know then we will let you know further investigation updates.

Thanks,
Suchitra.

Hello @DevOps BackendTeam@DevOps BackendTeam

Kindly let us know if the solution provided worked for you.

If you found the comment helpful, please consider clicking "Upvote it".

If the resolution did not help, feel free to share more details about the challenge you’re still facing. Any additional information such as your current issue or specific errors will help us perform a deeper analysis and provide more targeted guidance.

We’re happy to continue assisting and work with you toward the right solution.

Thanks,

Suchitra.