Unable to add hyper v sites and servers

Hello Adedayo Emmanuel Olatayo,

It looks like the issue is that the replication agent is installed and showing under Appliance, but the Hyper‑V server itself isn’t appearing under Servers in the Site Recovery Infrastructure. This happens because the Azure Site Recovery Provider hasn’t been fully installed and registered with the Recovery Services vault. The replication agent alone isn’t enough you also need to register the Hyper‑V host with a valid vault credentials file. Only then will the server show up under Servers and allow replication to be enabled.

1. Two components are required for Hyper‑V to Azure replication:

• Replication agent (MARS): Handles data transfer.
• Azure Site Recovery Provider: Registers the Hyper‑V host with the vault.

2. If only the agent is installed, the vault sees the appliance but not the host.

To resolve this, verify the following:

1. Check prerequisites: Make sure the Hyper‑V role is installed and running. Confirm the server OS is supported. Verify outbound internet access to Azure Site Recovery service URLs.
2. Install the Site Recovery Provider

• In the Azure portal, go to Recovery Services vault → Site Recovery → Prepare infrastructure.
• Download the Azure Site Recovery Provider for Hyper‑V.
• Run the installer on the Hyper‑V host.

3. Register the host with the vault: During installation, use a fresh Vault Credentials file (downloaded from the same vault and these expire after a few days). Complete the registration wizard.
4. Restart the Hyper‑V Virtual Machine Management Service (VMMS) and the Microsoft Azure Recovery Services Agent service.
5. Confirm in the portal:

• Go to Site Recovery Infrastructure > Hyper‑V Hosts.
• The server should now appear under Servers.
• Once visible, you can enable replication for your VMs.

If you've still facing an issue, could you please help us with the below questions:

1. What specific error messages are you seeing when you try to add the Hyper-V server?
2. Can you confirm if the Hyper-V server can communicate with the Azure site recovery endpoint?

Hope this helps!

Hi, There

As I knew, what’s really going on is

• Seeing an “appliance” with a replication agent usually means you set up Azure Migrate, not Azure Site Recovery (ASR).
• For Hyper-V > Azure replication, you need the ASR Provider on each Hyper-V host and the host must be registered to your Recovery Services vault.

I suggest you to try theses fix in a few steps (for ASR)

• On each Hyper-V host, remove Migrate/MARS agents (they’re for migrate/backup).
• Install: Microsoft Azure Site Recovery Provider (Unified Setup).
• During install, download fresh Vault Credentials from your vault and register the host.
• In the vault: Site Recovery > Infrastructure > Hyper-V (no VMM)
  • Create/use a Hyper-V site, Add server > host should show Healthy.
  • Then Replicate and choose VMs.

If you meant Azure Migrate

• Stay in Azure Migrate and enable replication there.
• You can’t add that “appliance” entry under Site Recovery.

Then try these gotchas to check

• Wrong agent installed > use ASR Provider.
• Vault creds expired > re-register with new credentials.
• 443 outbound open; proxy set in Provider if needed.
• TLS 1.2 enabled on the host.
• RBAC: you have rights on the vault/target RG/storage/network.
• Clusters: Provider on every node; Replica Broker online.
• Time sync/AV not blocking the provider.