Wely's Cloud Journey

I was super excited to hear the announcement by Microsoft at PDC2010 regarding the Windows Azure Connect. With Windows Azure Connect, we would be able to connect cloud instances (VMs on the cloud) with on-premise machine through logical virtual network. This really solves many scenarios that we are facing today, such as:

• Connecting on-premise SQL Server database from Windows Azure instances.
• Using on-premise SMTP gateway from Windows Azure instances.
• Windows Azure instance domain-joined to corporate Active Directory
• Remote Administration and troubleshooting on Windows Azure Role.

The following figure illustrates how the Windows Azure Connect works.

In order to enable Windows Azure Connect, the following is the steps that we would need to do. A detail step-by-step post will be followed on subsequent post.

• Enabling Windows Azure Connect at the Windows Azure Developer Portal.
• A tiny “Windows Azure Connect” engine will be installed on our on-premise application.
• A role group then must be created in order select which of the Windows Azure Roles and on-premise will be included.
• Your on-premise machine name will be shown on the developer portal when it’s successfully connected.
• Then the machines on that group regardless cloud or on-premise would be able to ping each other

I will show you the “how-to” on the subsequent post, stay tune here..

1. How to establishing virtual network connection between cloud and on-premise with Windows Azure Connect (Part 1– Preparing on-premise server and Configuring Firewall) | Wely's Cloud Journey... says:

   January 15, 2012 at 9:43 pm

   [...] between cloud instances and on-premise server with Windows Azure Connect. Please check out my last post about how the idea and concept beyond Windows Azure Connect [...]

   Reply to this Comment