Merge pull request #302972 from MicrosoftDocs/main

Auto Publish – main to live - 2025-07-18 17:00 UTC

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

articles/application-gateway/application-gateway-tls-version-retirement.md

@@ -5,7 +5,7 @@ services: application gateway
 author: jaesoni
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 05/15/2025
+ms.date: 07/18/2025
 ms.author: mbender
 ms.custom:
   - build-2025
@@ -84,7 +84,26 @@ You don't need to configure anything on your Application Gateway for the backend
 * For V2 SKUs: the connections to backend servers will always be with preferred TLS v1.3 and minimum up to TLS v1.2
 * For V1 SKUs: the connections to backend servers will always be with TLS v1.2
 
-You must ensure that your servers in the backend pools are compatible with these updated protocol versions. This compatibility avoids any disruptions when establishing a TLS/HTTPS connection with those backend servers.
+You must ensure that your servers in the backend pools are compatible with these updated protocol versions. This compatibility avoids any disruptions when establishing an TLS/HTTPS connection with those backend servers.
+
+## Identification methods
+
+### Metrics
+To determine whether clients connecting to your Application Gateway resource are utilizing TLS 1.0 or 1.1, use the `Client TLS protocol` metric provided by Application Gateway. For more information, see the [metrics documentation](monitor-application-gateway-reference.md#metrics). You can view it from the Portal by following these steps.
+
+1. Go to the Application Gateway resource in the Azure portal.
+2. In the left menu pane, open the "Metrics" blade in Monitoring section.
+3. Select metric as `Client TLS protocol` from the dropdown.
+4. To view granular protocol version information, select "Apply splitting" and choose "TLS protocol".
+
+[![A diagram showing metrics page with TLS version split for application gateway traffic.](media/application-gateway-tls-version-retirement/metric-tls-version.png)](media/application-gateway-tls-version-retirement/metric-tls-version.png#lightbox)
+
+### Logs
+You can also check the [Application Gateway Access logs](monitor-application-gateway-reference.md#access-log-category) to view this information in log format.
+
+### Error information
+Once support for TLS versions 1.0 and 1.1 is discontinued, clients may encounter errors such as `curl: (35) error:0A000410:SSL routines::sslv3 alert handshake failure`. Depending on the browser being used, various messages indicating TLS handshake failures may be displayed.
+
 
 ## Next steps
 

articles/application-gateway/media/application-gateway-tls-version-retirement/metric-tls-version.png

@@ -43,6 +43,12 @@ Service account owners can manage consent requests and private endpoints through
 
 When creating a private endpoint, you must specify the App Configuration store to which it connects. If you enable the geo-replication for an App Configuration store, you can connect to all replicas of the store using the same private endpoint. If you have multiple App Configuration stores, you need a separate private endpoint for each store.
 
+### Considerations for geo-replicated App Configuration stores
+
+When geo-replication is enabled for your App Configuration store, you can use a single private endpoint to connect to all replicas. However, since private endpoints are regional resources, this approach may not ensure connectivity in the event of a regional outage.
+
+For enhanced resilience, consider creating private endpoints for each replica of your geo-replicated store, in addition to a private endpoint for the origin store. This ensures that if one region becomes unavailable, clients can access the store through private endpoints provisioned in the same region as a replica. Ensure the relevant [DNS changes](#dns-changes-for-private-endpoints) are made so the endpoint for each replica resolves to the relevant IP address for the private endpoint in the respective replica's region.
+
 ### Connecting to private endpoints
 
 Azure relies upon DNS resolution to route connections from the VNet to the configuration store over a private link. You can quickly find connections strings in the Azure portal by selecting your App Configuration store, then selecting **Settings** > **Access Keys**.  

articles/azure-app-configuration/concept-private-endpoint.md

@@ -1,11 +1,11 @@
 ---
 title: Search backups of Azure NetApp Files volumes 
-description: Describes how to display and search backups of Azure NetApp Files volumes at the volume level and the NetApp account level.
+description: You can display and search for backups at the NetApp account level or the volume level. 
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 04/24/2024
+ms.date: 07/18/2025
 ms.author: anfdocs
 # Customer intent: As a cloud administrator, I want to search for backups of Azure NetApp Files volumes, so that I can efficiently manage and restore backups according to my data protection strategy.
 ---
@@ -16,7 +16,16 @@ The names used for snapshots are preserved when the snapshots are backed up. Sna
 If a volume is deleted, its backups are retained. The backups are listed in the associated backup vault, under the **Backups** section. This list includes all backups within the backup vault in the region. It can be used to restore a backup to a volume in another NetApp account under the same subscription.
 
 >[!IMPORTANT]
->All existing backups must be migrated to backup vaults. You can search for backups, but you are unable to perform any operations on a backup until the backup has been migrated to a backup vault. For more information about this procedure, see [Manage a backup vault](backup-vault-manage.md).
+>All existing backups must be migrated to backup vaults. You can search for backups, but you're unable to perform any operations on a backup until the backup has migrated to a backup vault. For more information about this procedure, see [Manage a backup vault](backup-vault-manage.md).
+
+In addition to name, size, and type, backups display time-based information:
+
+| Field | Description |
+| - | - | 
+| Started | Date and time the snapshot was created | 
+| Initiated | Date and time the backup was created |
+| Completed | Date and time the backup was completed | 
+| Duration | The elapsed time from the creation of the snapshot to the completion of the backup time. When you create a backup with existing snapshot, the reported backup duration can appear longer than the actual time taken for the backup operation. |
 
 ## Search backups from backup vault 
 
@@ -33,16 +42,16 @@ You can display and search backups at the volume level:
 
 1. Select **Volumes**.
 
-1. If you have migrated to a backup vault, navigate to **Backup Vault**. Select the backup vault.
-    If you have not yet migrated to a backup vault, navigate to **Backups**.   
+1. If you've migrated to a backup vault, navigate to **Backup Vault**. Select the backup vault.
+    If you've not yet migrated to a backup vault, navigate to **Backups**.   
     The **Type** column shows whether the backup is generated by a *Scheduled* (policy-based) or a *manual* backup.
 
 3. In the **Search Backups** field, enter the backup name that you want to search for.  
 
     A partial search is supported; you don’t have to specify the entire backup name. The search filters the backups based on the search string.
 
     :::image type="content" source="./media/backup-search/backup-search-volume-level.png" alt-text="Screenshot that shows a list of backup for a volume." lightbox="./media/backup-search/backup-search-volume-level.png":::
-    
+
 ## Next steps  
 
 * [Understand Azure NetApp Files backup](backup-introduction.md)

articles/azure-netapp-files/backup-search.md

@@ -47,11 +47,11 @@ Two settings are available for network features:
 
 This section shows you how to set the network features option when you create a new volume. 
 
-1. During the process of creating a new [NFS](azure-netapp-files-create-volumes.md), [SMB](azure-netapp-files-create-volumes-smb.md), or [dual-protocol](create-volumes-dual-protocol.md) volume, you can set the **Network Features** option to **Basic** or **Standard** under the Basic tab of the Create a Volume screen.
+1. During the process of creating a new [NFS](azure-netapp-files-create-volumes.md), [SMB](azure-netapp-files-create-volumes-smb.md), or [dual-protocol](create-volumes-dual-protocol.md) volume, you can set the **Network Features** option to **Basic** or **Standard** under the Basic tab of the Create a volume screen.
 
     ![Screenshot that shows volume creation for Standard network features.](./media/configure-network-features/network-features-create-standard.png)
 
-2. Before completing the volume creation process, you can display the specified network features setting in the **Review + Create** tab of the Create a Volume screen. Select **Create** to complete the volume creation.
+2. Before completing the volume creation process, you can display the specified network features setting in the **Review + Create** tab of the Create a volume screen. Select **Create** to complete the volume creation.
 
     ![Screenshot that shows the Review and Create tab of volume creation.](./media/configure-network-features/network-features-review-create-tab.png)
 
@@ -114,9 +114,9 @@ Updating the network features of your volume alters the underlying network sibli
 >A discontinuity between state data and remote Azure resource configurations--notably, in the `network_features` argument--can result in the destruction of one or more volumes and possible data loss upon running `terraform apply`. Carefully follow the workaround outlined here to safely update the network features from Basic to Standard of Terraform-managed volumes. 
 
 >[!NOTE]
->A Terraform module usually consists solely of all top level `*.tf` and/or `*.tf.json` configuration files in a directory, but a Terraform module can make use of module calls to explicitly include other modules into the configuration. You can [learn more about possible module structures](https://developer.hashicorp.com/terraform/language/files). To update all configuration file in your module that reference Azure NetApp Files volumes, be sure to look at all possible sources where your module can reference configuration files.
+>A Terraform module usually consists solely of all top level `*.tf` and/or `*.tf.json` configuration files in a directory, but a Terraform module can make use of module calls to explicitly include other modules into the configuration. You can [learn more about possible module structures](https://developer.hashicorp.com/terraform/language/files). To update all configuration files in your module that refer to Azure NetApp Files volumes, be sure to look at all possible sources where your module can reference configuration files.
 
-The name of the state file in your Terraform module is `terraform.tfstate`. It contains the arguments and their values of all deployed resources in the module. Below is highlighted the `network_features` argument with value “Basic” for an Azure NetApp Files Volume in a `terraform.tfstate` example file:
+The name of the state file in your Terraform module is `terraform.tfstate`. It contains the arguments and the values of all deployed resources in the module. The following image shows the `terraform.tfstate` file for an Azure NetApp Files volume, highlighting the `network_features` argument with value "Basic":
 
 :::image type="content" source="./media/configure-network-features/terraform-module.png" alt-text="Screenshot of Terraform module." lightbox="./media/configure-network-features/terraform-module.png":::
 
@@ -129,9 +129,9 @@ By following the steps outlined here, the `network_features` argument in the `te
 
 #### Determine affected volumes 
 
-Changing the network features for an Azure NetApp Files Volume can impact the network features of other Azure NetApp Files Volumes. Volumes in the same network sibling set must have the same network features setting. Therefore, before you change the network features of one volume, you must determine all volumes affected by the change using the Azure portal.
+Changing the network features for an Azure NetApp Files volume can impact the network features of other Azure NetApp Files volumes. Volumes in the same network sibling set must have the same network features setting. Therefore, before you change the network features of one volume, you must determine all volumes affected by the change using the Azure portal.
 
-1. Log in to the Azure portal. 
+1. Sign in to the Azure portal. 
 1. Navigate to the volume for which you want to change the network features option.
 1. Select the **Change network features**. ***Do **not** select Save.***
 1. Record the paths of the affected volumes then select **Cancel**. 
@@ -174,7 +174,7 @@ The `ignore_changes` feature is intended to be used when a resource’s referenc
     :::image type="content" source="./media/configure-network-features/terraform-plan-output.png" alt-text="Screenshot of terraform plan command output." lightbox="./media/configure-network-features/terraform-plan-output.png":::
 
     >[!IMPORTANT]
-    > As a safety precaution, execute `terraform plan` before executing `terraform apply`. The command `terraform plan` allows you to create a “plan” file, which contains the changes to your remote resources. This plan allows you to know if any of your affected volumes can be destroyed by running `terraform apply`.
+    > As a safety precaution, execute `terraform plan` before executing `terraform apply`. The command `terraform plan` allows you to create a "plan" file, which contains the changes to your remote resources. This plan allows you to know if any of your affected volumes can be destroyed by running `terraform apply`.
 
 1. Run `terraform apply` to update the `terraform.tfstate` file.
 

articles/azure-netapp-files/configure-network-features.md

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: references_regions
 ms.topic: concept-article
-ms.date: 04/17/2025
+ms.date: 07/18/2025
 ms.author: anfdocs
 # Customer intent: As a storage administrator, I want to review the requirements and limitations of large volumes in Azure NetApp Files, so that I can effectively plan the deployment and management of storage solutions to meet my organization's data capacity and performance needs.
 ---
@@ -21,7 +21,8 @@ The following requirements and considerations apply to large volumes. For perfor
 * A regular volume can’t be converted to a large volume.
 * You must create a large volume at a size of 50 TiB or larger. The maximum size of a large volume is 1,024 TiB, though 2-PiB large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team. 
 * You can't resize a large volume to less than 50 TiB.
-    A large volume cannot be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits). When requesting the resize, specify the desired size in TiB. 
+    * A large volume can't be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits). When requesting the resize, specify the desired size in TiB. 
+    * When reducing the size of a large volume, the size you can decrease to depends on the size of files written to the volume and the snapshots currently active on the volumes. 
 * Large volumes are currently not supported with Azure NetApp Files backup.
 * You can't create a large volume with application volume groups.
 * Currently, large volumes aren't suited for database (HANA, Oracle, SQL Server, etc.) data and log volumes. For database workloads requiring more than a single volume’s throughput limit, consider deploying multiple regular volumes. To optimize multiple volume deployments for databases, use [application volume groups](application-volume-group-concept.md).

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -3,8 +3,8 @@ title: About the Azure Virtual Machine restore process
 description: Learn how the Azure Backup service restores Azure virtual machines
 ms.topic: overview
 ms.date: 09/09/2024
-author: jyothisuri
-ms.author: jsuri
+author: AbhishekMallick-MS
+ms.author: v-mallicka
 ms.custom: engagement-fy24
 # Customer intent: As an IT admin, I want to understand the Azure VM restore process and its options, so that I can efficiently recover virtual machines based on different scenarios and ensure business continuity.
 ---

articles/azure-netapp-files/media/backup-search/backup-search-vault.png

@@ -4,8 +4,8 @@ description: Learn about the restore options available with the Microsoft Azure
 ms.reviewer: mepand
 ms.topic: overview
 ms.date: 09/09/2024
-author: jyothisuri
-ms.author: jsuri
+author: AbhishekMallick-MS
+ms.author: v-mallicka
 ms.custom: engagement-fy24
 # Customer intent: As a system administrator, I want to explore the various restore options available with the MARS agent, so that I can efficiently recover data in different scenarios and ensure business continuity.
 ---