When using a Failover recovery, the Cloud DR Server does not control the on-premises environment, and there is a possibility that the production virtual machine can still be accessed by users, even when there is a Failover VM that should be accessed instead of the on-premises’ one. In this case, the access to the production on-premises virtual machine should be manually disabled in order to prevent accidental access to it and redirect the users to access the recovered VM.
If users continue their access to the on-premises virtual machine when the recovered VM is running on the cloud as a Failover, and make changes, these changes might be lost when you decide to failback: you would not be able to save the changes made to both the Failover VM and the on-premises VM.
It is recommended to use DNS servers to redirect users to the active production virtual machine or recovered VM. After a Failover, make sure to update the DNS entry of your production virtual machine with the IP address of the recovered VM so the DNS servers will automatically redirect users to the recovered instance instead of the on-premises virtual machine.