Our company was just approved for the preview of azure site recovery for VMware. However we have been using azure for about a year now and have 30 machines currently running. We also have two networks configured within azure as well.

I am following this document to try to get things up and running.

http://azure.microsoft.com/en-us/documentation/articles/site-recovery-vmware-to-azure/

Currently I am on step 2, deploying the configuration server however when I try to deploy the server it does not work. I can enter the name of the server, username and password however when it asks me to pick an azure network the drop down list is blank. Its like the setup doesnt see our existing two networks. I have made sure that the recovery vault is in the same region as our existing virtual machines and networks.

It seems like this is something that should be very simple but I must be missing something?

Hi,

Can you please log off/log in back to the Azure portal and re-try the operation?

Let us know how it goes.

Thanks

Shashank

Just tried logging out and back in with no luck. Does it matter that I am using the old page manage.windowsazure.com and not the new site?

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator 10 hours 13 minutes ago

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator 10 hours 17 minutes ago

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM
• Marked as answer by Shashank PMicrosoft employee, Moderator 17 hours 45 minutes ago

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM
• Marked as answer by Shashank PMicrosoft employee, Moderator Monday, May 25, 2015 1:28 PM

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM
• Marked as answer by Shashank PMicrosoft employee, Moderator Monday, May 25, 2015 1:28 PM
• Unmarked as answer by xxdcmast 14 hours 42 minutes ago
• Unproposed as answer by xxdcmast 14 hours 42 minutes ago

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM
• Marked as answer by Shashank PMicrosoft employee, Moderator Monday, May 25, 2015 1:28 PM
• Unmarked as answer by xxdcmast 14 hours 47 minutes ago
• Unproposed as answer by xxdcmast 14 hours 47 minutes ago

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM
• Marked as answer by Shashank PMicrosoft employee, Moderator Monday, May 25, 2015 1:28 PM
• Unmarked as answer by xxdcmast Wednesday, May 27, 2015 4:31 PM
• Unproposed as answer by xxdcmast Wednesday, May 27, 2015 4:31 PM

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM
• Marked as answer by Shashank PMicrosoft employee, Moderator Monday, May 25, 2015 1:28 PM
• Unmarked as answer by xxdcmast Wednesday, May 27, 2015 4:31 PM
• Unproposed as answer by xxdcmast Wednesday, May 27, 2015 4:31 PM

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM
• Marked as answer by Shashank PMicrosoft employee, Moderator Monday, May 25, 2015 1:28 PM
• Unmarked as answer by xxdcmast Wednesday, May 27, 2015 4:31 PM
• Unproposed as answer by xxdcmast Wednesday, May 27, 2015 4:31 PM

This could be transient error. Can you please try creating a new Vnet in the same region and see if that works. If it doesn't then we can look into your setup.

Thanks

Shashank

• Proposed as answer by Shashank PMicrosoft employee, Moderator Thursday, May 21, 2015 9:02 PM
• Marked as answer by Shashank PMicrosoft employee, Moderator Monday, May 25, 2015 1:28 PM
• Unmarked as answer by xxdcmast Wednesday, May 27, 2015 4:31 PM
• Unproposed as answer by xxdcmast Wednesday, May 27, 2015 4:31 PM

Shashank the answer you provided is not correct. So I am updating this with information I received from my MS rep.

Since Azure site recovery for VMware is currently in preview it is only available out of the US WEST locations. Since we are on the east coast and all of our networks, VPN connections, vms, cloud services, and recovery vault are located in US EAST this is not available to us.

In testing I created a recovery vault and test network in US WEST they were immediately available. If you have resources anywhere besides US WEST you will have this same experience.

Shashank the answer you provided is not correct. So I am updating this with information I received from my MS rep.

Since Azure site recovery for VMware is currently in preview it is only available out of the US WEST locations. Since we are on the east coast and all of our networks, VPN connections, vms, cloud services, and recovery vault are located in US EAST this is not available to us.

In testing I created a recovery vault and test network in US WEST they were immediately available. If you have resources anywhere besides US WEST you will have this same experience.

• Marked as answer by Shashank PMicrosoft employee, Moderator 20 hours 38 minutes ago

Shashank the answer you provided is not correct. So I am updating this with information I received from my MS rep.

Since Azure site recovery for VMware is currently in preview it is only available out of the US WEST locations. Since we are on the east coast and all of our networks, VPN connections, vms, cloud services, and recovery vault are located in US EAST this is not available to us.

In testing I created a recovery vault and test network in US WEST they were immediately available. If you have resources anywhere besides US WEST you will have this same experience.

• Marked as answer by Shashank PMicrosoft employee, Moderator 20 hours 43 minutes ago

Shashank the answer you provided is not correct. So I am updating this with information I received from my MS rep.

Since Azure site recovery for VMware is currently in preview it is only available out of the US WEST locations. Since we are on the east coast and all of our networks, VPN connections, vms, cloud services, and recovery vault are located in US EAST this is not available to us.

In testing I created a recovery vault and test network in US WEST they were immediately available. If you have resources anywhere besides US WEST you will have this same experience.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, May 28, 2015 10:35 AM

Shashank the answer you provided is not correct. So I am updating this with information I received from my MS rep.

Since Azure site recovery for VMware is currently in preview it is only available out of the US WEST locations. Since we are on the east coast and all of our networks, VPN connections, vms, cloud services, and recovery vault are located in US EAST this is not available to us.

In testing I created a recovery vault and test network in US WEST they were immediately available. If you have resources anywhere besides US WEST you will have this same experience.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, May 28, 2015 10:35 AM

Shashank the answer you provided is not correct. So I am updating this with information I received from my MS rep.

Since Azure site recovery for VMware is currently in preview it is only available out of the US WEST locations. Since we are on the east coast and all of our networks, VPN connections, vms, cloud services, and recovery vault are located in US EAST this is not available to us.

In testing I created a recovery vault and test network in US WEST they were immediately available. If you have resources anywhere besides US WEST you will have this same experience.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, May 28, 2015 10:35 AM

Shashank the answer you provided is not correct. So I am updating this with information I received from my MS rep.

Since Azure site recovery for VMware is currently in preview it is only available out of the US WEST locations. Since we are on the east coast and all of our networks, VPN connections, vms, cloud services, and recovery vault are located in US EAST this is not available to us.

In testing I created a recovery vault and test network in US WEST they were immediately available. If you have resources anywhere besides US WEST you will have this same experience.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, May 28, 2015 10:35 AM