What Should You Configure Next for an FSLogix Profile Container?
You have an Azure Active Directory Domain Services (Azure AD DS) domain named contoso.com. You have an Azure Storage account named storage1. Storage1 hosts a file share named share1 that has share and file system permissions configured. Share1 is configured to use contoso.com for authentication. You create an Azure Virtual Desktop host pool named Pool1. Pool1 contains two session hosts that use the Windows 10 multi-session + Microsoft 365 Apps image. You need to configure an FSLogix profile container for Pool1. What should you do next?
Community Insight
This item tests the boundary between FSLogix agent installation and profile-container configuration; the trap is assuming a multi-session image needs the agent installed manually.
The FSLogix agent is preinstalled in the Windows 10 multi-session + Microsoft 365 Apps image, so the next step after preparing share1 is to configure the Profiles settings on Pool1's session hosts. This page establishes that answer C is correct, not installing the agent or generating a SAS key.
The most common wrong answer is A, installing the FSLogix agent again, because the image already includes it and only the profile container path and settings need configuration.
Community Discussion (22 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The share and file-system permissions and contoso.com authentication are already in place, so the remaining FSLogix task is to define the profile container location and related settings on the session hosts. In AVD, Windows 10 Enterprise multi-session images include the FSLogix agent; the administrator still must configure the Profiles settings, typically the UNC path to share1 and profile-container options. Option C matches that configuration step and is the action that makes the prepared SMB share usable for user profiles. This is why the answer is C rather than a deployment or storage-key operation.Why the Other Options Are Wrong
A is wrong because installing the FSLogix agent is not required on the Windows 10 multi-session + Microsoft 365 Apps image; the agent binaries are present by default. B is wrong because shared key access is an Azure Storage authorization setting for storage account keys and does not configure FSLogix profile containers, especially when SMB authentication is already set to contoso.com. D is wrong because a SAS key is not used by FSLogix SMB profile containers in this scenario; share1 already has AD DS-based authentication and permissions. None of these options sets the profile container UNC path or the Profiles settings that FSLogix needs.Community Comment Notes
KFM2020 explained that the Profiles setting is needed to define the UNC location of the FSLogix container and noted that FSLogix is preinstalled on multi-session images. LeGluten quoted Microsoft's FAQ saying the admin is "still responsible for configuring the FSLogix profile container," and TafMuko noted that multi-session images are Enterprise and include FSLogix. Some learners voted for A by citing general FSLogix setup documentation, but those steps apply when the agent is absent or when walking through a full deployment, not to this prebuilt image scenario. The useful consensus is that the remaining work is configuration, not installation.Official Reference
Exam Strategy
In AZ-140 FSLogix questions, first confirm whether the image is Windows 10/11 Enterprise multi-session, because that changes the next step from installing the agent to configuring profile settings. Then verify the SMB share permissions and identity source before selecting any storage-key or SAS option.
Frequently Asked Questions
Why is installing the FSLogix agent not the next step on this multi-session host?
The Windows 10 multi-session image already includes the FSLogix agent; the administrator still must configure the profile container path and settings.
Does share1 need a SAS key or shared key access for FSLogix profiles?
No. FSLogix uses SMB with contoso.com authentication plus share and NTFS permissions, so a SAS key or shared-key change is unrelated.
Related Analysis
Practice All AZ-140 Questions
Access 64 questions with complete answers and detailed explanations.
View Full AZ-140 Practice Test →