 Hi, I'm Amy Collier, Senior Cloud Advocate at Microsoft. With me is Federico Carini, Senior Cloud Solution Architect over AVS, and he's going over phase two connectivity between AVS private clouds and Azure VNets. On the agenda, we're going to go on the second design and the approach through the network design guide, connectivity between AVS and Azure VNets, how to connect on-premises to Azure into AVS, and then some security options. Federico, let's talk about that second design area covered by the guide. Sure. The second design area is connectivity between AVS private clouds and Azure Virtual Networks. Designing connectivity between AVS private cloud and Azure VNets is a relatively straightforward task. There are two options and which one to use is dictated by the design choices made for the previous design area which we covered in the previous video, connectivity to on-premises. In a nutshell, if in design phase one, XSR Global Reach was selected for connectivity between AVS and on-premises, VNets can be connected to AVS just by creating a connection between the AVS managed circuit and an XSR gateway deployed in the VNets itself. This is the default option and it is natively supported by AVS. If on the other hand, connectivity to on-premises leverages Azure resources deployed in VNets as it is the case when using IPsec VPNs, for example, or transit over XSR private piling, then nothing more is needed. Connectivity between AVS and Azure VNets is already there as a consequence of what you designed for design phase one. Okay. So, Federico, we've got VPN or ExpressRoute gateways to connect to Azure on-premises, then ExpressRoute gateway to connect to your AVS managed circuit and global reach for communication between on-premises and AVS circuits. Seems pretty straightforward. Is there anything else? Well, a typical requirement must be addressed when designing connectivity between AVS and Azure VNets is enforcing network security policies. Clearly, this can be done by simply defining network security groups on the Azure side. However, most enterprise customers want to leverage firewalls that they run in Azure, either Azure Firewall or third party NPAs. The guide covers this scenario and provides instructions on how to configure routing in the VNets to make sure that traffic between AVS and Azure resources in the VNets goes to the firewall when entering the VNets through the managed XSR circuit. Okay. Great. Thank you again, Federico, for that straightforward explanation for connectivity between the AVS private cloud and Azure VNets. Now, in phase three, we're going to see how to design for inbound internet connectivity for the Azure VMware solution. Thanks again. Thank you, Amy.