How Should You Reference User1 in FSLogix Per-User Registry Settings?
You have an on-premises Active Directory Domain Services (AD DS) domain named contoso.com that syncs with an Azure AD tenant. You have an Azure subscription that is linked to the Azure AD tenant. The subscription contains a user named User1 that has the following properties: • User logon name: [email protected] • SID: S-1-5-21-4534338-1127018997-2609994386-5108 • User logon name (pre-Windows 2000): CONTOSO\User1 The subscription contains an Azure Virtual Desktop deployment. The deployment contains a domain-joined session host named Host1 and an Azure file share. You need to configure per-user FSLogix profile settings for Host1. How should you reference User1 in the FSLogix registry configuration?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests whether you know FSLogix per-user configuration is stored and matched by SID; the trap is assuming the UPN ([email protected]) or the pre-Windows 2000 logon name (CONTOSO\User1) is the key.
FSLogix per-user profile settings on a domain-joined Azure Virtual Desktop session host are keyed to the user's security identifier (SID), not to a logon name. This page confirms that option D — User1's full SID — is the correct way to reference the account in the FSLogix registry configuration on Host1.
Picking B (CONTOSO\User1) or A ([email protected]) because those are the logon names a user actually types; FSLogix applies per-user settings through a SID-keyed registry subkey, so a renamed or reassigned UPN/SAM name would not map the profile correctly.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
FSLogix stores per-user profile configuration on the session host in a registry area scoped by the account's security identifier, so Host1 needs User1's SID (S-1-5-21-4534338-1127018997-2609994386-5108) for those settings to apply only to that user. A SID is unique within the domain and is never recycled or renamed, which is precisely why the product keys per-user configuration this way. Every community respondent (Bonesurfer, jeff1988, Moot2 and ClintC03) landed on D, and Bonesurfer's stated best practice is to "reference users by their Security Identifier (SID)" because it stays "unique and consistent across domain environments." The 100% vote for D happens to align with Microsoft's documented behavior, but the decisive factor is the SID-keyed per-user model itself, not the poll.Why the Other Options Are Wrong
A ([email protected]) is the UPN — a logon attribute that can be edited, re-issued or reassigned, so it is unsuitable as a stable per-user key. B (CONTOSO\User1) is the pre-Windows 2000 / SAM-style logon name; it is domain-qualified and used for authentication, but it is also mutable and is not how FSLogix matches per-user registry settings. C (User1) drops the domain qualifier entirely and is ambiguous, matching no FSLogix per-user key structure. All three are human-facing identifiers; none is the immutable primary key FSLogix uses to bind settings to User1 on Host1.Community Comment Notes
All four commenters agree on D and each grounds the answer in the SID's uniqueness. jeff1988 points out that the SID keeps settings tied to the right account "regardless of any changes to the username or domain," which mirrors the design intent of per-user FSLogix configuration. Moot2 contributes the terse "Should be SID" and ClintC03 adds "You use the SID." reinforcing the same consensus. Their agreement is a useful sanity check, but on AZ-140 you should still derive per-user references from FSLogix's SID-keyed configuration model rather than from the vote count.Official Reference
Exam Strategy
When AZ-140 asks how to reference a specific user for per-user configuration on FSLogix, default to the SID unless the item is explicitly about credentials or sign-in. Drill the distinction that UPN and domain\user are human-facing logon names, while the SID is the machine-stable key FSLogix writes into the registry.
Frequently Asked Questions
Why is CONTOSO\User1 wrong for FSLogix per-user settings?
FSLogix applies per-user settings through a SID-keyed registry subkey on the session host; a pre-Windows 2000 or UPN logon name can change and is not the mapping key.
Does referencing the SID still work if User1's logon name later changes?
Yes. Because the SID stays constant even when the UPN or SAM logon name is edited, FSLogix continues to match the per-user settings to the same account.
Related Analysis
Practice All AZ-140 Questions
Access 64 questions with complete answers and detailed explanations.
View Full AZ-140 Practice Test →