After a regional outage, the SaaS Workspace ONE UEM console is still reachable while on-premises Horizon is down. What should the city conclude?

After a regional outage, reachable SaaS UEM while on-prem Horizon is down shows cloud-hosted and on-premises control planes fail independently—phones can still be managed when VDI is dark. 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: Horizon does not have to be up for UEM to manage devices. Distractor concept: A SaaS UEM outage does not always take Connection Server with it. Distractor concept: UAG in the DMZ is not what keeps the SaaS UEM console online. Exam caveat: Independent failure domains: device management vs desktop brokering. Operational check: During a Horizon outage drill, confirm SaaS UEM still inventories/wipes a pilot phone while VDI remains unavailable. 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: Phones and VDI do not share one breaker panel. SaaS UEM can stay up in the provider cloud while the civic Horizon pod is dark, so device management and desktop brokering are different recovery domains. UAG in the DMZ is not why the SaaS console survived.