Merge pull request #253056 from b-ahibbard/fslogix-update

sme feedback

Author: prmerger-automator[bot]

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

@@ -21,7 +21,7 @@ The following known limitations may affect access to your on-premises or Active
 
 - Azure Virtual Desktop (classic) doesn't support Azure AD-joined VMs.
 - Azure AD-joined VMs don't currently support external identities, such as Azure AD Business-to-Business (B2B) and Azure AD Business-to-Consumer (B2C).
-- Azure AD-joined VMs can only access [Azure Files shares](create-profile-container-azure-ad.md) for hybrid users using Azure AD Kerberos for FSLogix user profiles.
+- Azure AD-joined VMs can only access [Azure Files shares](create-profile-container-azure-ad.md) or [Azure NetApp Files shares](create-fslogix-profile-container.md) for hybrid users using Azure AD Kerberos for FSLogix user profiles.
 - The [Remote Desktop app for Windows](users/connect-microsoft-store.md) doesn't support Azure AD-joined VMs.
 
 ## Deploy Azure AD-joined VMs
@@ -73,7 +73,7 @@ You can enable a single sign-on experience using Azure AD authentication when ac
 
 ## User profiles
 
-You can use FSLogix profile containers with Azure AD-joined VMs when you store them on Azure Files while using hybrid user accounts. For more information, see [Create a profile container with Azure Files and Azure AD](create-profile-container-azure-ad.md).
+You can use FSLogix profile containers with Azure AD-joined VMs when you store them on Azure Files or Azure NetApp Files while using hybrid user accounts. For more information, see [Create a profile container with Azure Files and Azure AD](create-profile-container-azure-ad.md).
 
 ## Accessing on-premises resources
 
@@ -88,3 +88,4 @@ Now that you've deployed some Azure AD joined VMs, we recommend enabling single
 - [Connect with the Windows Desktop client](users/connect-windows.md)
 - [Connect with the web client](users/connect-web.md)
 - [Troubleshoot connections to Azure AD-joined VMs](troubleshoot-azure-ad-connections.md)
+- [Create a profile container with Azure NetApp Files](create-fslogix-profile-container.md)

articles/virtual-desktop/create-fslogix-profile-container.md

@@ -7,7 +7,7 @@ ms.date: 07/01/2020
 ms.author: helohr
 manager: femila
 ---
-# Create a profile container with Azure NetApp Files and AD DS
+# Create a profile container with Azure NetApp Files
 
 We recommend using FSLogix profile containers as a user profile solution for the [Azure Virtual Desktop service](overview.md). FSLogix profile containers store a complete user profile in a single container and are designed to roam profiles in non-persistent remote computing environments like Azure Virtual Desktop. When you sign in, the container dynamically attaches to the computing environment using a locally supported virtual hard disk (VHD) and Hyper-V virtual hard disk (VHDX). These advanced filter-driver technologies allow the user profile to be immediately available and appear in the system exactly like a local user profile. To learn more about FSLogix profile containers, see [FSLogix profile containers and Azure Files](fslogix-containers-azure-files.md).
 
@@ -23,6 +23,10 @@ The instructions in this guide are specifically for Azure Virtual Desktop users.
 >[!NOTE]
 >If you're looking for comparison material about the different FSLogix Profile Container storage options on Azure, see [Storage options for FSLogix profile containers](store-fslogix-profile.md).
 
+## Considerations 
+
+FSLogix profile containers on Azure NetApp Files can be accessed by users authenticating from Active Directory Domain Services (AD DS) and from [hybrid identities](../active-directory/hybrid/whatis-hybrid-identity.md), allowing Azure AD users to access profile containers without requiring line-of-sight to domain controllers from hybrid Azure AD-joined and Azure AD-joined virtual machines (VMs). For more information, see [Access SMB volumes from Azure AD joined Windows VMs](../azure-netapp-files/access-smb-volume-from-windows-client.md).
+
 ## Prerequisites
 
 Before you can create an FSLogix profile container for a host pool, you must: