Virtual machines '%VMNames;' were not found in Azure or could not be reached for the failover operation. This can happen if the commit has failed or the VM was deleted from Azure.
Verify the virtual machine state, check that the VMM/Hyper-V server is available, and retry the planned failover. Or perform ...
Virtual machine '%VmRoleName;' couldn't be started under deployment '%DeployementName;' and cloud service '%HostedServiceName;'. ...
Virtual machine deployment '%DeploymentName;' couldn't be deleted because another operation is running on the virtual machine ...
Virtual machine information couldn't be retrieved from the configuration server. Check the Provider errors for more information. ...
Virtual machines '%VMNames;' were not found in Azure or could not be reached for the failover operation. This can happen ...
Virtual machines protected to Azure will be encrypted. Encrypted data is decrypted during failover from the Windows Hyper-V ...
Virtual machines protected to Azure will be encrypted. Encrypted data is decrypted during failover from the Windows Hyper-V ...
VM has stale protection settings. You'll need to manually clear protection settings before you can enable protection again. ...
VMM cannot migrate or clone the virtual machine (%VMName;) because the version (%TargetHostVSVersion;) of the virtualization ...