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

Author: ElazarK

.whatsnew/.application-management.json

@@ -1,7 +1,7 @@
 ---
 title: Supported regions for Change tracking and inventory using Azure Monitoring Agent
 description: This article describes the supported region mappings between an Automation account and monitoring agent workspace as it relates to certain features of Azure Automation.
-ms.date: 12/14/2022
+ms.date: 03/04/2024
 services: automation
 ms.topic: conceptual
 ms.custom: references_regions
@@ -18,24 +18,26 @@ The following table shows the supported mappings:
 
 |**Geography**| **Monitoring Agent workspace region**|
 |---| ---|
-|**US**| EastUS</br> EastUS2</br> WestUS </br> WestUS2 </br> NorthCentralUS </br> CentralUS </br> SouthCentralUS </br> WestCentralUS|
+|**Asia Pacific**| EastAsia </br> SoutheastAsia|
+|**Australia**| AustraliaEast </br> AustraliaSoutheast |
 |**Brazil**| BrazilSouth|
 |**Canada**| CanadaCentral|
-|**China**| ChinaEast2<sup>1</sup>|
-|**Asia Pacific**| EastAsia </br> SoutheastAsia|
+|**China**| ChinaEast2|
+|**Europe**| NorthEurope </br> WestEurope|
+|**France**| FranceCentral|
+|**Germany** | Germany WestCentral|
 |**India**| CentralIndia|
 |**Japan**| JapanEast|
-|**Australia**| AustraliaEast </br> AustraliaSoutheast </br> AustraliaSoutheast|
 |**Korea**| KoreaCentral|
 |**Norway**| NorwayEast|
-|**Europe**| NorthEurope </br> WestEurope|
-|**France**| FranceCentral|
-|**United Kingdom**| UKSouth|
+|**Sweden** | SwedenCentral|
 |**Switzerland**| SwitzerlandNorth|
 |**United Arab Emirates**| UAENorth|
-|**US Gov**| USGovVirginia </br> USGovArizona<sup>1</sup>|
+|**United Kingdom**| UKSouth|
+|**US Gov**| USGovVirginia </br> USGovArizona|
+|**US**| EastUS</br> EastUS2</br> WestUS </br> WestUS2 </br> NorthCentralUS </br> CentralUS </br> SouthCentralUS </br> WestCentralUS|
+
 
-<sup>1</sup> In this region, only Update Management is supported, and other features like Change Tracking and Inventory are not available at this time.
 
 
 ## Next steps

.whatsnew/.application-provisioning.json

@@ -111,11 +111,11 @@ Before creating an SMB volume, you need to create an Active Directory connection
     * Select your **Active Directory** connection from the drop-down list.  
     
     * Specify a unique **share name** for the volume. This share name is used when you create mount targets. The requirements for the share name are as follows:   
-        - It must be unique within each subnet in the region. 
-        - It must start with an alphabetical character.
+        - For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region.  
+        - For volumes in availability zones, it must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
         - It can contain only letters, numbers, or dashes (`-`). 
         - The length must not exceed 80 characters.   
-
+    
     * <a name="smb3-encryption"></a>If you want to enable encryption for SMB3, select **Enable SMB3 Protocol Encryption**.   
 
         This feature enables encryption for in-flight SMB3 data. SMB clients not using SMB3 encryption will not be able to access this volume.  Data at rest is encrypted regardless of this setting.   

.whatsnew/.application-proxy.json

@@ -106,7 +106,8 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
     * Select **NFS** as the protocol type for the volume.   
 
     * Specify a unique **file path** for the volume. This path is used when you create mount targets. The requirements for the path are as follows:   
-        - It must be unique within each subnet in the region. 
+        - For volumes not in an availability zone or volumes in the same availability zone, it must be unique within each subnet in the region. 
+        - For volumes in availability zones, it must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness). 
         - It must start with an alphabetical character.
         - It can contain only letters, numbers, or dashes (`-`). 
         - The length must not exceed 80 characters.

.whatsnew/.external-identities-ciam.json

@@ -138,18 +138,19 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
         ![Show advanced selection](./media/shared/volume-create-advanced-selection.png)
 
-3. Click the **Protocol** tab, and then complete the following actions:  
+3. Select the **Protocol** tab, and then complete the following actions:  
     * Select **Dual-protocol** as the protocol type for the volume.   
 
     * Specify the **Active Directory** connection to use.
 
     * Specify a unique **Volume Path**. This path is used when you create mount targets. The requirements for the path are as follows:  
 
-        - It must be unique within each subnet in the region. 
+        - For volumes not in an availability zone or volumes in the same availability zone, the volume path must be unique within each subnet in the region. 
+        - For volumes in availability zones, the volume path must be unique within each availability zone. This feature is currently in **preview** and requires you to register the feature. For more information, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md#file-path-uniqueness).
         - It must start with an alphabetical character.
         - It can contain only letters, numbers, or dashes (`-`). 
         - The length must not exceed 80 characters.
-
+    
     * Specify the **versions** to use for dual protocol: **NFSv4.1 and SMB**, or **NFSv3 and SMB**.
 
     * Specify the **Security Style** to use: NTFS (default) or UNIX.