Merge pull request #272622 from b-ahibbard/backup-afec-only

Backup afec only

Author: American-Dipper

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

@@ -10,13 +10,10 @@ 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 will 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 enable the backup feature for an Azure NetApp Files volume before policy-based backups or manual backups can be taken. 
 
 This article shows you how to configure manual backups. For policy-based backup configuration, see [Configure policy-based backups](backup-configure-policy-based.md).  
 
-> [!IMPORTANT]
-> The Azure NetApp Files backup feature is currently in preview. You need to submit a waitlist request for accessing the feature through the **[Azure NetApp Files Backup Public Preview](https://aka.ms/anfbackuppreviewsignup)** page. Wait for an official confirmation email from the Azure NetApp Files team before using the Azure NetApp Files backup feature.
-
 ## About manual backups  
 
 Every Azure NetApp Files volume must have the backup functionality enabled before any backups (policy-based or manual) can be taken.   
@@ -29,9 +26,11 @@ The following list summarizes manual backup behaviors:
 
 * 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. 
 
+[!INCLUDE [Backup registration heading](includes/backup-registration.md)]
+
 ## Requirements
 
-* Azure NetApp Files now requires you to create a backup vault before enabling backup functionality. If you have not configured a backup, refer to [Manage backup vaults](backup-vault-manage.md) for more information.
+* Azure NetApp Files now requires you to create a backup vault before enabling backup functionality. If you haven't configured a backup, see [Manage backup vaults](backup-vault-manage.md) for more information.
 * [!INCLUDE [consideration regarding deleting backups after deleting resource or subscription](includes/disable-delete-backup.md)]
 
 ## Enable backup functionality
@@ -62,13 +61,13 @@ If you haven’t done so, enable the backup functionality for the volume before
 
             `account1-pool1-vol1-backup1`   
 
-            If you are using a shorter form for the backup name, ensure that it still includes information that identifies the NetApp account, capacity pool, and volume name for display in the backup list.
+            If you're using a shorter form for the backup name, ensure that it still includes information that identifies the NetApp account, capacity pool, and volume name for display in the backup list.
 
     2. If you want to use an existing snapshot for the backup, select the **Use Existing Snapshot** option.  When you use this option, ensure that the Name field matches the existing snapshot name that is being used for the backup. 
 
 4. Select **Create**. 
 
-    When you create a manual backup, a snapshot is also created on the volume using the same name you specified for the backup. This snapshot represents the current state of the active file system. It is transferred to Azure storage. Once the backup completes, the manual backup entry appears in the list of backups for the volume.
+    When you create a manual backup, a snapshot is also created on the volume using the same name you specified for the backup. This snapshot represents the current state of the active file system. It's transferred to Azure storage. Once the backup completes, the manual backup entry appears in the list of backups for the volume.
 
 ![Screenshot that shows the New Backup window.](./media/backup-configure-manual/backup-new.png)
 

articles/azure-netapp-files/backup-configure-policy-based.md

@@ -14,9 +14,6 @@ Azure NetApp Files backup supports *policy-based* (scheduled) backups and *manua
 
 This article shows you how to configure policy-based backups. For manual backup configuration, see [Configure manual backups](backup-configure-manual.md).  
 
-> [!IMPORTANT]
-> The Azure NetApp Files backup feature is currently in preview. You need to submit a waitlist request for accessing the feature through the **[Azure NetApp Files Backup Public Preview](https://aka.ms/anfbackuppreviewsignup)** page. Wait for an official confirmation email from the Azure NetApp Files team before using the Azure NetApp Files backup feature.
-
 ## About policy-based backups    
 
 Backups are long-running operations. The system schedules backups based on the primary workload (which is given a higher priority) and runs backups in the background. Depending on the size of the volume being backed up, a backup can run in background for hours. There's no option to select the start time for backups. The service performs the backups based on the internal scheduling and optimization logic. 
@@ -25,6 +22,8 @@ Assigning a policy creates a baseline snapshot that is the current state of the
 
 [!INCLUDE [consideration regarding deleting backups after deleting resource or subscription](includes/disable-delete-backup.md)]
 
+[!INCLUDE [Backup registration heading](includes/backup-registration.md)]
+
 ## Configure a backup policy
 
 A backup policy enables a volume to be protected on a regularly scheduled interval. It does not require snapshot policies to be configured. Backup policies will continue the daily cadence based on the time of day when the backup policy is linked to the volume, using the time zone of the Azure region where the volume exists. Weekly schedules are preset to occur each Monday after the daily cadence.  Monthly schedules are preset to occur on the first day of each calendar month after the daily cadence. If backups are needed at a specific time/day, consider using [manual backups](backup-configure-manual.md). 

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

@@ -10,21 +10,10 @@ ms.author: anfdocs
 ms.custom: references_regions
 ---
 
-# Understand Azure NetApp Files backup
+# Understand Azure NetApp Files backup (preview)
 
 Azure NetApp Files backup expands the data protection capabilities of Azure NetApp Files by providing fully managed backup solution for long-term recovery, archive, and compliance. Backups created by the service are stored in Azure storage, independent of volume snapshots that are available for near-term recovery or cloning. Backups taken by the service can be restored to new Azure NetApp Files volumes within the region. Azure NetApp Files backup supports both policy-based (scheduled) backups and manual (on-demand) backups. For more information, see [How Azure NetApp Files snapshots work](snapshots-introduction.md).
 
-> [!IMPORTANT]
-> The Azure NetApp Files backup feature is currently in preview. You need to submit a waitlist request for accessing the feature through the **[Azure NetApp Files Backup Public Preview](https://aka.ms/anfbackuppreviewsignup)** page. The Azure NetApp Files backup feature is expected to be enabled within a week after you submit the waitlist request. You can check the status of feature registration by using the following command: 
->
-> ```azurepowershell-interactive
-> Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFBackupPreview                                                      
-> 
-> FeatureName      ProviderName     RegistrationState   
-> -----------      ------------     -----------------   
-> ANFBackupPreview Microsoft.NetApp Registered
-> ```
-
 ## Supported regions 
 
 Azure NetApp Files backup is supported for the following regions:   

articles/azure-netapp-files/includes/backup-registration.md

@@ -0,0 +1,30 @@
+---
+author: b-ahibbard
+ms.service: azure-netapp-files
+ms.topic: include
+ms.date: 03/20/2024
+ms.author: anfdocs
+
+# backup-configure-policy-based.md
+# backup-configure-manual.md 
+---
+
+## Register the feature
+
+Azure NetApp Files backup is currently in preview. You must register the feature before using it for the first time. 
+
+1.  Register the feature
+
+    ```azurepowershell-interactive
+    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFBackupPreview
+    ```
+
+2. Check the status of the feature registration: 
+
+    > [!NOTE]
+    > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is `Registered` before continuing.
+
+    ```azurepowershell-interactive
+    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFBackupPreview
+    ```
+You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 

articles/virtual-desktop/disaster-recovery.md

@@ -96,7 +96,7 @@ You also have the option to back up your data. You can choose one of the followi
 - For Compute data, we recommend only backing up personal host pools with [Azure Backup](../backup/backup-azure-vms-introduction.md). 
 - For Storage data, the backup solution we recommend varies based on the back-end storage you used to store user profiles:
   - If you used Azure Files Share, we recommend using [Azure Backup for File Share](../backup/azure-file-share-backup-overview.md). 
-  - If you used Azure NetApp Files, we recommend using either [Snapshots/Policies](../azure-netapp-files/snapshots-manage-policy.md) or [Azure NetApp Files Backup](../azure-netapp-files/backup-introduction.md).
+  - If you used Azure NetApp Files, we recommend using either [snapshots/policies](../azure-netapp-files/snapshots-manage-policy.md) or [Azure NetApp Files backup](../azure-netapp-files/backup-introduction.md).
 
 ## App dependencies