SalesBuy
1-855-856-7678
Technical SupportSupport
Enable Windows Azure Connect for a VM Role
Updated: March 8, 2011
[The VM Role feature of Windows Azure is being retired on May 15th, 2013. After the retirement date, VM role deployments will be deleted. To move forward with your existing applications, you can use Windows Azure Virtual Machines. For more information about using Virtual Machines for your application, see Moving from VM Role to Windows Azure Virtual Machines.
With Windows Azure Connect, you can configure IPsec protected connections between one or more computers or virtual machines (VMs) in your local network and VM Role instances running in Windows Azure. (IPsec protects communications over IP networks through the use of cryptographic security services.)
You must complete the following steps to enable a VM Role instance to use Windows Azure Connect:
-
Activate your Windows Azure roles for Windows Azure Connect by getting an activation token and ensuring that the token is included in the configuration for your roles. For more information, see How to Activate Windows Azure Roles for Windows Azure Connect.
-
Install the local endpoint software on computers or VMs in your local network. For more information, see How to Install Local Endpoints with Windows Azure Connect.
-
Install the endpoint software on the server image that you upload to Windows Azure, and define service configuration settings. The endpoint software is installed during the creation of the base VHD. For more information, see Create the Base VHD for a VM Role in Windows Azure.
When you get to the point in the creation process of the server image where you can install the endpoint software, complete the procedures listed in Enabling Windows Azure Connect for a VM Role. -
After the software has been installed and the role instances are running, you create one or more groups of endpoints. By configuring these groups, you specify connections between roles in Windows Azure and local endpoints. For more information, see How to Create and Configure a Group of Endpoints in Windows Azure Connect.
For a diagram that shows how roles connect to local endpoints in Windows Azure Connect, see Overview of Windows Azure Connect.
When creating the base VHD, you come to the point in the process where you can install applications and make configuration changes to the operating system. At this point in the process, you can install the endpoint software on the server image. Before you install the endpoint software, you must consider the following:
-
The virtual machine and operating system must be configured for Internet access to install the endpoint software on the server image.
-
You must ensure that IPv6 is enabled in the operating system of the server image you are including in the base VHD. IPv6 is enabled by default when you install the operating system.
-
All updates should be applied from Windows Update.
-
Open the browser.
-
Enter the following URL in the address bar and press Enter:
http://waconnect.blob.core.windows.net/client/latest/x64/wacendpointpackagefull.exe
Note This is not the same URL that is used to install the endpoint software on local computers. -
Complete the Windows Azure Connect Endpoint Installation Wizard.
When you are ready to use the VM Role, you must import the Connect module and enter the activation token into the service model to enable Windows Azure Connect for the VM Role instances. If you obtained an activation token, but did not record it, you can retrieve it from the Windows Azure Management Portal.
-
Log on to the Management Portal.
-
Click Virtual Network, and then select the subscription.
-
Click Get Activation Token, and then click Copy Token to Clipboard.
You must add configuration definitions and settings into the service model files to enable Windows Azure Connect for the VM Role instances. For more information, see Create and Deploy the VM Role Service Model.
