![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 34%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETD%3C/text%3E%3C/svg%3E)
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 97%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hello tech dev,
Thank you for posting your query on Microsoft Q&A platform.
When you cannot see the datastore in the Azure portal during VM reprotection after a failover, it means the Master Target is not recognized as a virtual machine under the vCenters registered with Azure Site Recovery.
Manually add the Master Target to the vCenter that manages your source machine. Once added, the datastore will appear after the next vCenter discovery and fabric refresh.
The discovery and refresh fabric operations can take up to 30 minutes to complete.
For more information about reprotecting a virtual machine, see Reprotect and fail back machines to an on-premises site after failover to Azure.
If you have any other questions or need further support, please feel free to contact us.
Thanks,
Suchitra.