The city already has Active Directory in the civic data center and wants SaaS Workspace ONE UEM. How can cloud UEM still use that directory?
Select an answer to reveal the explanation.
Short Explanation
Cloud UEM is not allergic to city-hall Active Directory. A connector walks over to AD; the town does not have to burn down the directory to use SaaS.
Full Explanation
Cloud UEM can still use on-premises Active Directory through an on-premises connector; SaaS does not require abandoning the civic directory. 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: Claiming SaaS UEM cannot use on-prem AD is a false absolute. Distractor concept: Migrating every AD object into Horizon Cloud before enrollment confuses desktop control-plane choices with UEM identity. Distractor concept: NSX overlay segments do not replace Active Directory for device enrollment. Exam caveat: SaaS UEM + existing AD = connector pattern, not burn-down AD or NSX-as-directory. Operational check: Configure the connector to civic AD, bind a pilot OU/group, enroll a directory user, and confirm group-based assignments resolve. 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.