Merge pull request #311738 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-12 18:00 UTC

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

articles/azure-cache-for-redis/cache-how-to-zone-redundancy.md

@@ -96,7 +96,7 @@ Users are allowed to pass this value only for Premium caches and can be passed i
 
 Users are allowed to pass this value only for Premium caches. This is the only value supported in the regions that don't support zones.
 
-- This value can't be passed by user in the request for Standard caches, since they can't explicitly choose for non zonal standard caches.
+- This value can't be passed by user in the request for Standard caches, since they can't explicitly choose for non-zonal standard caches.
 
 It is selected as default option for caches if `ZonalAllocationPolicy` isn't passed in the request in cases:
 
@@ -108,7 +108,7 @@ It is selected as default option for caches if `ZonalAllocationPolicy` isn't pas
 
 > [!IMPORTANT]
 >
-> - Starting with 2024-11-01 API version, Automatic Zonal Allocation is chosen as default option for Premium, Standard caches. In rare cases, when sufficient zonal capacity is unavailable to at-least allocate two zones, and user does not pass `ZonalAllocationPolicy` in the request, Azure will create a non-zonal cache which user can verify by checking the `ZonalAllocationPolicy` property in the response.
+> - Starting with 2024-11-01 API version, Automatic Zonal Allocation is chosen as default option for Premium, Standard caches. In rare cases, when sufficient zone capacity is unavailable to at-least allocate two zones, and user does not pass `ZonalAllocationPolicy` in the request, Azure will create a non-zonal cache which user can verify by checking the `ZonalAllocationPolicy` property in the response.
 >   - Hence, it is recommended not to pass `ZonalAllocationPolicy` in the request body while creating the cache as it will enable Azure to choose the best option among **Automatic**, **NoZones** for the cache based on the region's zonal supportability and capacity. Otherwise, users can pass `ZonalAllocationPolicy` if they want to explicitly use a specific zonal allocation policy.
 
 > [!IMPORTANT]

articles/azure-netapp-files/azure-netapp-files-service-levels.md

@@ -17,7 +17,7 @@ Service levels are an attribute of a capacity pool. Service levels are defined a
 
 Azure NetApp Files supports five service levels: *Elastic*, *Flexible*, *Standard*, *Premium*, and *Ultra*. 
 
-The Flexible, Standard, Premium, and Ultra service levels deliver in‑Azure bare‑metal flash performance. The Elastic service level runs on Azure infrastructure and provides built‑in zonal redundancy with low single‑digit millisecond latency.
+The Flexible, Standard, Premium, and Ultra service levels deliver in‑Azure bare‑metal flash performance. The Elastic service level runs on Azure infrastructure and provides built‑in zone redundancy with low single‑digit millisecond latency.
 
 * **Elastic service level (preview)**:
     Elastic is an advanced, high-availability service level designed to deliver continuous data access with zero data loss even if an entire Azure Availability Zone becomes unavailable. This service eliminates single points of failure, making it ideal for mission-critical workloads that require uncompromising resilience and in-region data protection.

articles/azure-netapp-files/create-cross-zone-replication.md

@@ -12,7 +12,7 @@ ms.custom: sfi-image-nochange
 ---
 # Create cross-zone replication relationships for Azure NetApp Files
 
-[Cross-zone replication](replication.md#cross-zone-replication) enables you to replicate volumes across availability zones within the same region. It enables you to fail over your critical application if a zonal outage or disaster occurs. 
+[Cross-zone replication](replication.md#cross-zone-replication) enables you to replicate volumes across availability zones within the same region. It enables you to fail over your critical application if a zone outage or disaster occurs. 
 
 For information about availability zones, see [Use availability zone volume placement for application high availability with Azure NetApp Files](replication.md#availability-zones) and [Manage availability zone volume placement for Azure NetApp Files](manage-availability-zone-volume-placement.md). 
 

articles/azure-netapp-files/elastic-capacity-pool-task.md

@@ -32,8 +32,8 @@ The maximum performance achieved will depend on the dataset and workload charact
 * Creating and resizing a capacity pool can be a long-running operation. On average, creating a pool takes 5-7 minutes, but can take longer. 
 * Manually changing the zone of a capacity pool can be a long-running operation. 
 * When creating capacity pools, you must designate the failover order for three zones. The order can't be changed after creating the capacity pools.
-    * Capacity pools automatically fail over if a zonal outage occurs. You can also manually fail over.  
-    * If a zonal outage occurs, capacity pools don't automatically fail back. You can manually perform a fail back. For more information, see [Change the availability zone of an Elastic capacity pool](elastic-capacity-pool-task.md).
+    * Capacity pools automatically fail over if a zone outage occurs. You can also manually fail over.  
+    * If a zone outage occurs, capacity pools don't automatically fail back. You can manually perform a fail back. For more information, see [Change the availability zone of an Elastic capacity pool](elastic-capacity-pool-task.md).
 * Volumes in zone-redundant storage capacity pools can't be moved out of the capacity pool they're created in. 
 * Review the [maximum and minimum sizes](azure-netapp-files-resource-limits.md) for Elastic zone-redundant storage. 
 * When resizing capacity pools: 

articles/azure-netapp-files/elastic-change-zones.md

@@ -13,7 +13,7 @@ ms.author: anfdocs
 With Elastic zone-redundant storage, you can easily change the availability zone of a capacity pool and its volumes based on needs, for example co-locating storage in the same availability zone to reduce latency.
 
 >[!NOTE]
->Capacity pools fail over to a new zone automatically in the event of a zonal outage. 
+>Capacity pools fail over to a new zone automatically in the event of a zone outage. 
 
 ## Considerations
 

articles/backup/azure-elastic-san-backup-overview.md

@@ -25,7 +25,7 @@ Elastic SAN backup includes the following key features:
 
 - **Region availability**: The feature is currently [available in specific regions](azure-elastic-storage-area-network-backup-support-matrix.md#supported-regions) only. 
 - **Snapshot export**: Exports the selected Elastic SAN to an independent managed disk incremental snapshot (operational tier) at a given point in time.
-- **Storage and resiliency**: Managed Disk incremental snapshot can be stored in Zonally redundant storage (ZRS) or Locally redundant storage (LRS) resiliency (in supported regions), independent of the Elastic SAN lifecycle.
+- **Storage and resiliency**: Managed Disk incremental snapshot can be stored in zone-redundant storage (ZRS) or Locally redundant storage (LRS) resiliency (in supported regions), independent of the Elastic SAN lifecycle.
 
    > [!NOTE]
    > ZRS snapshot storage applies only to new Backup instances created in regions that support ZRS, and only when no managed disk incremental snapshot is already exported from the volume snapshot. In these scenarios, snapshots are stored in ZRS by default. Existing Backup instances and regions that don't support ZRS continue to store snapshots as LRS.

articles/backup/backup-azure-arm-restore-vms.md

@@ -23,7 +23,7 @@ Azure Backup provides several ways to restore a VM.
 **Restore disk** | Restores a VM disk, which can then be used to create a new VM.<br/><br/> Azure Backup provides a template to help you customize and create a VM. <br/><br> The restore job generates a template that you can download and use to specify custom VM settings, and create a VM.<br/><br/> The disks are copied to the Resource Group you specify.<br/><br/> Alternatively, you can attach the disk to an existing VM, or create a new VM using PowerShell.<br/><br/> This option is useful if you want to customize the VM, add configuration settings that weren't there at the time of backup, or add settings that must be configured using the template or PowerShell.
 **Replace existing** | You can restore a disk, and use it to replace a disk on the existing VM.<br/><br/> The current VM must exist. If it's been deleted, this option can't be used.<br/><br/> Azure Backup takes a snapshot of the existing VM before replacing the disk. The snapshot is copied to the vault and retained in accordance with the retention policy.　<br/><br/> When you choose a Vault-Standard recovery point, a VHD file with the content of the chosen recovery point is also created in the staging location you specify. Existing disks connected to the VM are replaced with the selected restore point. <br/><br/> After the disk replacement operation is complete, the original disk is retained in the resource group. You can choose to manually delete the original disks if they aren't needed. <br/><br/>Replace existing is supported for unencrypted managed VMs, including VMs [created using custom images](/azure/virtual-machines/windows/tutorial-custom-images). It's unsupported for classic VMs, unmanaged VMs, and [generalized VMs](/azure/virtual-machines/windows/upload-generalized-managed).<br/><br/> If the restore point has more or less disks than the current VM, then the number of disks in the restore point will only reflect the VM configuration.<br><br> Replace existing is also supported for VMs with linked resources, like [user-assigned managed-identity](../active-directory/managed-identities-azure-resources/overview.md) or [Key Vault](/azure/key-vault/general/overview).
 **Cross Region (secondary region)** | Cross Region restore can be used to restore Azure VMs in the secondary region, which is an [Azure paired region](../availability-zones/cross-region-replication-azure.md).<br><br> You can restore all the Azure VMs for the selected recovery point if the backup is done in the secondary region.<br><br> During the backup, snapshots aren't replicated to the secondary region. Only the data stored in the vault is replicated. So secondary region restores are only [vault tier](about-azure-vm-restore.md#key-concepts-for-azure-vm-restore) restores. The restore time for the secondary region will be almost the same as the vault tier restore time for the primary region.  <br><br> This feature is available for the options below:<br><br> - [Create a VM](#create-a-vm) <br> - [Restore Disks](#restore-disks) <br><br> If the source machine has more than 16 disks, VHDs won't be created in Cross Region Restore. <br><br> We don't currently support the [Replace existing disks](#replace-existing-disks) option.<br><br> Permissions<br> The restore operation on secondary region can be performed by Backup Admins and App admins.
-**Cross Subscription Restore** | Allows you to restore Azure Virtual Machines or disks to a different subscription within the same tenant as the source subscription (as per the Azure RBAC capabilities) from restore points.  <br><br> Additionally, Cross Zone Restore supports restoring Azure non-zone pinned VMs from a Recovery Services vault configured with Zonal-Redundant Storage (ZRS), enabling enhanced resiliency and flexibility in disaster recovery scenarios.  <br><br> Allowed only if the [Cross Subscription Restore property](backup-azure-arm-restore-vms.md#cross-subscription-restore-for-azure-vm) is enabled for your Recovery Services vault.  <br><br>  Works with [Cross Region Restore](backup-azure-arm-restore-vms.md#cross-region-restore) and [Cross Zonal Restore](backup-azure-arm-restore-vms.md#create-a-vm).   <br><br>   You can trigger Cross Subscription Restore for managed virtual machines only. <br><br> Cross Subscription Restore is supported for [Restore with Managed System Identities (MSI)](backup-azure-arm-restore-vms.md#restore-vms-with-managed-identities). <br><br> It's unsupported for [snapshots tier](backup-azure-vms-introduction.md#snapshot-creation) recovery points. <br><br>  It's unsupported for [unmanaged VMs](#restoring-unmanaged-vms-and-disks-as-managed) and [ADE encrypted VMs](backup-azure-vms-encryption.md#encryption-support-by-using-ade).
+**Cross Subscription Restore** | Allows you to restore Azure Virtual Machines or disks to a different subscription within the same tenant as the source subscription (as per the Azure RBAC capabilities) from restore points.  <br><br> Additionally, Cross Zone Restore supports restoring Azure non-zone pinned VMs from a Recovery Services vault configured with Zone-Redundant Storage (ZRS), enabling enhanced resiliency and flexibility in disaster recovery scenarios.  <br><br> Allowed only if the [Cross Subscription Restore property](backup-azure-arm-restore-vms.md#cross-subscription-restore-for-azure-vm) is enabled for your Recovery Services vault.  <br><br>  Works with [Cross Region Restore](backup-azure-arm-restore-vms.md#cross-region-restore) and [Cross Zonal Restore](backup-azure-arm-restore-vms.md#create-a-vm).   <br><br>   You can trigger Cross Subscription Restore for managed virtual machines only. <br><br> Cross Subscription Restore is supported for [Restore with Managed System Identities (MSI)](backup-azure-arm-restore-vms.md#restore-vms-with-managed-identities). <br><br> It's unsupported for [snapshots tier](backup-azure-vms-introduction.md#snapshot-creation) recovery points. <br><br>  It's unsupported for [unmanaged VMs](#restoring-unmanaged-vms-and-disks-as-managed) and [ADE encrypted VMs](backup-azure-vms-encryption.md#encryption-support-by-using-ade).
 **Cross Zonal Restore** |	Allows you to restore Azure Virtual Machines or disks pinned to any zone to different available zones (as per the Azure RBAC capabilities) from restore points. Note that when you select a zone to restore, it selects the [logical zone](/azure/reliability/availability-zones-overview#zonal-and-zone-redundant-services) (and not the physical zone) as per the Azure subscription you will use to restore to.           <br><br> You can trigger Cross Zonal Restore for managed virtual machines only. <br><br> Cross Zonal Restore is supported for [Restore with Managed System Identities (MSI)](#restore-vms-with-managed-identities). <br><br> Cross Zonal Restore supports restore of an Azure zone pinned/non-zone pinned VM from a vault with Zonal-redundant storage (ZRS) enabled. Learn [how to set Storage Redundancy](backup-create-rs-vault.md#set-storage-redundancy). <br><br> It's supported to restore an Azure zone pinned VM only from a [vault with Cross Region Restore (CRR)](backup-create-rs-vault.md#set-storage-redundancy) (if the secondary region supports zones) or Zone Redundant Storage (ZRS) enabled. <br><br> Cross Zonal Restore is supported from [secondary regions](#restore-in-secondary-region). <br><br> It's unsupported from [snapshots](backup-azure-vms-introduction.md#snapshot-creation) restore point. <br><br> It's unsupported for [Encrypted Azure VMs](backup-azure-vms-introduction.md#encryption-of-azure-vm-backups).
 
 >[!Tip]
@@ -268,7 +268,7 @@ Currently, secondary region [RPO](azure-backup-glossary.md#recovery-point-object
 
 [Azure zone pinned VMs](/azure/virtual-machines/windows/create-portal-availability-zone) can be restored in any [availability zones](/azure/reliability/availability-zones-overview) of the same region.
 
-In the restore process, you'll see the option **Availability Zone.** You'll see your default zone first. To choose a different zone, choose the number of the zone of your choice. If the pinned zone is unavailable, you won't be able to restore the data to another zone because the backed-up data isn't zonally replicated. The restore in availability zones is possible from recovery points in vault tier only.
+In the restore process, you'll see the option **Availability Zone.** You'll see your default zone first. To choose a different zone, choose the number of the zone of your choice. If the pinned zone is unavailable, you won't be able to restore the data to another zone because the backed-up data isn't replicated across zones. The restore in availability zones is possible from recovery points in vault tier only.
 
 In summary, the **Availability Zone** will only appear when
  - The source VM is zone pinned and is NOT encrypted

articles/backup/backup-azure-database-postgresql-flex-use-rest-api.md

@@ -4,7 +4,7 @@ description: Learn how to back up Azure Database for PostgreSQL - Flexible serve
 ms.topic: concept-article
 ms.custom:
   - ignite-2024
-ms.date: 02/28/2025
+ms.date: 02/12/2026
 ms.assetid: 759ee63f-148b-464c-bfc4-c9e640b7da6b
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -18,11 +18,14 @@ This article describes how to back up Azure Database for PostgreSQL - Flexible S
 For information on the Azure PostgreSQL - Flexible server backup supported scenarios, limitations, and authentication mechanisms, see the [overview document](backup-azure-database-postgresql-flex-overview.md).
 
 ## Prerequisites
+
+Before configuring backup for Azure PostgreSQL - Flexible servers, ensure that the following prerequisites are met:
+
 - [Create a Backup vault](backup-azure-dataprotection-use-rest-api-create-update-backup-vault.md)
 - [Create a PostgreSQL flexible server backup policy](backup-azure-database-postgresql-flex-use-rest-api-create-update-policy.md).
 
 
-## Configure backup
+## Configure backup for PostgreSQL - Flexible servers
 
 Once the vault and policy are created, there're three critical points to consider for an Azure PostgreSQL - Flexible servers protection.
 
@@ -293,7 +296,7 @@ GET https://management.azure.com/subscriptions/00001111-aaaa-2222-bbbb-3333cccc4
 
 ```
 
-## Configure backup request
+## Configure backup request for PostgreSQL - Flexible servers
 
 Once the request is validated, you can submit the same to the [create backup instance API](/rest/api/dataprotection/backup-instances/create-or-update). One of the Azure Backup data protection services protects the Backup instance within the Backup vault. Here, the Azure PostgreSQL flexible server is the backup instance. Use the above-validated request body with minor additions.
 
@@ -448,7 +451,7 @@ Once the operation completes, it returns 200 (OK) with the success message in th
 
 ```
 
-## Stop protection and delete data
+## Stop protection and delete data for PostgreSQL - Flexible servers
 
 To remove the protection on an Azure PostgreSQL database and delete the backup data as well, perform a [delete operation](/rest/api/dataprotection/backup-instances/delete).
 

articles/backup/backup-azure-recovery-services-vault-overview.md

@@ -40,7 +40,7 @@ A Recovery Services vault is an entity that stores the backups and recovery poin
 
 - Azure Backup automatically handles storage for the vault. See how [storage settings can be changed](./backup-create-rs-vault.md#set-storage-redundancy).
 
-- To learn more about storage redundancy, see these articles on [geo](../storage/common/storage-redundancy.md#geo-zone-redundant-storage), [local](../storage/common/storage-redundancy.md#locally-redundant-storage) and [zonal](../storage/common/storage-redundancy.md#zone-redundant-storage) redundancy.
+- To learn more about storage redundancy, see these articles on [geo](../storage/common/storage-redundancy.md#geo-zone-redundant-storage), [local](../storage/common/storage-redundancy.md#locally-redundant-storage) and [zone](../storage/common/storage-redundancy.md#zone-redundant-storage) redundancy.
 
 ## Encryption settings in the Recovery Services vault