Council asks whether "moving 311 to the cloud" means deleting the on-premises Horizon Connection Servers this quarter. How should the technician answer?

EUC can be mixed: SaaS UEM for phones and on-premises Horizon for 311 desktops; cloud language does not require deleting Connection Servers this quarter. In municipal EUC terms, treat the endpoint as a window into city systems when the architecture says so, not as the system of record for the files or apps in the stem. Distractor concept: Cloud is not all-or-nothing forcing Connection Server deletion before UEM can be SaaS. Distractor concept: SaaS UEM can coexist with an on-premises Horizon pod. Distractor concept: Deleting Connection Servers so NSX can broker desktops misassigns brokering to NSX. Exam caveat: Hybrid EUC is valid—SaaS UEM + on-prem Horizon is a common municipal pattern. Operational check: Keep the 311 Horizon pod online, enroll phones to SaaS UEM, and verify both paths in a pilot before any decommission talk. Record the chosen control and the rejected failure modes in the civic change ticket or runbook so on-call staff and auditors share the same rationale after the next maintenance window. Re-validate after personnel or image changes that the same control still meets the city's continuity, security, and support expectations for this service. Helpdesk coaching tip aligned to the conversational brief: Cloud is not a wrecking ball for every on-site box. The city can park phones in SaaS UEM and leave 311 desktops on the local Horizon pod.