Skip to content

Commit 9a4f1b8

Browse files
Merge pull request #291342 from msft-jasonparker/patch-1
Updated known limitations for AVD Entra joined VMs
2 parents 8d119db + 3b874e8 commit 9a4f1b8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-desktop/azure-ad-joined-session-hosts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article will walk you through the process of deploying and accessing Micros
1717
The following known limitations may affect access to your on-premises or Active Directory domain-joined resources and you should consider them when deciding whether Microsoft Entra joined VMs are right for your environment.
1818

1919
- Microsoft Entra joined VMs don't currently support external identities, such as Microsoft Entra Business-to-Business (B2B) and Microsoft Entra Business-to-Consumer (B2C).
20-
- Microsoft Entra joined VMs can only access [Azure Files shares](create-profile-container-azure-ad.yml) or [Azure NetApp Files shares](create-fslogix-profile-container.md) for hybrid users using Microsoft Entra Kerberos for FSLogix user profiles.
20+
- Microsoft Entra joined VMs can only access [Azure Files shares](create-profile-container-azure-ad.yml) for hybrid users using Microsoft Entra Kerberos for FSLogix user profiles.
2121
- The [Remote Desktop Store app](users/connect-windows.md?pivots=rd-store) for Windows doesn't support Microsoft Entra joined VMs.
2222

2323
<a name='deploy-azure-ad-joined-vms'></a>

0 commit comments

Comments
 (0)