Cannot enable replication on Azure Site Recovery

Question

Cannot enable replication on Azure Site Recovery

SWiZ 35

Hi Everyone,

After the outage on West US 2, on 29 May 2026. I cannot enable replication for Physical Server in Azure Site Recovey. Is anyone facing the same issue?

azure-issue Error logs: An error has occurred. Please refresh the blade to try again.

Thank you.

Bharath Y P 9,720 Reputation points Microsoft External Staff Moderator

2026-06-01T01:52:30.9333333+00:00
Hello SWiZ, We understand that you are unable to enable replication for physical servers in Azure Site Recovery (ASR). While attempting to select machines, the portal shows "An error has occurred. Please refresh the blade…”

Additionally, the issue started after the West US 2 outage on May 29, 2026 and the machine list is not loading at all, preventing further progress.

After the outage in West US 2 affected multiple Azure services and control-plane operations. Azure Site Recovery depends on backend components like Recovery Services Vault , ASR Fabric / Discovery APIs and Configuration Server metadata sync. These components may become out of sync or partially inconsistent. This can lead to:

Failure to fetch machine list

Generic portal errors

Broken discovery state

Since the machine list is not loading, the failure is Looks like at the ASR backend discovery layer, not at:

Configuration server

Mobility agent

User permissions

To confirm, first rule out any UI issues by testing in an Incognito/InPrivate browser. If the issue persists, it indicates a backend problem.

Validate ASR infrastructure (sanity check): Ensure:

Configuration Server > Connected

Process Server > Healthy

Verify services on config server: Check these healthy or not
cxprocessserver obengine

Refresh ASR discovery: Go to: Recovery Services Vault > Site Recovery Infrastructure

Perform Refresh Configuration Server and Process Server

Retry: Enable Replication > Physical Machines

Check for partial/failed entries: Go to: Recovery Services Vault > Replicated Items

Remove any partially created entries and Retry replication

Isolate vault/region issue (important): Create a new Recovery Services Vault (same region) OR Try different region (if possible), this outcome:

Works > vault metadata issue

Fails > regional/backend issue

If the Machine list still not loading and All validations pass This confirms ASR fabric/discovery metadata inconsistency caused by the outage.

Hope this helps! If you have any question, please do let us know, thanks

Answer accepted by question author

Maxence RIOU 80

Exactly the same issue here in France Central Region, we cannot enable replication for physical servers in ASR.
Any news from Microsoft ?

Julien Rivoire 55 Reputation points

2026-06-08T21:55:15.4033333+00:00

@Maxence RIOU
There is an issue with the Enable Replication process for Physical Machines. The Microsoft support ASR Product Group is working on the fix and provided us with an alternate Azure Portal to be used in the time being.
Using the link below, you will be able to enable replication for those servers without getting the “An error has occurred” message:

https://aka.ms/asrportalfix

The Portal looks exactly the same, except for the address bar, where you will see “asrhotfix”

I'm working on replication right now and it seems to be working
Maxence RIOU 80 Reputation points

2026-06-09T09:04:35.12+00:00

Thanks a lot for your help!
It seems to work fine with your link (at least i can see the list of my servers ready for replication instead of an error).

(I was a bit worried by the link aka.ms..., i had to check it with a redirect link checker :D)
SWiZ 35 Reputation points

2026-06-09T13:01:15.58+00:00

Hi @Julien Rivoire

Thank you, it is working now.

2 additional answers

Your answer

Julien Rivoire 55 Reputation points

2026-06-08T21:55:15.4033333+00:00

@Maxence RIOU
There is an issue with the Enable Replication process for Physical Machines. The Microsoft support ASR Product Group is working on the fix and provided us with an alternate Azure Portal to be used in the time being.
Using the link below, you will be able to enable replication for those servers without getting the “An error has occurred” message:

https://aka.ms/asrportalfix

The Portal looks exactly the same, except for the address bar, where you will see “asrhotfix”

I'm working on replication right now and it seems to be working
Maxence RIOU 80 Reputation points

2026-06-09T09:04:35.12+00:00

Thanks a lot for your help!
It seems to work fine with your link (at least i can see the list of my servers ready for replication instead of an error).

(I was a bit worried by the link aka.ms..., i had to check it with a redirect link checker :D)
SWiZ 35 Reputation points

2026-06-09T13:01:15.58+00:00

Hi @Julien Rivoire

Thank you, it is working now.

Answer 1

Julien Rivoire 55

Hi @SWiZ

I have the same issue.
Did you find a solution?

Thank you

SWiZ 35 Reputation points

2026-06-03T23:43:07.9933333+00:00

Hello @Julien Rivoire

The issue is from Azure backend, and Microsoft still not fixed it.

Thank you.

Answer 2

It is not not a UI issue. ASR discovery API / fabric metadata got corrupted or stale after West US 2 outage. It usually indicates:

Backend service inconsistency after outage
Stale cache/session or partially broken ASR fabric discovery
Misconfigured / unhealthy Configuration Server / Process Server (for physical machines)

Refresh backend + session

Log out of Azure portal
Open Incognito/InPrivate browser
Try again
Switch region view (if possible)

Re-sync ASR infrastructure (critical)

Go to: Recovery Services Vault → Site Recovery Infrastructure

Select:
- Configuration Servers
- Click Refresh Server
- Restart services on config server
  Re-discover machines
This error often happens when machine discovery list is broken.
- Go to: Vault → Replicated Items / Site Recovery Infrastructure
- Trigger:
  - Refresh / Re-synchronize

Check Azure health (Post-outage side effects)

Outages leave services in degraded state.

Verify: Azure Service Health → Recovery Services / ASR (West US 2)

Validate permissions (less likely but quick check)

Ensure role:

Contributor or Site Recovery Contributor on Vault + RG

Share via

Cannot enable replication on Azure Site Recovery

2 additional answers

Refresh backend + session

Re-sync ASR infrastructure (critical)

Re-discover machines

Check Azure health (Post-outage side effects)

Validate permissions (less likely but quick check)

Your answer