Question 310
In the Bayview Compliance pilot environment, a controlled verification is required for: An AVD design uses Entra-joined session hosts for legacy applications that require direct traditional Kerberos domain controller authentication. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A representative legacy application authenticates from the joined host without requiring a local administrator workaround. This is an independently observable result of the targeted change: Choose an AD DS or compatible managed-domain identity model for the session hosts after validating the application's actual directory requirements. It closes the specific Bayview Compliance failure: An AVD design uses Entra-joined session hosts for legacy applications that require direct traditional Kerberos domain controller authentication.
Incorrect Answers
A supported smart-card user authenticates successfully while an invalid certificate is denied without falling back silently. This is evidence for a DIFFERENT remediation: Validate smart-card certificate trust, domain-controller readiness, and supported client redirection for the chosen AVD identity scenario. That remediation addresses: A Windows Server-backed AVD deployment depends on smart-card logon but the user is prompted for password because the certificate and identity path is incomplete. It does not establish resolution of the Bayview Compliance problem: An AVD design uses Entra-joined session hosts for legacy applications that require direct traditional Kerberos domain controller authentication. The required outcome here is: A representative legacy application authenticates from the joined host without requiring a local administrator workaround.
A domain-authenticated pilot can resolve domain controllers and sign in to the session host using the documented managed-domain path. This is evidence for a DIFFERENT remediation: Configure the supported managed-domain join, required DNS, password synchronization and profile-access prerequisites for the selected identity approach. That remediation addresses: A hybrid team uses Microsoft Entra Domain Services for traditional LDAP-dependent apps but configures hosts as if password hash and DNS behavior match on-prem AD DS automatically. It does not establish resolution of the Bayview Compliance problem: An AVD design uses Entra-joined session hosts for legacy applications that require direct traditional Kerberos domain controller authentication. The required outcome here is: A representative legacy application authenticates from the joined host without requiring a local administrator workaround.
A named diagnostic user can log on through the approved support workflow without broader host administration privileges. This is evidence for a DIFFERENT remediation: Assign required local or domain rights through managed groups and policy at the host scope, separate from Azure control-plane RBAC. That remediation addresses: A help desk group can manage AVD app assignments but does not have Windows logon rights on the session host where troubleshooting requires access. It does not establish resolution of the Bayview Compliance problem: An AVD design uses Entra-joined session hosts for legacy applications that require direct traditional Kerberos domain controller authentication. The required outcome here is: A representative legacy application authenticates from the joined host without requiring a local administrator workaround.