cross-subscription replication support

Author: b-ahibbard

articles/azure-netapp-files/TOC.yml

@@ -441,7 +441,7 @@
         href: backup-delete.md 	
     - name: Manage replication
       items:
-      - name: Create cross-region replication
+      - name: Create volume replication
         href: cross-region-replication-create-peering.md
       - name: Display health and monitor status of replication relationship
         href: cross-region-replication-display-health-status.md

articles/azure-netapp-files/cross-region-replication-create-peering.md

@@ -5,18 +5,42 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/23/2023
+ms.date: 04/23/2025
 ms.author: anfdocs
 ---
 # Create volume replication for Azure NetApp Files
 
-This article shows you how to set up cross-region replication by creating replication peering. 
+Azure NetApp Files supports [cross-zone](cross-region-replication-introduction.md) and [cross-zone replication](cross-zone-replication-introduction.md).
 
-Setting up replication peering enables you to asynchronously replicate data from an Azure NetApp Files volume (source) to another Azure NetApp Files volume (destination). The source volume and the destination volume must be deployed in separate regions. The service level for the destination capacity pool can match that of the source capacity pool, or you can select a different service level.   
+Setting up replication peering enables you to asynchronously replicate data from an Azure NetApp Files volume (source) to another Azure NetApp Files volume (destination). You can create volume replication between regions (the source and destination volumes reside in different regions, this is known as cross-region replication), or within a region where the replication is established to a different zone in the same region (this is known as cross-zone replication).  
 
-Azure NetApp Files replication does not currently support multiple subscriptions; all replications must be performed under a single subscription.
+>[!NOTE] 
+>During normal operation, the destination volume in an Azure NetApp Files replication relationship is available for read-only access. The destination volume becomes available for read-write operations when the replication is stopped. Any subsequent changes to the destination volume need to be synchronized with the source volume with a [reverse-resync operation](cross-region-replication-manage-disaster-recovery.md#resync-replication), after after which the normal replication can be resumed. 
 
-Before you begin, ensure that you have reviewed the [requirements and considerations for using cross-region replication](cross-region-replication-requirements-considerations.md).  
+Replication is permitted between different subscriptions under the same tenant ID. Replication across tenants isn't supported. Replication is supported with capacity pools of the same and different service level. For example, the source volume can be in an Ultra service level capacity pool, and the destination volume can be in a Standard service level capacity pool or any other service level. Volumes can be moved to a capacity pool with a different service level dynamically and without interruption to the service. 
+
+Before you begin, ensure you have reviewed the [requirements and considerations for using cross-region replication](cross-region-replication-requirements-considerations.md).  
+
+## Register for cross-subscription replication 
+
+Before using cross-subscription replication, you must register for the feature. Feature registration can take up to 60 minutes to complete.
+
+1. Register the feature
+
+    ```azurepowershell-interactive
+    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCrossSubscriptionReplication
+    ```
+
+2. Check the status of the feature registration: 
+
+    > [!NOTE]
+    > The **RegistrationState** might remain 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 ANFCrossSubscriptionReplication
+    ```
+
+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. 
 
 ## Locate the source volume resource ID  
 
@@ -29,9 +53,11 @@ You need to obtain the resource ID of the source volume that you want to replica
 
 ## Create the data replication volume (the destination volume)
 
-You need to create a destination volume where you want the data from the source volume to be replicated to. Before you can create a destination volume, you need to have a NetApp account and a capacity pool in the destination region. 
+You need to create a destination volume where you want the data from the source volume to be replicated to. Before you can create a **cross-region** destination volume, you need to have a NetApp account and a capacity pool in the destination region. 
+
+For **cross-zone replication**, begin with step four. 
 
-1. The destination account must be in a different region from the source volume region. If necessary, create a NetApp account in the Azure region to be used for replication by following the steps in [Create a NetApp account](azure-netapp-files-create-netapp-account.md).   
+1. If necessary, create a NetApp account in the Azure region to be used for replication by following the steps in [Create a NetApp account](azure-netapp-files-create-netapp-account.md).   
 You can also select an existing NetApp account in a different region.  
 
 2. If necessary, create a capacity pool in the newly created NetApp account by following the steps in [Create a capacity pool](azure-netapp-files-set-up-capacity-pool.md).   
@@ -51,7 +77,7 @@ You can also select an existing NetApp account in a different region.
     * Capacity pool
     * Volume quota
         > [!NOTE] 
-        > The volume quota (size) for the destination volume should mirror that of the source volume. If you specify a size that is smaller than the source volume, the destination volume is automatically resized to the source volume size. 
+        > The volume quota (size) for the destination volume should mirror that of the source volume. If you specify a size that is smaller than the source volume, the destination volume is automatically resized to the source volume's size. 
     * Virtual network 
     * Subnet
 
@@ -97,6 +123,8 @@ To authorize the replication, you need to obtain the resource ID of the replicat
 
 * [Cross-region replication](cross-region-replication-introduction.md)
 * [Requirements and considerations for using cross-region replication](cross-region-replication-requirements-considerations.md)
+* [Cross-zone replication](cross-zone-replication-introduction.md)
+* [Requirements and considerations for cross-zone replication](cross-zone-replication-requirements-considerations.md)
 * [Display health status of replication relationship](cross-region-replication-display-health-status.md)
 * [Volume replication metrics](azure-netapp-files-metrics.md#replication)
 * [Manage disaster recovery](cross-region-replication-manage-disaster-recovery.md)

articles/azure-netapp-files/cross-region-replication-requirements-considerations.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 02/13/2025
+ms.date: 04/23/2025
 ms.author: anfdocs
 ---
 
@@ -23,7 +23,7 @@ This article describes requirements and considerations about [using the volume c
     >Failover is a manual process. When you need to activate the destination volume (for example, when you want to fail over to the destination region), you need to break replication peering then mount the destination volume. For more information, see [fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume)
     >[!IMPORTANT]
     > A volume with an active backup policy enabled can't be the destination volume in a reverse resync operation. You must suspend the backup policy on the volume prior to starting the reverse resync then resume when the reverse resync completes. 
-* Azure NetApp Files replication doesn't currently support multiple subscriptions; all replications must be performed under a single subscription.
+* Azure NetApp Files replication is supported within a subscription and between subscriptions under the same tenant. You must [register this feature](cross-region-replication-create-peering.md#register-for-cross-subscription-replication) before using it for the first time. 
 * See [resource limits](azure-netapp-files-resource-limits.md) for the maximum number of cross-region replication destination volumes. You can open a support ticket to [request a limit increase](azure-netapp-files-resource-limits.md#request-limit-increase) in the default quota of replication destination volumes (per subscription in a region).
 * There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.  
 * Cascading and fan in/out topologies aren't supported.

articles/azure-netapp-files/cross-zone-replication-requirements-considerations.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 02/13/2025
+ms.date: 04/23/2025
 ms.author: anfdocs
 ---
 # Requirements and considerations for using cross-zone replication 
@@ -22,7 +22,7 @@ This article describes requirements and considerations about [using the volume c
 * The replication destination volume is read-only until you fail over to the destination zone to enable the destination volume for read and write. For more information about the failover process, see [fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
     >[!IMPORTANT]
     >Failover is a manual process. When you need to activate the destination volume (for example, when you want to fail over to the destination region), you need to break replication peering then mount the destination volume. For more information, see [fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
-* Azure NetApp Files replication doesn't currently support multiple subscriptions; all replications must be performed under a single subscription.
+* Azure NetApp Files replication is supported within a subscription and between subscriptions under the same tenant. You must [register this feature](cross-region-replication-create-peering.md#register-for-cross-subscription-replication) before using it for the first time. 
 * See [resource limits](azure-netapp-files-resource-limits.md) for the maximum number of cross-zone destination volumes. You can open a support ticket to [request a limit increase](azure-netapp-files-resource-limits.md#request-limit-increase) in the default quota of replication destination volumes (per subscription in a region). 
 * There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.  
 * Cross-zone replication doesn't support cascading and fan in/out topologies.

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

@@ -14,6 +14,10 @@ ms.author: anfdocs
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
 
+* [Cross-subscription replication](cross-region-replication-create-peering.md)
+
+    Azure NetApp Files cross-subscription replication enables replication across different subscriptions under the same tenant. This features enhances disaster recovery and operational agility by leveraging NetApp SnapMirror technology, which ensures efficient data transfer by sending only changed blocks in a compressed format. The feature is supported in all Azure NetApp Files regions with [availability zones](../reliability/regions-list.md). This feature is available with both [cross-zone replication](cross-zone-replication-introduction.md) and [cross-zone replication](cross-region-replication-introduction.md).
+
 ## April 2025
 
 * [New volume usage metrics:](azure-netapp-files-metrics.md#volumes) Volume Inodes Quota, Volume Inodes Total, Volume Inodes Used