After I clicked OK, Azure went about trying to discover my PRODSVR virtual machine on the AWS network. This took a few minutes but ultimately populated with my virtual machine:
At this point, I selected the machine and clicked OK. After clicking OK, I was prompted to configure the authentication account that I wanted to use to access the PRODSVR virtual machine:
I chose the authentication account I previously configured and clicked OK, after which I was prompted to configure replication settings:
When prompted for the replication settings, I ensured that the Replication Policy was set to my AWSMigrationPolicy (that I previously configured) and that multi-VM consistency was disabled since I’m not using it.
I then clicked OK to continue.
After clicking OK, all checkmarks turned green and the Enable Replication button became active:
I went ahead and clicked “Enable Replication” to launch the replication of my AWS virtual machine (PRODSVR) into Azure.
Once I had replication underway, I browsed over to my vault and clicked on “Replicated Items” so I could track the status of the replication of PRODSVR:
By clicking on the status, I was able to view details of that status:
Although it took maybe a half hour or so, the status eventually changed from “Enabling Protection” to “% Synchronized”, to “Protected”:
Migrated my EC2 Instance
Once the status reached “Protected”, I was able to perform a test failover to confirm that the process would work. To perform the test failover, I right-clicked my PRODSVR in the Replicated Items screen and selected “test Failover” from the context menu: