Merge pull request #285549 from MicrosoftDocs/main

8/26/2024 PM Publish

Author: Taojunshen

articles/azure-arc/resource-bridge/overview.md

@@ -107,6 +107,8 @@ Arc resource bridge supports the following Azure regions:
 * South Central US
 * Canada Central
 * Australia East
+* Australia SouthEast
+
 * West Europe
 * North Europe
 * UK South

articles/azure-netapp-files/configure-ldap-over-tls.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/23/2023
+ms.date: 08/20/2024
 ms.author: anfdocs
 ---
 # Configure AD DS LDAP over TLS for Azure NetApp Files
@@ -21,21 +21,20 @@ You can use LDAP over TLS to secure communication between an Azure NetApp Files
 
 If you do not have a root CA certificate, you need to generate one and export it for use with LDAP over TLS authentication. 
 
-1. Follow [Install the Certification Authority](/windows-server/networking/core-network-guide/cncg/server-certs/install-the-certification-authority) to install and configure AD DS Certificate Authority. 
+1. Follow [Screenshot of the the Certification Authority.](/windows-server/networking/core-network-guide/cncg/server-certs/install-the-certification-authority) to install and configure AD DS Certificate Authority. 
 
-2. Follow [View certificates with the MMC snap-in](/dotnet/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in) to use the MMC snap-in and the Certificate Manager tool.  
+2. Follow [Screenshot of the view certificates with the MMC snap-in.](/dotnet/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in) to use the MMC snap-in and the Certificate Manager tool.  
     Use the Certificate Manager snap-in to locate the root or issuing certificate for the local device. You should run the Certificate Management snap-in commands from one of the following settings:  
     * A Windows-based client that has joined the domain and has the root certificate installed 
     * Another machine in the domain containing the root certificate  
 
 3. Export the root CA certificate.  
-    Root CA certificates can be exported from the Personal or Trusted Root Certification Authorities directory, as shown in the following examples:   
-    ![screenshot that shows personal certificates](./media/configure-ldap-over-tls/personal-certificates.png)   
-    ![screenshot that shows trusted root certification authorities](./media/configure-ldap-over-tls/trusted-root-certification-authorities.png)    
+    Root CA certificates can be exported from the Personal or Trusted Root Certification Authorities directory. The following image shows the Personal Root Certification Authority directory:   
+    ![Screenshot that shows personal certificates.](./media/configure-ldap-over-tls/personal-certificates.png).  
 
     Ensure that the certificate is exported in the Base-64 encoded X.509 (.CER) format: 
 
-    ![Certificate Export Wizard](./media/configure-ldap-over-tls/certificate-export-wizard.png)
+    ![Screenshot of the Certificate Export Wizard.](./media/configure-ldap-over-tls/certificate-export-wizard.png)
 
 ## Enable LDAP over TLS and upload root CA certificate 
 

articles/azure-netapp-files/manage-cool-access.md

@@ -29,6 +29,7 @@ The storage with cool access feature provides options for the “coolness period
 * See [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md#resource-limits) for maximum number of volumes supported for cool access per subscription per region.
 * Considerations for using cool access with [cross-region replication](cross-region-replication-requirements-considerations.md) and [cross-zone replication](cross-zone-replication-introduction.md): 
     * The cool access setting on the destination is updated automatically to match the source volume whenever the setting is changed on the source volume or during authorizing or performing a reverse resync of the replication. Changes to the cool access setting on the destination volume don't affect the setting on the source volume.
+    * In cross-region or cross-zone replication configuration, you can enable cool access exclusively for destination volumes to enhance data protection and create cost savings without affecting latency in source volumes.
 * Considerations for using cool access with [snapshot restore](snapshots-restore-new-volume.md):
     * When restoring a snapshot of a cool access enabled volume to a new volume, the new volume inherits the cool access configuration from the parent volume. Once the new volume is created, the cool access settings can be modified.  
     * You can't restore from a snapshot of a non-cool-access volume to a cool access volume.  Likewise, you can't restore from a snapshot of a cool access volume to a non-cool-access volume.