Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us370875-cli-posh-nat

Author: asudbring

articles/app-service/configure-authentication-file-based.md

@@ -81,7 +81,7 @@ The following exhausts possible configuration options within the file:
             "url_scheme_of_your_app://easyauth.callback"
         ],
         "cookieExpiration": {
-            "convention": "FixedTime|IdentityDerived",
+            "convention": "FixedTime|IdentityProviderDerived",
             "timeToExpiration": "<timespan>"
         },
         "nonce": {

articles/azure-netapp-files/application-volume-group-manage-volumes.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/19/2021
+ms.date: 11/19/2024
 ms.author: anfdocs
 ---
 # Manage volumes in an application volume group for SAP HANA
@@ -14,24 +14,24 @@ You can manage a volume from its volume group. You can resize, delete, or change
 
 ## Steps
 
-1. From your NetApp account, select **Application volume groups**. Click a volume group to display the volumes in the group.  
+1. From your NetApp account, select **Application volume groups**. Select a volume group to display the volumes in the group.  
 
 2. Select the volume you want to resize, delete, or change throughput. The volume overview is displayed. 
 
     [![Screenshot that shows Application Volume Groups overview page.](./media/application-volume-group-manage-volumes/application-volume-group-overview.png)](./media/application-volume-group-manage-volumes/application-volume-group-overview.png#lightbox)  
 
-    * To resize the volume, click **Resize** and specify the quota in GiB.
+    * To resize the volume, select **Resize** and specify the quota in GiB.
 
     ![Screenshot that shows the Update Volume Quota window.](./media/application-volume-group-manage-volumes/application-volume-resize.png)
 
-    * To change the throughput for the volume, click **Change throughput** and specify the intended throughput in MiB/s.
+    * To change the throughput for the volume, select **Change throughput** and specify the intended throughput in MiB/s.
 
     ![Screenshot that shows the Change Throughput window.](./media/application-volume-group-manage-volumes/application-volume-change-throughput.png)
 
-    * To delete the volume in the volume group, click **Delete**. If you are prompted, type the volume name to confirm the deletion.  
+    * To delete the volume in the volume group, select **Delete**. If prompted, enter the volume name to confirm the deletion.  
 
     > [!IMPORTANT]
-    > The volume deletion operation cannot be undone.
+    > Volume deletion is permanent. It can't be undone.
     
     ![Screenshot that shows the Delete Volume window.](./media/application-volume-group-manage-volumes/application-volume-delete.png)
 

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: 09/12/2024
+ms.date: 02/13/2025
 ms.author: anfdocs
 ---
 
@@ -37,29 +37,6 @@ This article describes requirements and considerations about [using the volume c
 * [Large volumes](large-volumes-requirements-considerations.md) are supported with cross-region replication only with an hourly or daily replication schedule.
 * If the volume's size exceeds 95% utilization, there's a risk that replication to the destination volume can fail depending on the rate of data changes. 
 
-## Large volumes configuration
-
-[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) are supported with cross-region replication. You must [first register for the large volumes feature](large-volumes-requirements-considerations.md#register-the-feature) then register to use large volumes with cross-region replication:
-
->[!NOTE]
->Cross-zone and cross-region replication use the same Azure Feature Exposure Control (AFEC) name of `ANFLargeVolumesCRR`. If you've registered for cross-zone replication, the registration also works for cross-region replication. 
-
-1.  Register the feature by running the following commands:
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFLargeVolumesCRR
-    ```
-
-2. Check the status of the feature registration: 
-
-    > [!NOTE]
-    > The **RegistrationState** may be 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 ANFLargeVolumesCRR
-    ```
-
-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. 
-
 ## Next steps
 * [Create volume replication](cross-region-replication-create-peering.md)
 * [Display health status of replication relationship](cross-region-replication-display-health-status.md)

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: 07/30/2024
+ms.date: 02/13/2025
 ms.author: anfdocs
 ---
 # Requirements and considerations for using cross-zone replication 
@@ -25,37 +25,14 @@ This article describes requirements and considerations about [using the volume c
 * Azure NetApp Files replication doesn't currently support multiple subscriptions; all replications must be performed under a single subscription.
 * 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 does not support cascading and fan in/out topologies.
-* After you set up cross-zone replication, the replication process creates *SnapMirror snapshots* to provide references between the source volume and the destination volume. SnapMirror snapshots are cycled automatically when a new one is created for every incremental transfer. You cannot delete SnapMirror snapshots until you delete the replication relationship and volume. 
-* You cannot mount a dual-protocol volume until you [authorize replication from the source volume](cross-region-replication-create-peering.md#authorize-replication-from-the-source-volume) and the initial [transfer](cross-region-replication-display-health-status.md#display-replication-status) happens.
-* You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after you've deleted replication relationship. You cannot delete manual snapshots for the destination volume until you break the replication relationship.
-* When reverting a source volume with an active volume replication relationship, only snapshots that are more recent than the SnapMirror snapshot can be used in the revert operation. For more information, see [Revert a volume using snapshot revert with Azure NetApp Files](snapshots-revert-volume.md).
+* Cross-zone replication doesn't support cascading and fan in/out topologies.
+* After you set up cross-zone replication, the replication process creates *SnapMirror snapshots* to provide references between the source volume and the destination volume. SnapMirror snapshots are cycled automatically when a new one is created for every incremental transfer. You can't delete SnapMirror snapshots until you delete the replication relationship and volume. 
+* You can't mount a dual-protocol volume until you [authorize replication from the source volume](cross-region-replication-create-peering.md#authorize-replication-from-the-source-volume) and the initial [transfer](cross-region-replication-display-health-status.md#display-replication-status) happens.
+* You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after you've deleted replication relationship. You can't delete manual snapshots for the destination volume until you break the replication relationship.
+* When you revert a source volume with an active volume replication relationship, only snapshots dated more recently than the SnapMirror snapshot can be used in the revert operation. For more information, see [Revert a volume using snapshot revert with Azure NetApp Files](snapshots-revert-volume.md).
 * Data replication volumes support [customer-managed keys](configure-customer-managed-keys.md).
 * [Large volumes](large-volumes-requirements-considerations.md) are supported with cross-zone replication only with an hourly or daily replication schedule.
 
-## Large volumes configuration
-
-[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) are supported in cross-zone replication. You must [first register for the large volumes feature](large-volumes-requirements-considerations.md#register-the-feature) then register to use large volumes with cross-zone replication:
-
->[!NOTE]
->Cross-zone and cross-region replication use the same Azure Feature Exposure Control (AFEC) name of `ANFLargeVolumesCRR`. If you've registered for cross-region replication, the registration also works for cross-zone replication. 
-
-1.  Register the feature by running the following commands:
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFLargeVolumesCRR
-    ```
-
-2. Check the status of the feature registration: 
-
-    > [!NOTE]
-    > The **RegistrationState** may be 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 ANFLargeVolumesCRR
-    ```
-
-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. 
-
 ## Next steps
 * [Understand cross-zone replication](cross-zone-replication-introduction.md)
 * [Create cross-zone replication relationships](create-cross-zone-replication.md)

articles/azure-netapp-files/regional-capacity-quota.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 10/11/2021
+ms.date: 10/11/2024
 ms.author: anfdocs
 ---
 # Regional capacity quota for Azure NetApp Files
@@ -14,7 +14,7 @@ This article explains regional capacity quota of Azure NetApp Files.
 
 ## Display regional capacity quota
 
-You can click **Quota** under Settings of Azure NetApp Files to display the current and default quota sizes for the region. 
+You can select **Quota** under Settings of Azure NetApp Files to display the current and default quota sizes for the region. 
 
 For example: 
 

articles/azure-netapp-files/request-region-access.md

@@ -5,12 +5,12 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/15/2021
+ms.date: 02/10/2025
 ms.author: anfdocs
 ---
 # Request region access for Azure NetApp Files
 
-In some special situations, you might need to explicitly request access to a region. This article explains how to submit a request. 
+In special situations, you need to explicitly request access to a region. Learn how to submit a request. 
 
 ## Steps
 
@@ -23,7 +23,7 @@ In some special situations, you might need to explicitly request access to a reg
 
     ![Screenshot that shows the Problem Description tab.](./media/shared/support-problem-descriptions.png)
 
-3. Under the **Additional details** tab, click **Enter details** in the Request Details field.  
+3. In the **Additional details** tab, select **Enter details** in the Request Details field.  
 
     ![Screenshot that shows the Details tab and the Enter Details field.](./media/shared/quota-additional-details.png)
 
@@ -33,7 +33,7 @@ In some special situations, you might need to explicitly request access to a reg
 
     ![Screenshot that shows the Quota Details window for requesting region access.](./media/request-region-access/quota-details-region-access.png)
 
-5. Click **Save and continue**. Click **Review + create** to create the request.
+5. Select **Save and continue**. Click **Review + create** to create the request.
 
 ## Next steps  
 

articles/azure-netapp-files/solutions-benefits-azure-netapp-files-electronic-design-automation.md

@@ -25,13 +25,13 @@ Azure NetApp Files helps reduce the time EDA jobs take with a highly performant,
 
 The Azure NetApp Files large volumes feature is ideal for the storage needs of this most demanding industry, namely:  
 
-* **Large capacity single namespace:** Each volume offers from up to 500TiB of usable capacity under a single mount point. 
+* **Large capacity single namespace:** Each volume offers up to 1 PiB of usable capacity under a single mount point. You can [request a 2 PiB large volume](large-volumes-requirements-considerations.md).
 
 * **High I/O rate, low latency:** In testing using an EDA simulation benchmark, a single large volume delivered over 650K storage IOPS with less than 2 milliseconds of application latency. In a typical EDA workload, IOPS consists of a mixture or file creates, reads, writes, and a significant amount of other metadata operation. This result is considered to be enterprise-grade performance for many customers. This performance improvement is made possible by the way large volumes are able to parallelize incoming write operations across storage resources in Azure NetApp Files. Though many firms require 2ms or better response time, chip design tools can tolerate higher latency than this without impact to business.  
 
 * **At 826,000 operations per second:** the performance edge of a single large volume - the application layer peaked at 7ms of latency in our tests, which shows that more operations are possible in a single large volume at a slight cost of latency. 
 
-Tests conducted using an EDA benchmark found that with a single regular Azure NetApp Files volume, workload as high as 40,000 IOPS could be achieved at the 2ms mark, and 50,000 at the edge. See the table and chart below for regular and large volume side-by-side overview.
+Tests conducted using an EDA benchmark found that with a single regular Azure NetApp Files volume, workload as high as 40,000 IOPS could be achieved at the 2ms mark, and 50,000 at the edge. See the following table and chart for regular and large volumes side-by-side overview.
 
 
 | Scenario | I/O Rate at 2ms latency | I/O Rate at performance edge (~7 ms) | MiB/s at 2ms latency | MiB/s performance edge (~7 ms) | 
@@ -86,7 +86,7 @@ The EDA workload in this test was generated using a standard industry benchmark
 
 ## Test configuration 
 
-The results were produced using the below configuration details:
+The results were produced using the following configuration details:
 
 | Component | Configuration |
 | - | - | 

articles/azure-netapp-files/solutions-windows-virtual-desktop.md

@@ -5,14 +5,14 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 08/13/2020
+ms.date: 08/13/2024
 ms.author: anfdocs
 ---
 # Benefits of using Azure NetApp Files with Azure Virtual Desktop 
 
 This article provides best practice guidance on deploying Azure Virtual Desktop with Azure NetApp Files.
 
-Azure NetApp Files is a highly performant file storage service from Azure. It can provide up to 450,000 IOPS and sub-millisecond latency, capable of supporting extremely large scale of Azure Virtual Desktop deployments. You can adjust the bandwidth and change the service level of your Azure NetApp Files volumes on demand almost instantaneously without pausing IO while retaining data plane access. This capability allows you to easily optimize your Azure Virtual Desktop deployment scale for cost. You can also create space-efficient, point-in-time volume snapshots without impacting volume performance. This capability makes it possible for you to roll back individual [FSLogix user profile containers](../virtual-desktop/store-fslogix-profile.md) via a copy from the `~snapshot` directory, or to instantaneously roll back the entire volume at once via the volume revert capability.  With up to 255 (rotational) snapshots in place to protect a volume from data loss or corruption, administrators have many chances to undo what has been done.
+Azure NetApp Files is a highly performant file storage service from Azure. It can provide up to 450,000 I/OPS and sub-millisecond latency, capable of supporting extremely large scale of Azure Virtual Desktop deployments. You can adjust the bandwidth and change the service level of your Azure NetApp Files volumes on demand almost instantaneously without pausing IO while retaining data plane access. This capability allows you to easily optimize your Azure Virtual Desktop deployment scale for cost. You can also create space-efficient, point-in-time volume snapshots without impacting volume performance. This capability makes it possible for you to roll back individual [FSLogix user profile containers](../virtual-desktop/store-fslogix-profile.md) via a copy from the `~snapshot` directory, or to instantaneously roll back the entire volume at once via the volume revert capability. With up to 255 (rotational) snapshots in place to protect a volume from data loss or corruption, administrators have many chances to undo what has been done.
 
 ## Sample blueprints
 

articles/azure-netapp-files/troubleshoot-snapshot-policies.md

@@ -5,18 +5,18 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: troubleshooting
-ms.date: 09/23/2020
+ms.date: 09/23/2024
 ms.author: anfdocs
 ---
 # Troubleshoot snapshot policy errors
 
-This article describes error scenarios you might encounter when managing Azure NetApp Files snapshot policies. It also provides solutions that can help you address the issues.
+Learn about the possible error scenarios you can encounter when managing Azure NetApp Files snapshot policies and how to address them.
 
 ## Error conditions and resolutions 
 
 |     Error condition    |     Resolution    |
 |-|-|
-| Snapshot policy creation fails with invalid snapshot policy name. | An error occurs during snapshot policy creation if your snapshot policy name is invalid. The following guidelines apply for snapshot policy names:  <ul><li> The snapshot policy name cannot contain non-ASCII or special characters. </li> <li> The snapshot policy name must begin with a letter or a number and can contain letters, numbers, underscore ('_') and hyphens ('-') only. </li> <li> The snapshot policy name must be between 1 and 64 characters.  </li></ul> Revise the snapshot policy name according to the guidelines.  |
+| Snapshot policy creation fails with invalid snapshot policy name. | An error occurs during snapshot policy creation if your snapshot policy name is invalid. The following guidelines apply for snapshot policy names:  <ul><li> The snapshot policy name cannot contain non-ASCII or special characters. </li> <li> The snapshot policy name must begin with a letter or a number and can contain letters, numbers, underscore ('_') and hyphens ('-') only. </li> <li> The snapshot policy name must be between 1 and 64 characters. </li></ul> Revise the snapshot policy name according to the guidelines.  |
 | Snapshot policy creation fails with invalid values. | Azure NetApp Files fails to create a snapshot policy if you enter an invalid value for a field such as `Number of snapshots to keep` or `Minute on the hour to take snapshot`. The valid values are as follows:  <ul><li>The value must be a valid number.</li> <li>The value must be between 0 and 59.</li></ul> Make sure that a valid value is provided for the fields. | 
 | Snapshot policy creation fails with the error `Total number of snapshots to keep exceeds 255`. | Each volume can have a [maximum of 255 snapshots](azure-netapp-files-resource-limits.md). The maximum includes the sum of all hourly, daily, weekly, and monthly snapshots. <br> Decrease the `Snapshots to keep` value and try again. |
 | Assigning policy to a volume fails with the error `Total snapshot policy is over the max '255'`. | Each volume can have a [maximum of 255 snapshots](azure-netapp-files-resource-limits.md). When the sum of all on-demand, hourly, daily, weekly, and monthly snapshots exceeds the maximum, an error occurs. <br> Decrease the `snapshots to keep` value or delete some on-demand snapshots and try again. |