Failback From Azure to On-Premises Hyper-V Site.

Failover direction is from Azure to on-premises is considered a failback.
You fail back Hyper-V VMs from Azure by running a planned failover from Azure to the on-premises site,
failback turns off the VMs in Azure, and downloads the latest changes,
and since Azure is a highly available environment and VMs are always available, failback from Azure is a planned activity.
After Failback finishes you expect the VMs on-Premises Site to start up by themselves.
No data loss is expected.
Failback to On-Premises Hyper-V Site:
1. Replicated items choose the VM then choose Planned Failover.
2. Confirm.
3. Choose ( Minimize Downtime or Full Download)
Minimize Downtime : This option minimizes downtime for VMs as it synchronizes without shutting them down.
Full Download :You need to use this option if you've been running Azure for a while (a month or more) or if the on-premises VM is deleted, since It performs a download of the disk.
4.Minimize Downtime needs a user input to complete the failback and shut down the VM on Azure and Turn on the VM On-Premises.
Reverse Replicate:
is the process to start replicating the on-premises VM to Azure again.

[@hiandhra9971]

Good one thank you

[@arunkumarkt8730]

can we migrate VMs on Azure to OnPrem (HyperV)? What are the tools we may use? Please advice

[@AL-Techs]

I guess there are tools to do that, maybe Zerto...but honestly I have not tried it, but one of my customers asked about.
but if you have the Azure site recovery set up still there you can failback to On-premises, another option is to download the vhd disk from export disk when the VM is stopped and create a new VM in hyper-v.

[@arunkumarkt8730]

@@AL-Techs thank you for quick response