Question 90
In the Northgate Collaboration pilot environment, a controlled verification is required for: New pooled AVD hosts are domain joined but cannot use Azure Files identity authentication because the storage account was never configured for the selected identity scenario. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A standard signed-in user mounts the share without embedding a storage-account key in the session-host script. This is an independently observable result of the targeted change: Enable the supported identity-based SMB authentication model for the Azure Files account and assign necessary share and filesystem access. It closes the specific Northgate Collaboration failure: New pooled AVD hosts are domain joined but cannot use Azure Files identity authentication because the storage account was never configured for the selected identity scenario.
Incorrect Answers
A newly onboarded user creates their VHDX and saves settings without being granted full storage-account ownership. This is evidence for a DIFFERENT remediation: Assign the correct SMB share permissions together with effective filesystem ACLs for profile creation and modification. That remediation addresses: A desktop administrator grants Storage File Data SMB Share Reader and expects users to create and update their writable FSLogix profiles. It does not establish resolution of the Northgate Collaboration problem: New pooled AVD hosts are domain joined but cannot use Azure Files identity authentication because the storage account was never configured for the selected identity scenario. The required outcome here is: A standard signed-in user mounts the share without embedding a storage-account key in the session-host script.
A user mounts only their own profile while another nonadministrator account cannot read or modify that VHDX path. This is evidence for a DIFFERENT remediation: Apply documented FSLogix storage share and NTFS ACL patterns with per-user isolation and the required session-host access model. That remediation addresses: A profile container system stores VHDX files without predictable ownership or access-control inheritance, giving unrelated users access to profiles. It does not establish resolution of the Northgate Collaboration problem: New pooled AVD hosts are domain joined but cannot use Azure Files identity authentication because the storage account was never configured for the selected identity scenario. The required outcome here is: A standard signed-in user mounts the share without embedding a storage-account key in the session-host script.
A domain-eligible session host mounts the share via its private address and public network access can remain disabled. This is evidence for a DIFFERENT remediation: Configure storage-account private endpoints, SMB connectivity, private DNS, and identity-based access for Azure Files profile storage. That remediation addresses: An Azure Files profile share is created with a public endpoint even though session hosts must access storage exclusively through private networking. It does not establish resolution of the Northgate Collaboration problem: New pooled AVD hosts are domain joined but cannot use Azure Files identity authentication because the storage account was never configured for the selected identity scenario. The required outcome here is: A standard signed-in user mounts the share without embedding a storage-account key in the session-host script.