The 311 desktop pool must be entitled to a civic directory group. What identity dependency does Horizon have in the normal municipal design?

The 311 desktop pool entitled to a civic directory group depends on Active Directory users and groups as the normal municipal identity source for Horizon. 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: A Horizon-only local user database is not the designed civic identity source. Distractor concept: Workspace ONE Boxer contacts do not entitle the desktop pool. Distractor concept: NSX security groups are not the standard Horizon entitlement identity source here. Exam caveat: Horizon entitlements hang off AD users/groups in the usual design. Operational check: Entitle via an AD group, add/remove a test user, and confirm pool launch follows directory membership. 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: Horizon does not keep its own little phone book as the civic design. Entitlements hang off Active Directory users and groups, the same directory that already knows the 311 staff. Boxer contacts and NSX groups are not how you entitle a desktop pool.