Choose personal RDS host assignment and privileges independently

Source facts

Microsoft’s personal-session collection parameter associates users with their own session hosts instead of assigning the next available host at sign-in. A separate option grants the assigned user administrative privileges; omitting it leaves standard-user privileges. Automatic assignment also has its own option. With it, a new user needs an unassigned host or receives an error; without it, an administrator must assign the host before sign-in. Microsoft documentation.

Applicability

Identify the intended users, available hosts, assignment method, privilege requirement, and collection. Review whether a personal host is needed and whether local administrative rights are separately justified.

DSE recommendation

Prepare a user-to-host allocation record and approve privileges independently of assignment. Have the service owner define who can reassign a host and how departing users are handled. Check available unassigned capacity before enabling automatic assignment for additional users.

Verification

Query the collection’s actual associations and sign in with representative assigned and unassigned users. Check the resulting host and privilege level, including the no-capacity case in an approved test. Record an unexpected assignment or excessive privilege as a configuration failure before opening the collection more broadly.

Official references

Microsoft Learn: Use personal session desktops with Remote Desktop Services. Source reviewed September 8, 2026.