Azure enhancement Site-to-Site VPN functionality

Share this:

After Scott Guthrie announce the new enhancements on Azure, last May, I was very excited with one in particular. Multi Site-to-Site VPN. This enhancement comes at the best time. Because I have 2 datacenter and I want to connect both with the same Azure Subscription.

I did used the Site-to-Site VPN when I want to extend my datacenter to Azure. It’s very handy when you need to spin a temporary virtual machine and you are almost running out of resources in your datacenter. The possibility of extend your network to Azure and the virtual machine that you just created is accessible from your network, but you are using the Azure resources it’s pretty cool and sometimes save you time. Especially if you are outside of your organization.

Last time I did this, it was for a simple test when I was shopping with my family!

But this Site-to-Site VPN had a limitation, it only worked if you have one site (datacenter) to azure. If you have more than one datacenter (like me) you cannot use Site-to-Site VPN with the same Azure subscription. But now it’s possible with Multi Site-to-Site VPN.

That means that I can have multiple sites (datacenters) using the some Azure subscription and be able to spin virtual machines in Azure and they can be accessible from both datacenters. The cost of this stay the same!


Now with Azure you can connect different Azure Regions through VNET-to-VNET connectivity. That means that multiple virtual networks can now be directly and securely connected with one another. Using this feature, you can connect VNETs that are running in the same or different Azure regions and in case of different Azure regions have the traffic securely route via the Microsoft network backbone.

This feature enables scenarios that require presence in multiple regions (e.g. Europe and US, or East US and West US), applications that are highly available, or the integration of VNETs within a single region for a much larger network. This feature also enables you to connect VNETs across multiple different Azure account subscriptions, so you can now connect workloads across different divisions of your organization, or even different companies. The data traffic flowing between VNETs is charged at the same rate as egress traffic.


To see the full announcement click here

To have more information about Azure Virtual Network, click here

Written by Marcos Nogueira

With more than 19 years’ experience in Datacenter Architectures, Marcos Nogueira is currently working as a Senior Cloud Solution Architect. He is an expert in Private and Hybrid Cloud, with a focus on Microsoft Azure, Virtualization and System Center. He has worked in several industries, including Aerospace, Transportation, Energy, Manufacturing, Financial Services, Government, Health Care, Telecoms, IT Services, and Gas & Oil in different countries and continents.

Marcos was an MVP in System Center Cloud & Datacenter Managenment and he has +14 years as Microsoft Certified, with more than 100+ certifications (MCT, MCSE, and MCITP, among others). Marcos is also certified in VMware, CompTIA and ITIL v3. He assisted Microsoft in the development of workshops and special events on Private & Hybrid Cloud, Azure, System Center, Windows Server, Hyper-V and as a speaker at several Microsoft TechEd/Ignite and communities events around the world.

Related Post

How to move your workloads to Azure When integrating your on-premises environment with Azure, you might want to use the lift-and-shift approach to migrate some of your existing workloads...
Windows Azure and Office365 – Configuring th... So far in this series we subscribed to the services, configured the on-premises and cloud environments and in the last one we install the tool on our ...
Installing Server Management tools In this tutorial, we are going over the process to install the required software in a Windows Server 2012 or Windows Server 2012 R2 to support SMT (Se...
How to extend Azure Service Fabric to on-premise? You can deploy a Service Fabric cluster on any physical or virtual machine running the Windows Server operating system, including ones residing in you...