Merge branch 'main' into release-aio-2603

Author: v-alje

articles/azure-app-configuration/concept-enable-rbac.md

@@ -60,9 +60,27 @@ Follow these steps to assign App Configuration Data roles to your credential.
 3. On the **Members** tab, follow the wizard to select the credential you're granting access to and then select **Next**.
 4. Finally, on the **Review + assign** tab, select **Review + assign** to assign the role.
 
-## Cloud-specific audience for Entra ID authentication
+## Audience for Entra ID authentication
 
-When using Entra ID and the following Azure App Configuration libraries in clouds other than Azure cloud, Azure Government, and Microsoft Azure operated by 21Vianet, an appropriate Entra ID audience must be configured to enable authentication.
+The audience for Microsoft Entra ID authentication defines who is permitted to access a specific resource. It identifies the intended recipient of the security token. App Configuration supports different audiences for different clouds.
+
+### App Configuration audience
+
+For Azure App Configuration in the global Azure cloud, use the following audience: 
+
+`https://appconfig.azure.com`
+
+For Azure App Configuration in the national clouds, use the applicable audience specified in the table below:
+
+| **National cloud**                   | **Audience**                        |
+| ------------------------------------ | ----------------------------------- |
+| Azure Government                     | `https://appconfig.azure.us`        |
+| Microsoft Azure operated by 21Vianet | `https://appconfig.azure.cn`        |
+| Bleu                                 | `https://appconfig.sovcloud-api.fr` |
+
+### Configure cloud-specific audience
+
+When using Entra ID to authenticate with Azure App Configuration in clouds other than Azure cloud, Azure Government, and Microsoft Azure operated by 21Vianet, an appropriate Entra ID audience must be configured.
 
 > [!TIP]
 > If you encounter the following error when connecting to Azure App Configuration, it’s typically because you’re using App Configuration in a specific cloud without explicitly configuring the Microsoft Entra ID audience.
@@ -74,32 +92,12 @@ When using Entra ID and the following Azure App Configuration libraries in cloud
 > To resolve this issue, configure the appropriate Entra ID audience as shown in the code snippets below.
 
 ### [.NET](#tab/dotnet)
+#### .NET configuration provider
 
-The Audience for the target cloud must be configured for the following packages.
-
-- Azure SDK for .NET: Azure.Data.AppConfiguration >= 1.6.0
-- .NET configuration provider: Microsoft.Extensions.Configuration.AzureAppConfiguration >= 8.2.0
-
-In the **Azure SDK for .NET**, audience is configured by utilizing the following API calls:
-
-* The ConfigurationClient constructor [accepts ConfigurationClientOptions](/dotnet/api/azure.data.appconfiguration.configurationclient.-ctor#azure-data-appconfiguration-configurationclient-ctor(system-uri-azure-core-tokencredential-azure-data-appconfiguration-configurationclientoptions))
-* ConfigurationClientOptions allows [Audience](/dotnet/api/azure.data.appconfiguration.configurationclientoptions.audience#azure-data-appconfiguration-configurationclientoptions-audience) to be set
-
-The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
-
-```csharp
-var configurationClient = new ConfigurationClient(
-    myStoreEndpoint,
-    new DefaultAzureCredential(),
-    new ConfigurationClientOptions
-    {
-        Audience = "{Cloud specific audience here}"
-    });
-```
-
-In the **.NET configuration provider**, audience is configured by utilizing the following API calls:
-
-* AzureAppConfigurationOptions exposes a [ConfigureClientOptions](/dotnet/api/microsoft.extensions.configuration.azureappconfiguration.azureappconfigurationoptions.configureclientoptions#microsoft-extensions-configuration-azureappconfiguration-azureappconfigurationoptions-configureclientoptions(system-action((azure-data-appconfiguration-configurationclientoptions)))) method
+If your application uses any of the following packages, audience can be configured by utilizing the [ConfigureClientOptions](/dotnet/api/microsoft.extensions.configuration.azureappconfiguration.azureappconfigurationoptions.configureclientoptions#microsoft-extensions-configuration-azureappconfiguration-azureappconfigurationoptions-configureclientoptions(system-action((azure-data-appconfiguration-configurationclientoptions)))) method. Use version **8.2.0** or later of any of the following packages to configure the audience.
+ - `Microsoft.Extensions.Configuration.AzureAppConfiguration`
+ - `Microsoft.Azure.AppConfiguration.AspNetCore`
+ - `Microsoft.Azure.AppConfiguration.Functions.Worker`
 
 The following code snippet demonstrates how to add the Azure App Configuration provider into a .NET application with a cloud-specific audience.
 
@@ -110,30 +108,34 @@ builder.AddAzureAppConfiguration(o =>
             myStoreEndpoint,
             new DefaultAzureCredential());
 
-        o.ConfigureClientOptions(clientOptions => clientOptions.Audience = "{Cloud specific audience here}");
+        o.ConfigureClientOptions(clientOptions =>
+            clientOptions.Audience = "{Cloud specific audience here}");
     });
 ```
 
-### [Java](#tab/java)
-
-The Audience for the target cloud must be configured for the following packages.
-
-- Azure SDK for Java: azure-data-appconfiguration >= 1.8.0
-- Java configuration provider: spring-cloud-azure-appconfiguration-config >= 5.22.0
+#### Azure SDK for .NET
 
-In the **Azure SDK for Java**, audience is configured by passing the `audience` option to the `ConfigurationClientBuilder` when building a `ConfigurationClient`.
+If your application uses the following package, audience can be configured in `ConfigurationClientOptions` when constructing the `ConfigurationClient` object. Use version **1.6.0** or later of the following package.
+ - `Azure.Data.AppConfiguration`
 
 The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
 
-```java
-ConfigurationClient configurationClient = new ConfigurationClientBuilder()
-    .endpoint(myStoreEndpoint)
-    .credential(new DefaultAzureCredentialBuilder().build())
-    .audience(ConfigurationAudience.fromString("{Cloud specific audience here}"))
-    .buildClient();
+```csharp
+var configurationClient = new ConfigurationClient(
+    myStoreEndpoint,
+    new DefaultAzureCredential(),
+    new ConfigurationClientOptions
+    {
+        Audience = "{Cloud specific audience here}"
+    });
 ```
 
-In the **Spring configuration provider**, audience is configured by customizing the `ConfigurationClientBuilder` through the `ConfigurationClientCustomizer` interface, then adding it to the bootstrap registry.
+### [Java](#tab/java)
+#### Spring configuration provider
+
+If your application uses any of the following packages, audience can be configured by customizing the `ConfigurationClientBuilder` through the `ConfigurationClientCustomizer` interface, then adding it to the bootstrap registry. Use version **5.22.0** or later of the following packages to configure the audience.
+ - `spring-cloud-azure-appconfiguration-config`
+ - `spring-cloud-azure-appconfiguration-config-web`
 
 The following code snippet demonstrates how to add the Azure App Configuration provider into a Spring Boot application with a cloud-specific audience.
 
@@ -178,24 +180,26 @@ public class Application {
 }
 ```
 
-### [JavaScript](#tab/javascript)
-
-The Audience for the target cloud must be configured for the following packages.
-
-- Azure SDK for JavaScript: @azure/app-configuration >= 1.9.0
-- JavaScript configuration provider: @azure/app-configuration-provider >= 1.0.0
+#### Azure SDK for Java
 
-In the **Azure SDK for JavaScript**, audience is configured by passing the `audience` option to the `AppConfigurationClient` constructor.
+If your application uses the following package, audience can be configured by passing the `audience` option to the `ConfigurationClientBuilder` when building a `ConfigurationClient`. Use version **1.8.0** or later of the following package.
+ - `azure-data-appconfiguration`
 
 The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
 
-```javascript
-const client = new AppConfigurationClient(myStoreEndpoint, new DefaultAzureCredential(), {
-    audience: "{Cloud specific audience here}",
-});
+```java
+ConfigurationClient configurationClient = new ConfigurationClientBuilder()
+    .endpoint(myStoreEndpoint)
+    .credential(new DefaultAzureCredentialBuilder().build())
+    .audience(ConfigurationAudience.fromString("{Cloud specific audience here}"))
+    .buildClient();
 ```
 
-In the **JavaScript configuration provider**, audience is configured by passing the `clientOptions` with the `audience` property to the `load` function.
+### [JavaScript](#tab/javascript)
+#### JavaScript configuration provider
+
+If your application uses the following package, audience can be configured by passing the `clientOptions` with the `audience` property to the `load` function. Use version **1.0.0** or later of the following package.
+ - `@azure/app-configuration-provider`
 
 The following code snippet demonstrates how to load Azure App Configuration in a JavaScript application with a cloud-specific audience.
 
@@ -207,47 +211,71 @@ const appConfig = await load(myStoreEndpoint, credential, {
 });
 ```
 
-### [Go](#tab/go)
+#### Azure SDK for JavaScript
 
-The Audience for the target cloud must be configured for the following packages.
+If your application uses the following package, audience can be configured by passing the `audience` option to the `AppConfigurationClient` constructor. Use version **1.9.0** or later of the following package.
+ - `@azure/app-configuration`
 
-- Azure SDK for Go: azappconfig >= 2.1.0
-- Go configuration provider: azureappconfiguration >= 1.0.0
+The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
 
-You need to import the following packages:
+```javascript
+const client = new AppConfigurationClient(myStoreEndpoint, new DefaultAzureCredential(), {
+    audience: "{Cloud specific audience here}",
+});
+```
 
-```golang
-import (
-    "github.com/Azure/azure-sdk-for-go/sdk/azcore/cloud"
-    "github.com/Azure/azure-sdk-for-go/sdk/azcore/policy"
+### [Python](#tab/python)
+#### Python configuration provider
+
+If your application uses the following package, audience can be configured by passing the keyword `audience` to the `load` method. Use version **2.4.0** or later of the following package.
+ - `azure-appconfiguration-provider`
+
+The following code snippet demonstrates how to load Azure App Configuration in a Python application with a cloud-specific audience.
+
+```python
+from azure.appconfiguration.provider import load
+from azure.identity import DefaultAzureCredential
+
+config = load(
+    endpoint=myStoreEndpoint,
+    credential=DefaultAzureCredential(),
+    audience="{Cloud specific audience here}",
 )
 ```
 
-In the **Azure SDK for Go**, audience is configured by utilizing the cloud configuration.
+#### Azure SDK for Python
+
+If your application uses the following package, audience can be configured by passing the `audience` keyword to the `AzureAppConfigurationClient` constructor. Use version **1.8.0** or later of the following package.
+ - `azure-appconfiguration`
 
 The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
 
-```golang
-credential, _:= azidentity.NewDefaultAzureCredential(nil)
+```python
+from azure.appconfiguration import AzureAppConfigurationClient
+from azure.identity import DefaultAzureCredential
 
-cloudConfig := cloud.Configuration{
-    Services: map[cloud.ServiceName]cloud.ServiceConfiguration{
-        azappconfig.ServiceName: {
-            Audience: "{Cloud specific audience here}",
-        },
-    },
-}
+client = AzureAppConfigurationClient(
+    myStoreEndpoint,
+    DefaultAzureCredential(),
+    audience="{Cloud specific audience here}",
+)
+```
 
-clientOptions := &azappconfig.ClientOptions{
-    ClientOptions: policy.ClientOptions{
-        Cloud: cloudConfig,
-    },
-}
+### [Go](#tab/go)
 
-client, _ := azappconfig.NewClient(myStoreEndpoint, credential, clientOptions)
+To configure the Entra ID audience, import the following packages in your Go application first:
+
+```golang
+import (
+    "github.com/Azure/azure-sdk-for-go/sdk/azcore/cloud"
+    "github.com/Azure/azure-sdk-for-go/sdk/azcore/policy"
+)
 ```
 
-In the **Go configuration provider**, audience is configured by passing the `ClientOptions` with the cloud configuration to the `Load` function.
+#### Go configuration provider
+
+If your application uses the following package, audience can be configured by passing the `ClientOptions` with the cloud configuration to the `Load` function. Use version **1.0.0** or later of the following package.
+ - `azureappconfiguration`
 
 The following code snippet demonstrates how to load Azure App Configuration in a Go application with a cloud-specific audience.
 
@@ -278,21 +306,34 @@ options := &azureappconfiguration.Options{
 appConfig, _ := azureappconfiguration.Load(context.Background(), authOptions, options)
 ```
 
----
+#### Azure SDK for Go
 
-### Audience
+If your application uses the following package, audience can be configured by utilizing the cloud configuration. Use version **2.1.0** or later of the following package.
+ - `azappconfig`
 
-For Azure App Configuration in the global Azure cloud, use the following audience: 
+The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
 
-`https://appconfig.azure.com`
+```golang
+credential, _:= azidentity.NewDefaultAzureCredential(nil)
 
-For Azure App Configuration in the national clouds, use the applicable audience specified in the table below:
+cloudConfig := cloud.Configuration{
+    Services: map[cloud.ServiceName]cloud.ServiceConfiguration{
+        azappconfig.ServiceName: {
+            Audience: "{Cloud specific audience here}",
+        },
+    },
+}
 
-| **National cloud**                   | **Audience**                        |
-| ------------------------------------ | ----------------------------------- |
-| Azure Government                     | `https://appconfig.azure.us`        |
-| Microsoft Azure operated by 21Vianet | `https://appconfig.azure.cn`        |
-| Bleu                                 | `https://appconfig.sovcloud-api.fr` |
+clientOptions := &azappconfig.ClientOptions{
+    ClientOptions: policy.ClientOptions{
+        Cloud: cloudConfig,
+    },
+}
+
+client, _ := azappconfig.NewClient(myStoreEndpoint, credential, clientOptions)
+```
+
+---
 
 ## Next steps
 Learn how to [use managed identities to access your App Configuration store](howto-integrate-azure-managed-service-identity.md).

articles/azure-app-configuration/monitor-app-configuration.md

@@ -237,6 +237,17 @@ The following table lists common and recommended alert rules for App C
 ### Metrics schema
 For details on the metrics schema, see [App Configuration Metrics](/azure/azure-monitor/reference/supported-metrics/microsoft-appconfiguration-configurationstores-metrics)
 
+#### Metrics Dimensions
+| Metric Name | Dimension description |
+|-------|-----|
+| HTTP Incoming Request Count | The supported dimensions are the **HttpStatusCode**, **AuthenticationScheme**, and **Endpoint** of each request. **AuthenticationScheme** can be filtered by "AAD" or "HMAC" authentication. |
+| HTTP Incoming Request Duration | The supported dimensions are the **HttpStatusCode**, **AuthenticationScheme**, and **Endpoint** of each request. **AuthenticationScheme** can be filtered by "AAD" or "HMAC" authentication. |
+| Throttled HTTP Request Count | The **Endpoint** of each request is included as a dimension. |
+| Daily Storage Usage | This metric does not have any dimensions. |
+| Request Quota Usage | The supported dimensions are the **OperationType** ("Read" or "Write") and **Endpoint** of each request. |
+| Replication Latency | The **Endpoint** of the replica that data was replicated to is included as a dimension. |
+| Snapshot Storage Size | This metric does not have any dimensions. |
+
 ### Logs schema
 
 #### Activity logs schema

articles/azure-app-configuration/rest-api-authentication-azure-ad.md

@@ -39,7 +39,7 @@ Before acquiring a Microsoft Entra token, you must identify what user you want t
 
 Request the Microsoft Entra token with a proper audience. The audience can also be referred to as the *resource* that the token is being requested for.
 
-For details on which audience to use for which cloud, refer to the [audience section of the  Entra ID access overview](./concept-enable-rbac.md#audience).
+For details on which audience to use for which cloud, refer to the [audience section of the  Entra ID access overview](./concept-enable-rbac.md#app-configuration-audience).
 
 <a name='azure-ad-authority'></a>
 

articles/azure-netapp-files/advanced-ransomware-protection.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: netapp-manishc
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 01/13/2026
+ms.date: 03/17/2026
 ms.author: anfdocs
 ms.custom: references_regions
 # Customer intent: "As a data engineer, I want to understand the advanced ransomware protection features of Azure NetApp Files, so that I can safeguard the cloud file data against ransomware attacks."
@@ -56,7 +56,10 @@ Advanced ransomware protection (ARP) in Azure NetApp Files is a built-in capabil
 - UAE Central 
 - UAE North 
 - UK South 
-- UK West 
+- UK West
+- US Gov Arizona
+- US Gov Texas
+- US Gov Virginia  
 - West Europe 
 - West US 
 - West US 2 

articles/azure-netapp-files/azure-government.md

@@ -6,7 +6,7 @@ author: b-hchen
 ms.service: azure-netapp-files
 ms.custom: devx-track-azurecli, no-azure-ad-ps-ref
 ms.topic: concept-article
-ms.date: 02/02/2026
+ms.date: 03/17/2026
 ms.author: anfdocs
 # Customer intent: As a government IT administrator, I want to understand how to access and utilize Azure NetApp Files in Azure Government, so that I can effectively manage mission-critical workloads within the dedicated cloud environment.
 ---
@@ -25,7 +25,6 @@ All [Azure NetApp Files features](whats-new.md) available on Azure public cloud
 
 | Azure NetApp Files features | Azure public cloud availability |  Azure Government availability |
 |:--- |:--- |:--- |
-| Advanced ransomware protection | Preview | No |
 | Customer-managed keys with managed Hardware Security Module | Generally available | No |
 | Elastic zone-redundant storage service level | Preview | No |
 | File access logs | Generally available | [Partial support](manage-file-access-logs.md#supported-regions) |

articles/azure-netapp-files/azure-netapp-files-metrics.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 01/16/2026
+ms.date: 03/16/2026
 ms.author: anfdocs
 # Customer intent: As a cloud storage administrator, I want to analyze performance and usage metrics for Azure NetApp Files, so that I can optimize storage provisioning and ensure efficient operation of my storage resources.
 ---
@@ -314,7 +314,7 @@ Azure NetApp Files provides metrics on allocated storage, actual storage usage,
     The delay between when data is written to the source volume and when it’s available on the destination volume.
 
 > [!NOTE]
-> When assessing the health status of the volume replication, consider the volume replication lag time. If the lag time is greater than the replication schedule, the replication volume won't catch up to the source. To resolve this issue, adjust the replication speed or the replication schedule. 
+> When assessing the health status of the volume replication, consider the volume replication lag time. If the lag time is greater than the replication schedule, the replication volume won't catch up to the source. To resolve this issue, adjust the replication schedule. 
 
 - *Volume replication last transfer duration*   
     The time taken for the most recent replication session to transfer all changed data (example: blocks, snapshots) from the source volume to the destination volume.