Now let’s move to the main part of this series which is the configuring the Windows Azure Connect.
Requesting Beta Access to Azure Connect
At the time where this post was written, Windows Azure Connect is on beta status. Therefore, for those who have not possess the access, log-on to http://windows.azure.com, click on Beta Programs and click on appropriate service.
Having done so, you will probably need some time (may varies to days or weeks) in order to be activated).
Activating Azure Connect
Assuming your request has been granted, on the Windows Azure Developer Portal, click on Virtual Network link a the left-bottom of the page.
Select your appropriate subscription and click OK to activate your Windows Azure Connect when a pop-up occurs.
Applying Activation Token to Windows Azure Role
The next step is to get a token and apply the token to our Windows Azure Project. The intention of doing this is to tell Windows Azure Connect that this particular role is “Windows Azure Connect –enabled”.
To do that, click on Get Activation Token. When the pop-up occurs, copy the token by clicking on Copy to Clipboard.
If a Silverlight dialog show up, click on Yes to accept.
Go back to your Visual Studio’s solution, double-click on your intended role (in my cases WebRole1). Click on Virtual Network tab, check the Activate Windows Azure Connect checkbox and paste the token key that we’ve copied on the portal earlier.
Installing Windows Azure Connect Endpoint on On-premise Machine
Next step is to installing a small agent on our on-premise machine. Windows Azure Connect has the ability to connect back to on-premise machine through this small agent.
Go back to our Windows Azure Developer Portal. To get the agent, click on Install Local Endpoint button, copy the URL to the Clipboard.
Paste on your browser to download the agent. Please note that at the moment, we can only use IE to download.
When finished the download, install the agent by following the wizard.
You can click on Open Windows Azure Connect and see the detail.
As expected, the agent is not connected since it has not been configured.
Go back to your Windows Azure Developer Portal, you will now can see that your machine name (including the details of that machine) is shown on the Groups and Roles section.
In the next post, I’ll show you how to group the on-premise instance with cloud instances.