Merge pull request #270837 from rvandenbedem/patch-2

Update azure-vmware-solution-horizon.md

Author: v-dirichards

articles/azure-vmware/azure-vmware-solution-horizon.md

@@ -3,15 +3,14 @@ title: Deploy Horizon on Azure VMware Solution
 description: Learn how to deploy VMware Horizon on Azure VMware Solution.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 11/27/2023
+ms.date: 4/1/2024
 ms.custom: engagement-fy23
 ---
 
-
 # Deploy Horizon on Azure VMware Solution 
 
 >[!NOTE]
->This document focuses on the VMware Horizon product, formerly known as Horizon 7. Horizon is a different solution than Horizon Cloud on Azure, although there are some shared components. Key advantages of the Azure VMware Solution include both a more straightforward sizing method and the integration of VMware Cloud Foundation management into the Azure portal.
+>This document focuses on the VMware Horizon product, formerly known as Horizon 7. Horizon is a different solution than Horizon Cloud on Azure, although there are some shared components. Key advantages of the Azure VMware Solution include both a more straightforward sizing method and the integration of Software-Defined Data Center (SDDC) private cloud management into the Azure portal.
 
 [VMware Horizon](https://www.vmware.com/products/horizon.html)®, a virtual desktop and applications platform, runs in the data center and provides simple and centralized management. It delivers virtual desktops and applications on any device, anywhere. Horizon lets you create, and broker connections to Windows and Linux virtual desktops, Remote Desktop Server (RDS) hosted applications, desktops, and physical machines.
 
@@ -23,9 +22,11 @@ Here, we focus specifically on deploying Horizon on Azure VMware Solution. For g
 
 * [Horizon Reference Architecture](https://techzone.vmware.com/resource/workspace-one-and-horizon-reference-architecture)
 
-With Horizon's introduction on Azure VMware Solution, there are now two Virtual Desktop Infrastructure (VDI) solutions on the Azure platform. The following diagram summarizes the key differences at a high level.
+With Horizon's introduction on Azure VMware Solution, there are now two Virtual Desktop Infrastructure (VDI) solutions on the Azure platform:
+
+* VMware Horizon on Azure VMware Solution
 
-:::image type="content" source="media/vmware-horizon/difference-horizon-azure-vmware-solution-horizon-cloud-azure.png" alt-text="Diagram showing the differences between Horizon on Azure VMware Solution and Horizon Cloud on Azure." border="false":::
+* VMware Horizon Cloud (Desktop-as-a-Service Model)
 
 Horizon 2006 and later versions on the Horizon 8 release line supports both on-premises and Azure VMware Solution deployment. There are a few Horizon features that are supported on-premises but not on Azure VMware Solution. Other products in the Horizon ecosystem are also supported. For more information, see [feature parity and interoperability](https://kb.vmware.com/s/article/80850).
 
@@ -67,9 +68,9 @@ Customers are required to use the Cloud Admin role, which has a limited set of v
 
 A typical Horizon architecture design uses a pod and block strategy. A block is a single vCenter Server, while multiple blocks combined make a pod. A Horizon pod is a unit of organization determined by Horizon scalability limits. Each Horizon pod has a separate management portal, and so a standard design practice is to minimize the number of pods.
 
-Every cloud has its own network connectivity scheme. Combine that with VMware SDDC networking / NSX-T Data Center, the Azure VMware Solution network connectivity presents unique requirements for deploying Horizon that is different from on-premises.
+Every cloud has its own network connectivity scheme. Combine that with VMware NSX, the Azure VMware Solution network connectivity presents unique requirements for deploying Horizon that is different from on-premises.
 
-Each Azure private cloud and SDDC can handle 4,000 desktop or application sessions, assuming:
+Each Azure VMware Solution private cloud and SDDC can handle 4,000 desktop or application sessions, assuming:
 
 * The workload traffic aligns with the LoginVSI task worker profile.
 
@@ -82,21 +83,21 @@ Each Azure private cloud and SDDC can handle 4,000 desktop or application sessio
 
 Given the Azure private cloud and SDDC max limit, we recommend a deployment architecture where the Horizon Connection Servers and VMware Unified Access Gateways (UAGs) are running inside the Azure Virtual Network. It effectively turns each Azure private cloud and SDDC into a block. In turn, maximizing the scalability of Horizon running on Azure VMware Solution.
 
-The connection from Azure Virtual Network to the Azure private clouds / SDDCs should be configured with ExpressRoute FastPath. The following diagram shows a basic Horizon pod deployment.
+The connection from Azure Virtual Network to the Azure private clouds / SDDCs should be configured with ExpressRoute Connections (FastPath enabled). The following diagram shows a basic Horizon pod deployment.
 
-:::image type="content" source="media/vmware-horizon/horizon-pod-deployment-expresspath-fast-path.png" alt-text="Diagram showing the typical Horizon pod deployment using ExpressPath Fast Path." border="false":::
+:::image type="content" source="media/vmware-horizon/horizon-pod-deployment-expressroute-connection-fast-path.png" alt-text="Diagram showing the typical Horizon pod deployment using ExpressRoute Connections (FastPath enabled)." border="false" lightbox="media/vmware-horizon/horizon-pod-deployment-expressroute-connection-fast-path.png":::
 
 ## Network connectivity to scale Horizon on Azure VMware Solution
 
 This section lays out the network architecture at a high level with some common deployment examples to help you scale Horizon on Azure VMware Solution. The focus is specifically on critical networking elements. 
 
 ### Single Horizon pod on Azure VMware Solution
 
-:::image type="content" source="media/vmware-horizon/single-horizon-pod-azure-vmware-solution.png" alt-text="Diagram showing a single Horizon pod on Azure VMware Solution." border="false":::
+:::image type="content" source="media/vmware-horizon/single-horizon-pod-azure-vmware-solution.png" alt-text="Diagram showing a single Horizon pod on Azure VMware Solution." border="false" lightbox="media/vmware-horizon/single-horizon-pod-azure-vmware-solution.png":::
 
 A single Horizon pod is the most straight forward deployment scenario because you deploy just one Horizon pod in the US East region.  Since each private cloud and SDDC is estimated to handle 4,000 desktop sessions, you deploy the maximum Horizon pod size.  You can plan the deployment of up to three private clouds/SDDCs.
 
-With the Horizon infrastructure virtual machines (VMs) deployed in Azure Virtual Network, you can reach the 12,000 sessions per Horizon pod. The connection between each private cloud and SDDC to the Azure Virtual Network is ExpressRoute Fast Path.  No east-west traffic between private clouds is needed. 
+With the Horizon infrastructure virtual machines (VMs) deployed in Azure Virtual Network, you can reach the 12,000 sessions per Horizon pod. The connection between each private cloud and SDDC to the Azure Virtual Network is an ExpressRoute Connection (FastPath enabled).  No east-west traffic between private clouds is needed. 
 
 Key assumptions for this basic deployment example include that:
 
@@ -110,7 +111,7 @@ A variation on the basic example might be to support connectivity for on-premise
 
 The diagram shows how to support connectivity for on-premises resources. To connect to your corporate network to the Azure Virtual Network, you need an ExpressRoute circuit. You need to connect your corporate network with each of the private cloud and SDDCs using ExpressRoute Global Reach. It allows the connectivity from the SDDC to the ExpressRoute circuit and on-premises resources. 
 
-:::image type="content" source="media/vmware-horizon/connect-corporate-network-azure-virtual-network.png" alt-text="Diagram showing the connection of a corporate network to an Azure Virtual Network." border="false":::
+:::image type="content" source="media/vmware-horizon/connect-corporate-network-azure-virtual-network.png" alt-text="Diagram showing the connection of a corporate network to an Azure Virtual Network." border="false" lightbox="media/vmware-horizon/connect-corporate-network-azure-virtual-network.png":::
 
 ### Multiple Horizon pods on Azure VMware Solution across multiple regions
 
@@ -120,7 +121,7 @@ Connect the Azure Virtual Network in each region to the private clouds/SDDCs in
 
 The same principles apply if you deploy two Horizon pods in the same region. Make sure to deploy the second Horizon pod in a *separate Azure Virtual Network*. Just like the single pod example, you can connect your corporate network and on-premises pod to this multi-pod/region example using ExpressRoute and Global Reach. 
 
-:::image type="content" source="media/vmware-horizon/multiple-horizon-pod-azure-vmware-solution.png" alt-text=" Diagram showing multiple Horizon pods on Azure VMware Solution across multiple regions." border="false":::
+:::image type="content" source="media/vmware-horizon/multiple-horizon-pod-azure-vmware-solution.png" alt-text=" Diagram showing multiple Horizon pods on Azure VMware Solution across multiple regions." border="false" lightbox="media/vmware-horizon/multiple-horizon-pod-azure-vmware-solution.png":::
 
 ## Size Azure VMware Solution hosts for Horizon deployments