Merge pull request #304535 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-21 17:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-netapp-files/includes/region-pairs.md

@@ -9,7 +9,7 @@ ms.custom: include file, references_regions
 # azure-netapp-files/replication.md
 # Customer intent: As a cloud architect, I want to understand Azure NetApp Files volume replication across different regional pairs, so that I can plan and implement resilient data storage solutions for multi-region applications.
 ---
-Azure NetApp Files volume replication is supported between various [Azure regional pairs](../../reliability/cross-region-replication-azure.md#azure-paired-regions) and non-standard pairs. Azure NetApp Files volume replication is currently available between the following regions. You can replicate Azure NetApp Files volumes from Regional Pair A to Regional Pair B, and vice versa.  
+Azure NetApp Files volume replication is supported between various [Azure regional pairs](../../reliability/cross-region-replication-azure.md#paired-regions) and nonstandard pairs. Azure NetApp Files volume replication is currently available between the following regions. You can replicate Azure NetApp Files volumes from Regional Pair A to Regional Pair B and from Regional Pair B to Regional Pair A.
 
 ### Azure regional pairs
 
@@ -38,7 +38,7 @@ Azure NetApp Files volume replication is supported between various [Azure region
 | US Government | US Gov Arizona | US Gov Texas |
 | US Government | US Gov Virginia | US Gov Texas |
 
-### Azure regional non-standard pairs
+### Azure regional nonstandard pairs
 
 | Geography | Regional Pair A | Regional Pair B  |
 |:--- |:--- |:--- |
@@ -68,5 +68,5 @@ Azure NetApp Files volume replication is supported between various [Azure region
 | UK/Europe | UK South | North Europe |
 | US Government | US Gov Arizona | US Gov Virginia |
 
->[!NOTE]
->There can be a discrepancy in the size and number of snapshots between source and destination. This discrepancy is expected. Snapshot policies and replication schedules will influence the number of snapshots. Snapshot policies and replication schedules, combined with the amount of data changed between snapshots, will influence the size of snapshots. To learn more about snapshots, refer to [How Azure NetApp Files snapshots work](../snapshots-introduction.md).
+> [!NOTE]
+> There can be a discrepancy in the size and number of snapshots between the source and the destination. This discrepancy is expected. Snapshot policies and replication schedules influence the number of snapshots. Snapshot policies and replication schedules, combined with the amount of data that changes between snapshots, influence the size of snapshots. For more information, see [How Azure NetApp Files snapshots work](../snapshots-introduction.md).

articles/azure-netapp-files/manage-availability-zone-volume-placement.md

@@ -19,7 +19,7 @@ You can deploy new volumes in the logical availability zone of your choice. You
 >[!IMPORTANT]
 >If you're using availability zones with custom roles or the built-in Contributor RBAC role, ensure you have the appropriate permissions set. Not having certain permissions can cause issues in the Azure portal. For configuration details, see [Configure custom RBAC roles](#configure-custom-rbac-roles).
 
-* This feature doesn't guarantee free capacity in the availability zone. For example, even if you can deploy a VM in availability zone 3 of the East US region, it doesn’t guarantee free Azure NetApp Files capacity in that zone. If no sufficient capacity is available, volume creation will fail.
+* This feature doesn't guarantee free capacity in the availability zone. For example, even if you can deploy a VM in availability zone 3 of the East US region, it doesn’t guarantee free Azure NetApp Files capacity in that zone. If no sufficient capacity is available, volume creation fails.
 
 * After a volume is created with an availability zone, the specified availability zone can’t be modified. Volumes can’t be moved between availability zones.
 
@@ -33,8 +33,8 @@ You can deploy new volumes in the logical availability zone of your choice. You
 
 * <a name="file-path-uniqueness"></a> For volumes in different availability zones, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol). 
 
->[!IMPORTANT]
->It's not recommended that you use availability zones for Terraform-managed volumes. If you do, you must [add the zone property to your volume](#populate-availability-zone-for-terraform-managed-volumes).
+> [!IMPORTANT]
+> We don't recommend that you use availability zones for Terraform-managed volumes. If you do, you must [add the zone property to your volume](#populate-availability-zone-for-terraform-managed-volumes).
 
 ## Create a volume with an availability zone 
 
@@ -45,7 +45,7 @@ You can deploy new volumes in the logical availability zone of your choice. You
     * [Create an SMB volume](azure-netapp-files-create-volumes-smb.md)      
     * [Create a dual-protocol volume](create-volumes-dual-protocol.md)    
 
-2.	In the **Create a Volume** page, under the **Basic** tab, select the **Availability Zone** dropdown to specify an availability zone where Azure NetApp Files resources are present.   
+2.	In the **Create a Volume** page, under the **Basic** tab, select the **Availability Zone** dropdown menu to specify an availability zone where Azure NetApp Files resources are present.   
 
     > [!IMPORTANT]
     > Logical availability zones for the subscription without Azure NetApp Files presence are marked `(Unavailable)` and are greyed out.
@@ -75,7 +75,7 @@ You can deploy new volumes in the logical availability zone of your choice. You
 
 ## Populate availability zone for Terraform-managed volumes
 
-The populate availability zone features requires a `zone` property on the volume. You can set the zone property only when you create the Terraform-managed volume, but you can't modify it after the volume has been created. Adding the `zone` property after the volume has been created can cause data loss or loss of the volume if the specified zone value does not match the availability zone. 
+The populate availability zone features requires a `zone` property on the volume. You can set the zone property only when you create the Terraform-managed volume, but you can't modify the property after you create the volume. Adding the `zone` property after you create the volume can cause data loss or loss of the volume if the specified zone value doesn't match the availability zone. 
 
 >[!IMPORTANT]
 >To prevent data loss on any Azure resource that includes volatile resources, you should use the [`prevent_destroy` lifecycle argument](https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle#prevent_destroy).
@@ -142,7 +142,7 @@ If you're using a custom RBAC role or the [built-in Contributor role](../role-ba
     ```
 
 1. Select **Review + update**.
-1. Sign out of your Azure account, then log back in to confirm permissions effect has taken hold and the options are visible. 
+1. Sign out of your Azure account, and then log back in to confirm that the permissions are in effect and the options are visible.
 
 ## Next steps