Merge pull request #257926 from b-ahibbard/smb-ca

SMB CA support for MSIX app attach: what's new, faq

Author: rmca14

articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md

@@ -141,8 +141,7 @@ Before creating an SMB volume, you need to create an Active Directory connection
 
     * <a name="continuous-availability"></a>If you want to enable Continuous Availability for the SMB volume, select **Enable Continuous Availability**.    
       
-        >[!IMPORTANT]
-        >You should enable Continuous Availability for Citrix App Layering, SQL Server, [FSLogix user profile containers](../virtual-desktop/create-fslogix-profile-container.md), and FSLogix ODFC containers. Using SMB Continuous Availability shares for workloads other than Citrix App Layering, SQL Server, FSLogix user profile containers, or FSLogix ODFC containers is *not* supported. This feature is currently supported on Windows SQL Server. Linux SQL Server is not currently supported. If you are using a non-administrator (domain) account to install SQL Server, ensure that the account has the required security privilege assigned. If the domain account does not have the required security privilege (`SeSecurityPrivilege`), and the privilege cannot be set at the domain level, you can grant the privilege to the account by using the **Security privilege users** field of Active Directory connections. See [Create an Active Directory connection](create-active-directory-connections.md#create-an-active-directory-connection).
+        [!INCLUDE [SMB Continuous Availability warning](includes/smb-continuous-availability.md)]
 
         **Custom applications are not supported with SMB Continuous Availability.**
 

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

@@ -109,7 +109,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
         >[!NOTE]
         >By default, the `.snapshot` directory path is hidden from NFSv4.1 clients. Enabling the **Hide snapshot path** option will hide the .snapshot directory from NFSv3 clients; the directory will still be accessible.
 
-3. Click **Protocol**, and then complete the following actions:  
+3. Select **Protocol** then complete the following actions:  
     * Select **NFS** as the protocol type for the volume.   
 
     * Specify a unique **file path** for the volume. This path is used when you create mount targets. The requirements for the path are as follows:   
@@ -133,7 +133,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
 
     ![Specify NFS protocol](../media/azure-netapp-files/azure-netapp-files-protocol-nfs.png)
 
-4. Click **Review + Create** to review the volume details. Then click **Create** to create the volume.
+4. Select **Review + Create** to review the volume details. Select **Create** to create the volume.
 
     The volume you created appears in the Volumes page. 
 

articles/azure-netapp-files/enable-continuous-availability-existing-SMB.md

@@ -22,14 +22,9 @@ You can enable the SMB Continuous Availability (CA) feature when you [create a n
 >[!IMPORTANT]
 > Custom applications are not supported with SMB Continuous Availability.
 > 
-> See the [**Enable Continuous Availability**](azure-netapp-files-create-volumes-smb.md#continuous-availability) option for additional details and considerations. 
+> For more information, see [**Enable Continuous Availability**](azure-netapp-files-create-volumes-smb.md#continuous-availability).
 
->[!IMPORTANT]
-> You should enable Continuous Availability for [Citrix App Layering](https://docs.citrix.com/en-us/citrix-app-layering/4.html), SQL Server, [FSLogix user profile containers](../virtual-desktop/create-fslogix-profile-container.md), and FSLogix ODFC containers. Using SMB Continuous Availability shares for workloads other than Citrix App Layering, SQL Server, FSLogix user profile containers, or FSLogix ODFC containers is *not* supported. This feature is currently supported on Windows SQL Server. Linux SQL Server is not currently supported.   
-> If you are using a non-administrator (domain) account to install SQL Server, ensure that the account has the required security privilege assigned. If the domain account does not have the required security privilege (`SeSecurityPrivilege`), and the privilege cannot be set at the domain level, you can grant the privilege to the account by using the **Security privilege users** field of Active Directory connections. See [Create an Active Directory connection](create-active-directory-connections.md#create-an-active-directory-connection).
-
->[!IMPORTANT]
-> Change notifications are not supported with Continuously Available shares in Azure NetApp Files.
+[!INCLUDE [SMB Continuous Availability warning](includes/smb-continuous-availability.md)]
 
 ## Steps
        

articles/azure-netapp-files/faq-application-resilience.md

@@ -26,6 +26,8 @@ Yes, certain SMB-based applications require SMB Transparent Failover. SMB Transp
 * [FSLogix user profile containers](../virtual-desktop/create-fslogix-profile-container.md)
 * FSLogix ODFC containers
 * Microsoft SQL Server (not Linux SQL Server)
+* [MSIX app attach](../virtual-desktop/create-netapp-files.md)
+
 
 >[!CAUTION]
 >Custom applications are not supported with SMB Continuous Availability and cannot be used with SMB Continuous Availability enabled volumes.

articles/azure-netapp-files/includes/smb-continuous-availability.md

@@ -0,0 +1,40 @@
+---
+title: include file
+description: include file
+author: b-ahibbard
+ms.service: azure-netapp-files
+ms.topic: include
+ms.date: 11/07/2023
+ms.author: anfdocs
+ms.custom: include file
+
+# azure-netapp-files-create-volumes-smb.md
+# enable-continuous-availability-existing-SMB.md
+---
+
+You should enable Continuous Availability for the following workloads/use cases only:
+
+* [Citrix App Layering](https://docs.citrix.com/en-us/citrix-app-layering/4.html)
+* [FSLogix user profile containers](../../virtual-desktop/create-fslogix-profile-container.md), including [FSLogix ODFC containers](/fslogix/concepts-container-types#odfc-container)
+* [MSIX app attach with Azure Virtual Desktop](../../virtual-desktop/create-netapp-files.md)
+    * When using MSIX applications with the `CIM FS` file format:
+        * The number of AVD session hosts per volume shouldn't exceed 500.
+        * The number of MSIX applications per volume shouldn't exceed 40.
+    * When using MSIX applications with the `VHDX` file format:
+        * The number of AVD session hosts per volume shouldn't exceed 500.
+        * The number of MSIX applications per volume shouldn't exceed 60.
+    * When using a combination of MSIX applications with both the `VHDX` and `CIM FS` file formats:
+        * The number of AVD session hosts per volume shouldn't exceed 500.
+        * The number of MSIX applications per volume using the `CIM FS` file format shouldn't exceed 24.
+        * The number of MSIX applications per volume using the `VHDX` file format shouldn't exceed 24.
+* SQL Server
+    * Continuous Availability is currently supported on Windows SQL Server.
+    * Linux SQL Server is not currently supported.
+
+>[!IMPORTANT]
+>Using SMB Continuous Availability shares is only supported for Citrix App Layering, SQL Server, FSLogix user profile containers including FSLogix ODFC containers, or MSIX app attach containers. This feature is currently supported on SQL Server on Windows. Any other workload is not supported.
+>
+> If you are using a non-administrator (domain) account to install SQL Server, ensure the account has the required security privilege assigned. If the domain account does not have the required security privilege (`SeSecurityPrivilege`), and the privilege cannot be set at the domain level, you can grant the privilege to the account by using the Security privilege users field of Active Directory connections. For more information, see [Create an Active Directory connection](../create-active-directory-connections.md#create-an-active-directory-connection).
+
+>[!IMPORTANT]
+>Change notifications are not supported with Continuously Available shares in Azure NetApp Files.

articles/azure-netapp-files/whats-new.md

@@ -13,16 +13,21 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.custom: devx-track-linux
 ms.topic: overview
-ms.date: 11/02/2023
+ms.date: 11/08/2023
 ms.author: anfdocs
 ---
 
 # What's new in Azure NetApp Files
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
 
+ 
 ## November 2023
 
+* [SMB Continuous Availability (CA)](azure-netapp-files-create-volumes-smb.md#add-an-smb-volume) shares now supports MSIX app attach for Azure Virtual Desktop
+
+    In addition to Citrix App Layering, FSLogix user profiles including FSLogix ODFC containers, and Microsoft SQL Server, Azure NetApp Files now supports [MSIX app attach](../virtual-desktop/create-netapp-files.md) with SMB Continuous Availability shares to enhance resiliency during storage service maintenance operations.  Continuous Availability enables SMB transparent failover to eliminate disruptions as a result of service maintenance events and improves reliability and user experience.
+
 * [Azure NetApp Files datastores for Azure VMware Solution](../azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md#supported-regions) in select US Gov regions
 
     Azure NetApp Files now supports [Azure NetApp Files datastores for Azure VMware Solution](../azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md?tabs=azure-portal) in US Gov Arizona and US Gov Virginia regions. Azure NetApp Files datastores for Azure VMware Solution provide the ability to scale storage independently of compute and can go beyond the limits of the local instance storage provided by vSAN reducing total cost of ownership.

articles/virtual-desktop/create-netapp-files.md

@@ -30,8 +30,8 @@ To start using Azure NetApp Files:
 
 1. Set up your Azure NetApp Files account by following the instructions in [Set up your Azure NetApp Files account](create-fslogix-profile-container.md#set-up-your-azure-netapp-files-account).
 2. Create a capacity pool by following the instructions in [Set up a capacity pool](../azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md).
-3. Join a Microsoft Entra connection by following the instructions in [Join an Active Directory connection](create-fslogix-profile-container.md#join-an-active-directory-connection).
-4. Create a new volume by following the instructions in [Create a new volume](create-fslogix-profile-container.md#create-a-new-volume) and [Configure volume access parameters](create-fslogix-profile-container.md#configure-volume-access-parameters).
+3. Join an Active Directory connection by following the instructions in [Join an Active Directory connection](create-fslogix-profile-container.md#join-an-active-directory-connection).
+4. Create a new volume by following the instructions to [create an SMB volume for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-create-volumes-smb.md). Ensure select **Enable Continuous Availability**.
 5. Make sure your connection to the Azure NetApp Files share works by following the instructions in [Make sure users can access the Azure NetApp Files share](create-fslogix-profile-container.md#make-sure-users-can-access-the-azure-netapp-files-share).
 
 ## Upload an MSIX image to the Azure NetApp file share
@@ -41,7 +41,7 @@ Now that you've set up your Azure NetApp Files share, you can start uploading im
 To upload an MSIX image to your Azure NetApp Files share:
 
 1. In each session host, install the certificate that you signed the MSIX package with. Make sure to store the certificates in the folder named **Trusted People**.
-2. Copy the MSIX image you want to add to the Azure NetApps Files share.
+2. Copy the MSIX image you want to add to the Azure NetApp Files share.
 3. Go to **File Explorer** and enter the mount path, then paste the MSIX image into the mount path folder.
 
 Your MSIX image should now be accessible to your session hosts when they add an MSIX package using the Azure portal or PowerShell.