Operators of a Horizon Cloud environment need the SaaS management layer, not the on-prem Connection Server UI. Which console is that?
Select an answer to reveal the explanation.
Short Explanation
Cloud desktops get a cloud clipboard: Horizon Cloud Control Plane. That is not the Connection Server admin site, not App Volumes Manager, and not vCenter wearing a new hat.
Full Explanation
Operators of a Horizon Cloud environment who need the SaaS management layer—not the on-prem Connection Server UI—use Horizon Cloud Control Plane, the SaaS management layer distinct from on-premises Horizon Console. That naming is the associate-depth identifier for cloud-managed Horizon operations in a municipal subscription. Horizon Administrator on a Connection Server is the on-premises style console path, not the SaaS control plane. App Volumes Manager does not federate all cloud pods as the Horizon Cloud control plane. vCenter Server HTML5 client is not rebranded as Horizon Cloud and remains the vSphere inventory console when vSphere is actually in use. Exam caveat: on-prem pods keep Horizon Console or Administrator patterns; Horizon Cloud questions want Control Plane—do not answer vCenter or App Volumes Manager as the SaaS management layer. Operational check: sign into Horizon Cloud Control Plane for cloud pool and capacity tasks, confirm Connection Server Administrator is not the primary SaaS UI for that environment, keep vCenter reserved for any underlying vSphere inventory that truly exists, and update operator bookmarks. Keep civic diagrams labeled so help-desk and network teams do not swap these products during incidents.