Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into update-openai

Author: bandersmsft

articles/azure-netapp-files/snapshots-delete.md

@@ -5,33 +5,33 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 03/16/2024
+ms.date: 08/30/2024
 ms.author: anfdocs
 ---
 
 # Delete snapshots using Azure NetApp Files 
 
-You can delete snapshots that you no longer need to keep. 
+You can delete snapshots that you no longer need. 
 
 > [!IMPORTANT]
-> The snapshot deletion operation cannot be undone. A deleted snapshot cannot be recovered. 
+> You can't undo the snapshot deletion. You can't recover a deleted snapshot. 
 
 ## Considerations 
 
-* You can't delete a snapshot if it is part of an active file-restore operation or if it is in the process of being cloned.
+* You can't delete a snapshot if it's part of an active file-restore operation or if it's in the process of being cloned.
 * You can't delete a replication generated snapshot that is used for volume baseline data replication.
 
 ## Steps
 
-1. Go to the **Snapshots** menu of a volume. Right-click the snapshot you want to delete. Select **Delete**.
+1. Go to the **Snapshots** menu of a volume. Select the three dots at the end of the row of the snapshot want to delete. Select **Delete**.
 
-    ![Screenshot that describes the right-click menu of a snapshot](./media/shared/snapshot-right-click-menu.png) 
+    ![Screenshot illustrating the Snapshot overview menu.](./media/shared/snapshot-right-click-menu.png) 
 
-2. In the Delete Snapshot window, confirm that you want to delete the snapshot by clicking **Yes**. 
+2. In the Delete Snapshot window, confirm that you want to delete the snapshot by selecting **Yes**. 
 
-    ![Screenshot that confirms snapshot deletion](./media/snapshots-delete/snapshot-confirm-delete.png)  
+    ![Screenshot showing confirmed snapshot deletion.](./media/snapshots-delete/snapshot-confirm-delete.png)  
 
 ## Next steps
 
 * [Learn more about snapshots](snapshots-introduction.md)
-* [Azure NetApp Files Snapshot Overview](https://anfcommunity.com/2021/01/31/azure-netapp-files-snapshot-overview/)
+* [Azure NetApp Files snapshot overview](https://anfcommunity.com/2021/01/31/azure-netapp-files-snapshot-overview/)

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

@@ -40,12 +40,11 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * Availability zone volume placement enhancement - [**Populate existing volumes**](manage-availability-zone-volume-placement.md#populate-an-existing-volume-with-availability-zone-information) is now generally available (GA).
 
-
 * [Cross-zone replication](cross-zone-replication-introduction.md) is now generally available (GA).
 
     Cross-zone replication allows you to replicate your Azure NetApp Files volumes asynchronously from one Azure availability zone (AZ) to another within the same region. Using technology similar to the cross-region replication feature and Azure NetApp Files availability zone volume placement feature, cross-zone replication replicates data in-region across different zones; only changed blocks are sent over the network in a compressed, efficient format. It helps you protect your data from unforeseeable zone failures without the need for host-based data replication. This feature minimizes the amount of data required to replicate across the zones, limiting data transfers required and shortens the replication time so you can achieve a smaller Restore Point Objective (RPO). Cross-zone replication doesn’t involve any network transfer costs and is highly cost-effective. 
 
-    Cross-zone replication is available in all [AZ-enabled regions](../availability-zones/az-overview.md#azure-regions-with-availability-zones) with [Azure NetApp Files presence](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=netapp&regions=all&rar=true).
+    Cross-zone replication is available in all [AZ-enabled regions](../reliability/availability-zones-service-support.md) with [Azure NetApp Files presence](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=netapp&regions=all&rar=true).
 
 * [Transition a volume to customer-managed keys](configure-customer-managed-keys.md#transition) (Preview)
 
@@ -278,7 +277,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
     This feature is now in public preview, currently available in [16 Azure regions](azure-netapp-files-network-topologies.md). It will roll out to other regions. Stay tuned for further information as more regions become available.
 
-* [Azure Application Consistent Snapshot tool (AzAcSnap) 8 (GA)](azacsnap-introduction.md)
+* [Azure Application Consistent Snapshot tool (AzAcSnap) 8](azacsnap-introduction.md) is now generally available (GA)
 
     Version 8 of the AzAcSnap tool is now generally available. [Azure Application Consistent Snapshot Tool](azacsnap-introduction.md) (AzAcSnap) is a command-line tool that enables you to simplify data protection for third-party databases in Linux environments. AzAcSnap 8 introduces the following new capabilities and improvements:
 
@@ -293,7 +292,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * [Troubleshooting enhancement: break file locks](troubleshoot-file-locks.md)
 
-    In some cases you may encounter (stale) file locks on NFS, SMB, or dual-protocol volumes that need to be cleared. With this new Azure NetApp Files feature, you can now break these locks. You can break file locks for all files in a volume or break all file locks initiated by a specified client.
+    You might sometimes encounter stale file locks on NFS, SMB, or dual-protocol volumes that need to be cleared. With this new Azure NetApp Files feature, you can now break these locks. You can break file locks for all files in a volume or break all file locks initiated by a specified client.
 
 ## April 2023
 
@@ -500,7 +499,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * [Single-file snapshot restore](snapshots-restore-file-single.md) (Preview)
 
-    Azure NetApp Files provides ways to quickly restore data from snapshots (mainly at the volume level). See [How Azure NetApp Files snapshots work](snapshots-introduction.md). Options for user file self-restore are available via client-side data copy from the `~snapshot` (Windows) or `.snapshot` (Linux) folders. These operations require data (files and directories) to traverse the network twice (upon read and write). As such, the operations aren't time and resource efficient, especially with large data sets. If you don't want to restore the entire snapshot to a new volume, revert a volume, or copy large files across the network, you can use the single-file snapshot restore feature to restore individual files directly on the service from a volume snapshot without requiring data copy via an external client. This approach drastically reduces RTO and network resource usage when restoring large files.
+    Azure NetApp Files provides ways to quickly restore data from snapshots (mainly at the volume level). See [How Azure NetApp Files snapshots work](snapshots-introduction.md). Options for user file self-restore are available via client-side data copy from the `~snapshot` (Windows) or `.snapshot` (Linux) folders. These operations require data (files and directories) to traverse the network twice (upon read and write). As such, the operations aren't time and resource efficient, especially with large data sets. If you don't want to restore the entire snapshot to a new volume, revert a volume, or copy large files across the network, you can use the single-file snapshot restore feature to restore individual files directly on the service from a volume snapshot without requiring data copy via an external client. This approach drastically reduces recovery time objective (RTO) and network resource usage when restoring large files.
 
 * Features that are now generally available (GA)
 
@@ -541,7 +540,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * [Azure NetApp Files backup](backup-introduction.md) (Preview)
 
-    Azure NetApp Files online snapshots now support backup of snapshots. With this new backup capability, you can vault your Azure NetApp Files snapshots to cost-efficient and ZRS-enabled Azure storage in a fast and cost-effective way. This approach further protects your data from accidental deletion.
+    Azure NetApp Files online snapshots now support backup of snapshots. With this new backup capability, you can vault your Azure NetApp Files snapshots to cost-efficient and zone redundant Azure storage in a fast and cost-effective way. This approach further protects your data from accidental deletion.
 
     Azure NetApp Files backup extends ONTAP's built-in snapshot technology. When snapshots are vaulted to Azure storage, only changed blocks relative to previously vaulted snapshots are copied and stored, in an efficient format. Vaulted snapshots are still represented in full. You can restore them to a new volume individually and directly, eliminating the need for an iterative, full-incremental recovery process. This advanced technology minimizes the amount of data required to store to and retrieve from Azure storage, therefore saving data transfer and storage costs. It also shortens the backup vaulting time, so you can achieve a smaller Restore Point Objective (RPO). You can keep a minimum number of snapshots online on the Azure NetApp Files service for the most immediate, near-instantaneous data-recovery needs. In doing so, you can build up a longer history of snapshots at a lower cost for long-term retention in the Azure NetApp Files backup vault.
 
@@ -696,7 +695,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * [AES encryption for AD authentication](create-active-directory-connections.md#create-an-active-directory-connection) (Preview)
 
-    Azure NetApp Files now supports AES encryption on LDAP connection to DC to enable AES encryption for an SMB volume. This feature is currently in preview.
+    Azure NetApp Files now supports AES encryption on LDAP connections to domain controllers (DC) to enable AES encryption for an SMB volume. This feature is currently in preview.
 
 * New [metrics](azure-netapp-files-metrics.md):
 

articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md

@@ -12,6 +12,8 @@ This article describes the steps to move App Service resources between resource
 
 If you want to move App Services to a new region, see [Move an App Service resource to another region](../../../app-service/manage-move-across-regions.md).
 
+You can move App Service resources to a new resource group or subscription but you need to delete and upload its TLS/SSL certificates to the new resource group or subscription. Also, you can't move a free App Service managed certificate. For that scenario, see [Move with free managed certificates](#move-with-free-managed-certificates).
+
 ## Move across subscriptions
 
 When you move a Web App across subscriptions, the following guidance applies:
@@ -26,7 +28,6 @@ When you move a Web App across subscriptions, the following guidance applies:
 - App Service Environments can't be moved to a new resource group or subscription.
     - You can move a Web App and App Service plan hosted on an App Service Environment to a new subscription without moving the App Service Environment. The Web App and App Service plan that you move will always be associated with your initial App Service Environment. You can't move a Web App/App Service plan to a different App Service Environment.
     - If you need to move a Web App and App Service plan to a new App Service Environment, you'll need to recreate these resources in your new App Service Environment. Consider using the [backup and restore feature](../../../app-service/manage-backup.md) as way of recreating your resources in a different App Service Environment.
-- You can move a certificate bound to a web without deleting the TLS bindings, as long as the certificate is moved with all other resources in the resource group. However, you can't move a free App Service managed certificate. For that scenario, see [Move with free managed certificates](#move-with-free-managed-certificates).
 - App Service apps with private endpoints cannot be moved. Delete the private endpoint(s) and recreate it after the move.
 - App Service apps with virtual network integration cannot be moved. Remove the virtual network integration and reconnect it after the move.
 - App Service resources can only be moved from the resource group in which they were originally created. If an App Service resource is no longer in its original resource group, move it back to its original resource group. Then, move the resource across subscriptions. For help with finding the original resource group, see the next section.

articles/load-balancer/load-balancer-nat-pool-migration.md

@@ -139,7 +139,7 @@ $slb | Set-AzLoadBalancer
 
 ## Migration with automation script for Virtual Machine Scale Set 
 
-
+The migration process will reuse existing backend pools with membership matching the NAT Pools to be migrated; if no matching backend pool is found, the script will exit (without making changes). Alternatively, use the  `-backendPoolReuseStrategy` parameter to either always create new backend pools (`NoReuse`) or create a new backend pool if a matching one doesn't exist (`OptionalFirstMatch`). Backend pools and NAT Rule associations can be updated post migration to match your preference.
 ### Prerequisites
 
 Before beginning the migration process, ensure the following prerequisites are met:

articles/migrate/migrate-support-matrix-physical.md

@@ -87,7 +87,7 @@ For Linux servers, based on the features you want to perform, you can create a u
     Operating system | Versions
     --- | ---
     Red Hat Enterprise Linux | 5.1, 5.3, 5.11, 6.x, 7.x, 8.x, 9.x
-    Ubuntu | 12.04, 14.04, 16.04, 18.04, 20.04
+    Ubuntu | 12.04, 14.04, 16.04, 18.04, 20.04, 22.04
     Oracle Linux | 6.1, 6.7, 6.8, 6.9, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 8, 8.1, 8.3, 8.5
     SUSE Linux | 10, 11 SP4, 12 SP1, 12 SP2, 12 SP3, 12 SP4, 15 SP2, 15 SP3
     Debian | 7, 8, 9, 10, 11

articles/migrate/vmware/migrate-support-matrix-vmware.md

@@ -334,7 +334,7 @@ Support | Details
 --- | ---
 Supported servers | You can enable agentless dependency analysis on up to 1,000 servers (across multiple vCenter Servers) discovered per appliance.
 Windows servers | Windows Server 2022 <br/> Windows Server 2019<br /> Windows Server 2016<br /> Windows Server 2012 R2<br /> Windows Server 2012<br /> Windows Server 2008 R2 (64-bit)<br /> Windows Server 2008 (32-bit)
-Linux servers | Red Hat Enterprise Linux 5.1, 5.3, 5.11, 6.x, 7.x, 8.x <br /> Ubuntu 12.04, 14.04, 16.04, 18.04, 20.04 <br /> OracleLinux 6.1, 6.7, 6.8, 6.9, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 8, 8.1, 8.3, 8.5 <br /> SUSE Linux 10, 11 SP4, 12 SP1, 12 SP2, 12 SP3, 12 SP4, 15 SP2, 15 SP3 <br /> Debian 7, 8, 9, 10, 11
+Linux servers | Red Hat Enterprise Linux 5.1, 5.3, 5.11, 6.x, 7.x, 8.x <br /> Ubuntu 12.04, 14.04, 16.04, 18.04, 20.04, 22.04 <br /> OracleLinux 6.1, 6.7, 6.8, 6.9, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 8, 8.1, 8.3, 8.5 <br /> SUSE Linux 10, 11 SP4, 12 SP1, 12 SP2, 12 SP3, 12 SP4, 15 SP2, 15 SP3 <br /> Debian 7, 8, 9, 10, 11
 Server requirements | VMware Tools (10.2.1 and later) must be installed and running on servers you want to analyze.<br /><br /> Servers must have PowerShell version 2.0 or later installed.<br /><br /> WMI should be enabled and available on Windows servers.
 vCenter Server account | The read-only account used by Azure Migrate and Modernize for assessment must have privileges for guest operations on VMware VMs.
 Windows server access |  A user account (local or domain) with administrator permissions on servers.

articles/operator-service-manager/TOC.yml

@@ -35,6 +35,9 @@
     items:
       - name: Get Started with Safe Upgrade Practices
         href: safe-upgrade-practices.md
+      - name: Control rollback behavior on upgrade failure 
+
+        href: safe-upgrades-nf-level-rollback.md
 - name: Quickstarts
   expanded: false
   items:

articles/operator-service-manager/index.yml

@@ -81,6 +81,18 @@ landingContent:
           - text: Troubleshoot common CLI Issues
             url: troubleshoot-cli-common-issues.md
 
+  # Card
+  - title: Safe Upgrade Practices
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: Get started with safe upgrades
+            url: safe-upgrade-practices.md
+      - linkListType: concept
+        links:
+          - text: Control rollback behavior on upgrade failure
+            url: safe-upgrades-nf-level-rollback.md
+            
   # Card
   - title: Additional Resources
     linkLists: