Merge pull request #53528 from JustPies/jpzoneterms-2-18-2

551033 Remediate availability zone terminology

Author: v-regandowner

learn-pr/advocates/architect-scalable-ai-agent-solutions/includes/4-design-principles.md

@@ -241,7 +241,7 @@ Reducing unnecessary data movement is a direct lever for cost savings.
 - **Optimize replication and backup strategies.**
   - Evaluate whether cross-region replication is necessary for all
   workloads.
-  - Use zonal redundancy when regional replication isn't required.
+  - Use zone redundancy when regional replication isn't required.
   - Apply compression and deduplication to reduce replication volume.
 
 ### Data management best practices

learn-pr/azure/azure-well-architected-reliability/includes/6-keep-it-simple.md

@@ -60,4 +60,4 @@ This approach saves development time and relies on proven practices used in simi
 
 - During the initial migration to App Service, the team removes all custom instrumentation code by using Application Insights autoinstrumentation.
 
-- They also take advantage of other App Service functions like autoscaling, Azure Key Vault integration, and zonal redundancy.
+- They also take advantage of other App Service functions like autoscaling, Azure Key Vault integration, and zone redundancy.

learn-pr/azure/protect-virtual-machines-with-azure-backup/includes/5-restore-virtual-machine-data.md

@@ -13,7 +13,7 @@ Azure Backup provides many ways to restore a VM. As explained earlier, you can e
 |**Replace existing**    |   You can restore a disk and use it to replace a disk on the existing VM. Azure Backup takes a snapshot of the existing VM before replacing the disk and stores it in the staging location you specify. Existing disks connected to the VM are replaced with the selected restore point. The current VM must exist. You can't use this option if the VM is deleted.      |
 |**Cross region (secondary region)**   |   Cross region restore can be used to restore Azure VMs in the secondary region, which is an Azure paired region.<br> This feature is available for the following options:<br> <li> Create a VM <li> Restore Disks<br> We don't currently support the Replace existing disks option. |
 | **Cross Subscription Restore** | Backup Admins and App admins can perform the restore operation on secondary regions. <br> Cross Subscription Restore: <br><br> - 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 role-based access control capabilities from restore points. <br> - Allowed only if the Cross Subscription Restore property is enabled for your Recovery Services vault. <br> - Works with Cross Region Restore and Cross Zonal Restore. <br> - You can trigger Cross Subscription Restore for managed virtual machines only. <br> - Cross Subscription Restore is supported for Restore with Managed System Identities (MSI). <br> - It's unsupported for snapshots tier recovery points. <br> - It's unsupported for unmanaged VMs and VMs encrypted with Advanced Digital Encryption (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 Role-based access control capabilities) from restore points. When you select a zone to restore, it selects the logical zone (and not the physical zone) as per the Azure subscription you use to restore to. <br> - You can trigger Cross Zonal Restore for managed virtual machines only. <br> - Cross Zonal Restore is supported for Restore with Managed System Identities (MSI). <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. <br> - You can only use Cross Zonal Restore to restore a VM pinned to an Azure zone from a vault with Cross Region Restore (CRR) under these conditions: The secondary region supports zones, or Zone Redundant Storage (ZRS) is enabled. <br> - Cross Zonal Restore is supported from secondary regions. <br> - It's unsupported from snapshots restore point. <br> - It's unsupported for Encrypted Azure VMs. |
+| **Cross Zonal Restore** | Allows you to restore Azure Virtual Machines or disks pinned to any zone to different available zones (as per the Azure Role-based access control capabilities) from restore points. When you select a zone to restore, it selects the logical zone (and not the physical zone) as per the Azure subscription you use to restore to. <br> - You can trigger Cross Zonal Restore for managed virtual machines only. <br> - Cross Zonal Restore is supported for Restore with Managed System Identities (MSI). <br> - Cross Zonal Restore supports restore of an Azure zone pinned/non-zone pinned VM from a vault with Zone-redundant storage (ZRS) enabled. Learn how to set Storage Redundancy. <br> - You can only use Cross Zonal Restore to restore a VM pinned to an Azure zone from a vault with Cross Region Restore (CRR) under these conditions: The secondary region supports zones, or Zone Redundant Storage (ZRS) is enabled. <br> - Cross Zonal Restore is supported from secondary regions. <br> - It's unsupported from snapshots restore point. <br> - It's unsupported for Encrypted Azure VMs. |
 | **Selective disk backup** | Allows you to back up and restore selective VM disks through Enhanced policy. Using this capability, you can selectively back up a subset of the data disks that are attached to your VM. Then, you can restore a subset of the disks that are available in a recovery point, both from instant restore and vault tier. <br><br>  Selective disk backup is useful when you: <br><br> - Manage critical data in a subset of the VM disks. <br> - Use database backup solutions and want to back up only their OS disk to reduce cost. |
 
 ## Recover files from a backup

learn-pr/wwl-azure/implement-high-availability-for-sap-workloads-azure/includes/17-explore-active-active-deployment-scenario.md

@@ -14,7 +14,7 @@ The following considerations apply for this configuration:
 - The Azure virtual network that you deployed to host the SAP system, together with its subnets, is stretched across zones. You don't need separate virtual networks and subnets for each zone.
 - For all virtual machines you deploy, you need to use Azure Managed Disks. Unmanaged disks aren't supported for zonal deployments.
 - Azure Premium Storage, Ultra SSD storage, or ANF don't support any type of storage replication across zones. For DBMS deployments, we rely on database methods to replicate data across zones.
-- For SMB and NFS shares based on Azure Premium Files, zonal redundancy with synchronous replication is offered. The usage of zonal replicated NFS and SMB shares is fully supported with SAP application layer deployments and high availability failover clusters for SAP NetWeaver or SAP S/4HANA centrals services.
+- For SMB and NFS shares based on Azure Premium Files, zone redundancy with synchronous replication is offered. The usage of zone-replicated NFS and SMB shares is fully supported with SAP application layer deployments and high availability failover clusters for SAP NetWeaver or SAP S/4HANA centrals services.
 - The third zone is used to host the SBD device if you build a SUSE Linux Pacemaker cluster and use SBD devices instead of the Azure Fencing Agent.
 - To achieve run time consistency for critical business processes, you can try to direct certain batch jobs and users to application instances that are in-zone with the active DBMS instance by using SAP batch server groups, SAP logon groups, or RFC groups. However, in zonal failover process, you would need to manually move these groups to instances running on virtual machines that are in-zone with the active DB virtual machine.  
 - You might want to deploy dormant dialog instances in each of the zones.

learn-pr/wwl-sci/design-resiliency-strategy-common-cyberthreats-like-ransomware/includes/4-configurations-secure-backup-restore.md

@@ -33,7 +33,7 @@ Consider the following factors when designing BCDR for application workloads:
 
 - Network connectivity if a failover occurs:
   - Bandwidth capacity planning for Azure ExpressRoute.
-  - Traffic routing during a regional, zonal, or network outage.
+  - Traffic routing during a regional, zone, or network outage.
 
 - Planned and unplanned failovers:
   - IP address consistency requirements, and the potential need to maintain IP addresses after failover and failback.