Merge pull request #296591 from maud-lv/ml-ac-entra-howto-labels-aspnet-core

Update authentication in snapshots and labels how-to articles

Author: prmerger-automator[bot]

articles/azure-app-configuration/howto-create-snapshots.md

@@ -5,7 +5,7 @@ author: Muksvso
 ms.author: mubatra
 ms.service: azure-app-configuration
 ms.topic: how-to 
-ms.date: 11/15/2023
+ms.date: 03/19/2025
 ---
 
 # Manage and use snapshots
@@ -96,8 +96,8 @@ Edit the call to the `AddAzureAppConfiguration` method, which is often found in
 ```csharp
 configurationBuilder.AddAzureAppConfiguration(options =>
 {
-    options.Connect(Environment.GetEnvironmentVariable("ConnectionString"));
-
+    string endpoint = Environment.GetEnvironmentVariable("Endpoint"); 
+    options.Connect(new Uri(endpoint), new DefaultAzureCredential());
     // Select an existing snapshot by name. This will add all of the key-values from the snapshot to this application's configuration.
     options.SelectSnapshot("SnapshotName");
 

articles/azure-app-configuration/howto-labels-aspnet-core.md

@@ -7,13 +7,13 @@ ms.devlang: csharp
 author: maud-lv
 ms.topic: conceptual
 ms.custom: devx-track-csharp
-ms.date: 02/20/2024
+ms.date: 03/19/2025
 ms.author: malev
 
 ---
 # Use labels to provide per-environment configuration values.
 
-Many applications need to use different configurations for different environments. Suppose that an application has a configuration value that defines the connection string to use for its back-end database. The application developers use a different database from the one used in production. The database connection string that the application uses must change as the application moves from development to production.
+Many applications need to use different configurations for different environments. Suppose that an application has a configuration value that defines the endpoint to use for its back-end database. The application developers use a different database from the one used in production. The database endpoint that the application uses must change as the application moves from development to production.
 
 In Azure App Configuration, you can use *labels* to define different values for the same key. For example, you can define a single key with different values for development and production. You can specify which label to load when connecting to App Configuration.
 
@@ -47,17 +47,15 @@ var builder = WebApplication.CreateBuilder(args);
 
 builder.Configuration.AddAzureAppConfiguration(options =>
     {
-            options.Connect(builder.Configuration.GetConnectionString("AppConfig"))
-                // Load configuration values with no label
-                .Select(KeyFilter.Any, LabelFilter.Null)
-                // Override with any configuration values specific to current hosting env
-                .Select(KeyFilter.Any, builder.Environment.EnvironmentName);
+        string endpoint = Environment.GetEnvironmentVariable("Endpoint");
+        options.Connect(new Uri(endpoint), new DefaultAzureCredential())
+               // Load configuration values with no label
+               .Select(KeyFilter.Any, LabelFilter.Null)
+               // Override with any configuration values specific to current hosting env
+               .Select(KeyFilter.Any, builder.Environment.EnvironmentName);
     });
 ```
 
-> [!IMPORTANT]
-> The preceding code snippet uses the Secret Manager tool to load App Configuration connection string. For information storing the connection string using the Secret Manager, see [Quickstart for Azure App Configuration with ASP.NET Core](quickstart-aspnet-core-app.md).
-
 The `Select` method is called twice. The first time, it loads configuration values with no label. Then, it loads configuration values with the label corresponding to the current environment. These environment-specific values override any corresponding values with no label. You don't need to define environment-specific values for every key. If a key doesn't have a value with a label corresponding to the current environment, it uses the value with no label.
 
 ## Test in different environments