A county already uses Azure AD and Azure regions for civic SaaS. Leadership wants VDI in that same cloud. Which Horizon Cloud environment type matches that choice?
Select an answer to reveal the explanation.
Short Explanation
Already living in Azure AD and Azure regions? Park the desktops in Horizon Cloud on Azure. That is a named environment type—not NSX in AWS, not “Cloud cannot do Azure,” and not Assist.
Full Explanation
A county that already uses Azure AD and Azure regions for civic SaaS and wants VDI in that same cloud should pick Horizon Cloud on Azure, aligning desktops with the existing Azure identity and regional footprint. That named environment type matches a “stay in Azure” municipal strategy for assessors and clerks. NSX-T stretched into AWS is not the required desktop platform for an Azure-aligned county. Claiming on-prem Horizon 8 only is incorrect because Horizon Cloud can run on Azure. Workspace ONE Assist is remote support for UEM endpoints, not the Azure DaaS control plane. Exam caveat: identity integration details vary by design, but when the stem anchors on Azure AD and Azure regions, the environment type to name is Horizon Cloud on Azure. Operational check: record Horizon Cloud on Azure as the selected environment type in the county architecture decision record, confirm alignment with Azure regions and identity direction, reject Assist or NSX-to-AWS as the VDI platform answer, and present the choice to leadership with clear non-goals. Keep civic diagrams labeled so help-desk and network teams do not swap these products during incidents. Document the successful test in the municipal runbook for the next change window.