This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
I have previously talked about Azure VMware Solution Landing Zone Accelerator (AVS LZ) and the automation tools in my previous blog post. This open-source solution provides an architectural approach and reference implementation to prepare Azure landing zone subscriptions for a scalable Azure VMware Solution.
We have received feedback from many of you that there are a lot of decisions and important choices to make when designing your Azure VMware Solution deployment. We are bringing you new additions as part of the AVS LZ which is an Azure VMware Solution Landing Zone Accelerator Network Design Guide.
Using this guide will walk you through the networking options and what may be best for your organization. Because each decision, impacts the next it is imperative to look at all the networking choices and what fits your needs. This recommended approach aligns with the Azure Landing Zone reference architecture.
Using this guide will walk you through the networking options and what may be best for your organization. Because each decision, impacts the next it is imperative to look at all the networking choices and what fits your needs. This recommended approach aligns with the Azure Landing Zone reference architecture.
The AVS Accelerator Network Design Guide can be found here to follow along with the videos provided below.
Federico Guerrini, Senior Cloud Architect walk us through each decision.
Overview
Federico talks about the flowchart and decisions to make when starting out your connectivity option for AVS. Start with understanding the basics here. There are 4 design areas with each decision potentially impacting the next. Hence, the importance of choosing what is correct for your environment.
We decided to make bite sized videos for easy consumption and to help make your networking decisions quicker and easier.
Introduction - Overview of the Network Design Guide
Phase 1 - Connectivity between Azure VMware Solution and on-premises sites
Here we go over the first design approach and best order for use. The guide describes three implementation options in order of complexity with the simplest option being preferable first. Options like Global reach, IPSec VPN and other choices are covered.
Phase 2 - Connectivity between AVS private clouds and Azure VNets
This is the second design approach connecting AVS to Azure VNets. Two options are available and dictated by your previous choice in the Phase 1 of design.
Phase 3 - Inbound Internet Connectivity for AVS
The Network Design Guide advocates starting with your inbound internet connectivity for AVS and then address outbound afterwards. Decisions for inbound internet connections can set constraints for your outbound connectivity.
Phase 4 - Outbound Internet Connectivity for AVS
Outbound connectivity is about Source-NAT connections initiated by Azure VMware Solution VMs.
The easiest option is to let the platform do that on your behalf known as “Managed SNAT” in the Azure portal. The other option is to use Public IPs on the NSX-T edge as a SNAT pool. This allows you to decide which SNAT pool to use, and to do more advanced things such as using different IPs for SNAT-ting different connections. This can be done by means of proper NSX-T configuration. Finally, you can implement SNAT in Azure. To do so, a default route must be announced from Azure to AVS
The Network Design guide will assist you in all the necessary design phases and help ensure you make the correct choices when choosing which connection option is the best solution for your Azure VMware Solution design.
Coming soon will be additional blogs and videos discussing the details of how to deploy some of the networking design scenarios outlined in the Azure VMware Solution Landing Zone here.
Also be sure to check out upcoming webinar: Get Started with Azure VMware Solution: A Look Inside