I know we've all been waiting for this, but Azure AD Joined AVD hosts are now supported in NMM v2.3+. You can now have environments without Azure AD DS or AD DS (domain controller) for directory services. I do want to point out some limitations currently for Azure AD joined AVD instances:
https://docs.microsoft.com/en-us/azure/virtual-desktop/deploy-azure-ad-joined-vm#known-limitations
From that link:
- Azure Virtual Desktop (classic) doesn't support Azure AD-joined VMs.
- Azure AD-joined VMs don't currently support external users.
- Azure AD-joined VMs only supports local user profiles at this time.
- Azure AD-joined VMs can't access Azure Files file shares for FSLogix or MSIX app attach. You'll need Kerberos authentication to access either of these features.
- The Windows Store client doesn't currently support Azure AD-joined VMs.
- Azure Virtual Desktop doesn't currently support single sign-on for Azure AD-joined VMs.
These are some limitation that should be taken into consideration and reviewed against your customer's needs/use case. With FSLogix profile currently unsupported/Azure Files not supported, a typical use case would be dedicated personal AVD instances as the profiles would be local. If you have any other questions feel free to drop us a support request at nmm.support@getnerdio.com.
Comments (0 comments)