change manual backup workflow

Author: b-ahibbard

articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md

@@ -14,7 +14,7 @@ ms.custom: devx-track-azurecli, subject-armqs, mode-ui, devx-track-azurepowershe
 
 This article shows you how to quickly set up Azure NetApp Files and create an NFS volume. 
 
-In this quickstart, you will set up the following items:
+In this quickstart, you set up the following items:
 
 - Registration for NetApp Resource Provider
 - A NetApp account
@@ -265,13 +265,13 @@ The following code snippet shows how to create a capacity pool in an Azure Resou
 
 4. Select **Protocol**, and then complete the following actions:
     * Select **NFS** as the protocol type for the volume.
-    * Enter **myfilepath1** as the file path that will be used to create the export path for the volume.
+    * Enter **myfilepath1** for the file path used to create the export path for the volume.
     * Select the NFS version (**NFSv3** or **NFSv4.1**) for the volume.
       See [considerations](azure-netapp-files-create-volumes.md#considerations) and [best practice](azure-netapp-files-create-volumes.md#best-practice) about NFS versions.
 
     ![Screenshot of NFS protocol for selection.](./media/azure-netapp-files-quickstart-set-up-account-create-volumes/azure-netapp-files-quickstart-protocol-nfs.png)
 
-5. Select **Review + create** to display information for the volume you are creating.  
+5. Select **Review + create** to display information for the volume you're creating.  
 
 6. Select **Create** to create the volume. 
     The created volume appears in the Volumes blade.
@@ -389,14 +389,13 @@ The following code snippets show how to set up a VNet and create an Azure NetApp
 
 # [Portal](#tab/azure-portal)
 
-When you are done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
+When you're done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
 
 > [!IMPORTANT]
-> All resources within the resource groups will be permanently deleted and cannot be undone.
-
+>Deleting a resource group also deletes all resources within it. The action can't be undone.  
 
 >[!IMPORTANT]
->Before you delete a resource group, you must first delete the backups. Deleting a resource group will not delete the backups. You can preemptively delete backups on volumes by [disabling the backup policy](backup-disable.md) or you can [manually delete the backups](backup-delete.md). If you delete the resource group without disabling backups, backups will continue to impact your billing.  
+>Before you delete a resource group, you must first delete the backups. Deleting a resource group will not delete the backups. You can preemptively delete backups on volumes by [manually delete the backups](backup-delete.md). If you delete the resource group without deleting all the backups, you can't see those backups anymore but can continue to incur billing for them. In case you're wrongly billed for some backups, open a support case ticket to get this issue resolved. 
 
 1. In the Azure portal's search box, enter **Azure NetApp Files** and then select **Azure NetApp Files** from the list that appears.
 
@@ -409,18 +408,18 @@ When you are done and if you want to, you can delete the resource group. The act
 
     ![Screenshot that highlights the Delete resource group button.](./media/azure-netapp-files-quickstart-set-up-account-create-volumes/azure-netapp-files-azure-delete-resource-group.png)
 
-    A window opens and displays a warning about the resources that will be deleted with the resource group.
+    A window opens and displays a warning about the resources to be deleted with the resource group.
 
 4. Enter the name of the resource group (myRG1) to confirm that you want to permanently delete the resource group and all resources in it, and then select **Delete**.
 
     ![Screenshot showing confirmation of deleting resource group.](./media/azure-netapp-files-quickstart-set-up-account-create-volumes/azure-netapp-files-azure-confirm-resource-group-deletion.png)
 
 # [PowerShell](#tab/azure-powershell)
 
-When you are done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
+When you're done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
 
 > [!IMPORTANT]
-> All resources within the resource groups will be permanently deleted and cannot be undone.
+>Deleting a resource group also deletes all resources within it. The action can't be undone.  
 
 1. Delete resource group by using the [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup) command.
 
@@ -430,10 +429,10 @@ When you are done and if you want to, you can delete the resource group. The act
 
 # [Azure CLI](#tab/azure-cli)
 
-When you are done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
+When you're done and if you want to, you can delete the resource group. The action of deleting a resource group is irreversible.
 
 > [!IMPORTANT]
-> All resources within the resource groups will be permanently deleted and cannot be undone.
+>Deleting a resource group also deletes all resources within it. The action can't be undone.  
 
 1. Delete resource group by using the [az group delete](/cli/azure/group#az-group-delete) command.
 

articles/azure-netapp-files/backup-configure-manual.md

@@ -10,21 +10,21 @@ ms.author: anfdocs
 ---
 # Configure manual backups for Azure NetApp Files 
 
-Azure NetApp Files backup supports *policy-based* (scheduled) backups and *manual* (on-demand) backups at the volume level. You can use both types of backups in the same volume. During the configuration process, you enable the backup feature for an Azure NetApp Files volume before policy-based backups or manual backups can be taken. 
+Azure NetApp Files backup supports *policy-based* (scheduled) backups and *manual* (on-demand) backups at the volume level. You can use both types of backups in the same volume. During the configuration process, you need to assign a backup vault to Azure NetApp Files volume before policy-based backups or manual backups can be created. 
 
 This article shows you how to configure manual backups. For policy-based backup configuration, see [Configure policy-based backups](backup-configure-policy-based.md).  
 
 ## About manual backups  
 
-Every Azure NetApp Files volume must have the backup functionality enabled before any backups (policy-based or manual) can be taken.   
+Every Azure NetApp Files volume must have a backup vault assigned before any backups (policy-based or manual) can be taken.   
 
-After you enable the backup functionality, you can choose to manually back up a volume. A manual backup takes a point-in-time snapshot of the active file system and backs up   that snapshot to the Azure storage account.
+After you assign a backup vault, you can choose to manually back up a volume. A manual backup takes a point-in-time snapshot of the active file system and backs up that snapshot to the Azure storage account.
 
 The following list summarizes manual backup behaviors:  
 
-* You can create manual backups on a volume even if the volume is already backup-enabled and configured with backup policies.  However, there can be only one outstanding manual-backup request for the volume. If you assign a backup policy and if the baseline transfer is still in progress, then the creation of a manual backup will be blocked until the baseline transfer is complete.
+* You can create manual backups on a volume even if the volume is already assigned to a backup vault and configured with backup policies.  However, there can be only one outstanding manual-backup request for the volume. If you assign a backup policy and if the baseline transfer is still in progress, then the creation of a manual backup is blocked until the baseline transfer is complete.
 
-* Unless you specify an existing snapshot to use for a backup, creating a manual backup automatically generates a snapshot on the volume. The snapshot is then transferred to Azure storage. The snapshot created on the volume will be retained until the next manual backup is created. During the subsequent manual backup operation, older snapshots will be cleaned up. You can't delete the snapshot generated for the latest manual backup. 
+* Unless you specify an existing snapshot to use for a backup, creating a manual backup automatically generates a snapshot on the volume. The snapshot is then transferred to Azure storage. The snapshot created on the volume will be retained until the next manual backup is created. During the subsequent manual backup operation, older snapshots are cleaned up. You can't delete the snapshot generated for the latest manual backup. 
 
 [!INCLUDE [Backup registration heading](includes/backup-registration.md)]
 
@@ -35,11 +35,11 @@ The following list summarizes manual backup behaviors:
 
 ## Enable backup functionality
 
-If you haven’t done so, enable the backup functionality for the volume before creating manual backups: 
+If you haven’t done so, assign a backup vault to the volume before creating manual backups: 
 
-1. Go to **Volumes** and select the specific volume for which you want to enable backup.
+1. Go to **Volumes** and select the specific volume for which you want to configure backups.
 2. Select **Configure**.
-3. In the Configure Backup page, toggle the **Enabled** setting to **On**.   
+3. In the Configure Backup page, select the backup vault from the dropdown menu.  
 4. Select **OK**.   
 
 ![Screenshot that shows the Enabled setting of Configure Backups window.](./media/shared/backup-configure-enabled.png)

articles/azure-netapp-files/backup-disable.md

@@ -15,7 +15,10 @@ You can disable the backup functionality for a volume if you no longer need the
 > [!IMPORTANT]
 > Disabling backups for a volume deletes all the backups stored in the Azure storage for that volume.
 
-If a volume is deleted but the backup policy wasn’t disabled before the volume deletion, all the backups related to the volume are retained in the Azure storage and will be listed under the associated NetApp account. 
+If a volume is deleted but the backup policy wasn’t disabled before the volume deletion, all the backups related to the volume are retained in the Azure storage and listed under the associated NetApp account. 
+
+>[!IMPORTANT]
+>Beginning with the 2023.09 API version, the `backupEnabled` property is no longer supported on Azure NetApp Files.  
 
 ## Steps