In addition to building Virtual Networks on the Windows Azure cloud fabric for running Virtual Machines in the cloud, we can also securely extend those virtual networks to on-premise devices in a couple ways:
In this article, I’ll step through the configuration of Windows Azure Connect to securely connect one or more cloud-based virtual machines to one or more on-premise client or server endpoints.
In this Step-by-Step Guide, we’ll work through the process for installing and configuring Windows Azure Connect on both a pre-existing Windows Azure Virtual Machine and an on-premise client or server to enable secure cloud-to-client connectivity.
Lab Scenario: Windows Azure Connect
Lab Scenario: Windows Azure Connect
If you have additional cloud-based virtual machines or on-premise clients/servers that you wish to join together using Azure Connect, you can simply perform the steps in this Step-by-Step Guide for each additional virtual machine, client or server to create a broader connectivity solution.
The following is required to complete this step-by-step guide:
In this Step-by-Step Guide, you will complete the following exercises to configure secure cloud-to-client network connectivity between a cloud-based virtual machine and an on-premise client or server device using Windows Azure Connect:
Estimate Completion Time: 30 minutes
In this exercise, you will install and configure the Windows Azure Connect client software on each cloud-based virtual machine and on-premise client/server endpoint. The Windows Azure Connect client software is used to establish connectivity and route network traffic securely through the Windows Azure cloud to other configured endpoints. NOTE: Complete the steps in this exercise at the console of each cloud-based virtual machine ( ie., XXXlabad01 in the Lab Scenario diagram above ) and on each on-premise client and server endpoint that you wish to securely connect using Windows Azure Connect.
In this exercise, you will create two Windows Azure Connect endpoint groups: one group for cloud-based virtual machines and one group for on-premise client and/or server endpoints. After each groups is created, you will associate each endpoint with the appropriate group and configure inter-group connectivity.
In this exercise, you will test cloud-to-client secure connectivity via Windows Azure Connect by using Windows Azure Connect client diagnostics, ping and remote desktop tools.
Success! You’ve completed the configuration of Windows Azure Connect to permit secure Cloud-to-Client connectivity.
The configuration of a new Windows Azure Connect cloud-to-client secure connectivity solution is now complete. To continue your learning about Windows Server 2012 and Windows Azure, be sure to explore these other great resources:
Do you have an interesting or unique scenario that you are evaluating on the Windows Azure cloud platform? Feel free to leave your comments, feedback and ideas below to share across our IT Pro community!
Be sure to check out these additional resources:
Keith Mayer is a Principal Technical Architect at Microsoft, focused on helping ISV partners leverage the Azure cloud platform. Keith has over 20 years of experience as a technical leader of complex IT projects, in diverse roles, such as Network Engineer, IT Manager, Technical Instructor and Consultant. He has consulted and trained thousands of customers and partners worldwide on design of enterprise technology solutions.
Keith is currently certified on several Microsoft technologies, including Azure, Private Cloud, System Center, Hyper-V, Windows, Windows Server, SharePoint, SQL Server and Exchange. He also holds other industry certifications from VMware, IBM, Cisco, Citrix, HP, CheckPoint, CompTIA and Interwoven.
You can contact Keith online at http://aka.ms/AskKeith.