You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-desktop/azure-ad-joined-session-hosts.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ This article will walk you through the process of deploying and accessing Micros
17
17
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.
18
18
19
19
- 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.
21
21
- The [Remote Desktop Store app](users/connect-windows.md?pivots=rd-store) for Windows doesn't support Microsoft Entra joined VMs.
0 commit comments