Merge pull request #292102 from zhenlan/endpoint

Fix the code for endpoint retrieval

Author: prmerger-automator[bot]

articles/azure-app-configuration/quickstart-aspnet-core-app.md

@@ -64,12 +64,6 @@ Connect to your App Configuration store using Microsoft Entra ID (recommended),
     ```
     ---
 
-1. Run the following command to restore packages for your project:
-
-    ```dotnetcli
-    dotnet restore
-    ```
-
 1. Create a user secret for the application by navigating into the *TestAppConfig* folder and running the following command.
 
     ### [Microsoft Entra ID (recommended)](#tab/entra-id)
@@ -83,11 +77,11 @@ Connect to your App Configuration store using Microsoft Entra ID (recommended),
     
     ### [Connection string](#tab/connection-string)
 
-    The command uses [Secret Manager](/aspnet/core/security/app-secrets) to store a secret named `ConnectionStrings:AppConfig`, which stores the connection string for your App Configuration store. Replace the `<your_connection_string>` placeholder with your App Configuration store's connection string. You can find the connection string in your App Configuration store's **Access settings** in the Azure portal.
+    The command uses [Secret Manager](/aspnet/core/security/app-secrets) to store a secret named `ConnectionStrings:AppConfiguration`, which stores the connection string for your App Configuration store. Replace the `<your-App-Configuration-connection-string>` placeholder with your App Configuration store's read-only connection string. You can find the connection string in your App Configuration store's **Access settings** in the Azure portal.
 
     ```dotnetcli
     dotnet user-secrets init
-    dotnet user-secrets set ConnectionStrings:AppConfig "<your_connection_string>"
+    dotnet user-secrets set ConnectionStrings:AppConfiguration "<your-App-Configuration-connection-string>"
     ```
 
     > [!TIP]
@@ -124,15 +118,16 @@ Connect to your App Configuration store using Microsoft Entra ID (recommended),
     var builder = WebApplication.CreateBuilder(args); 
     
     // Retrieve the endpoint
-    string endpoint = builder.Configuration.Get("Endpoints:AppConfiguration");
-    
+    string endpoint = builder.Configuration.GetValue<string>("Endpoints:AppConfiguration")
+        ?? throw new InvalidOperationException("The setting `Endpoints:AppConfiguration` was not found.");
+
     // Load configuration from Azure App Configuration 
     builder.Configuration.AddAzureAppConfiguration(options =>
     {
         options.Connect(new Uri(endpoint), new DefaultAzureCredential());
     });
     
-     // The rest of existing code in program.cs
+    // The rest of existing code in program.cs
     // ... ...    
     ```
 
@@ -142,7 +137,8 @@ Connect to your App Configuration store using Microsoft Entra ID (recommended),
     var builder = WebApplication.CreateBuilder(args);
 
     // Retrieve the connection string
-    string connectionString = builder.Configuration.GetConnectionString("AppConfig");
+    string connectionString = builder.Configuration.GetConnectionString("AppConfiguration")
+        ?? throw new InvalidOperationException("The connection string 'AppConfiguration' was not found.");
 
     // Load configuration from Azure App Configuration
     builder.Configuration.AddAzureAppConfiguration(connectionString);

articles/azure-app-configuration/use-variant-feature-flags-aspnet-core.md

@@ -1,17 +1,17 @@
 ---
-title: 'Tutorial: Use variant feature flags from Azure App Configuration in an ASP.NET application'
+title: 'Tutorial: Use variant feature flags from Azure App Configuration in an ASP.NET Core application'
 titleSuffix: Azure App configuration
-description: In this tutorial, you learn how to use variant feature flags in an ASP.NET application
+description: In this tutorial, you learn how to use variant feature flags in an ASP.NET Core application
 #customerintent: As a user of Azure App Configuration, I want to learn how I can use variants and variant feature flags in my ASP.NET application.
 author: rossgrambo
 ms.author: rossgrambo
 ms.service: azure-app-configuration
 ms.devlang: csharp
 ms.topic: tutorial
-ms.date: 10/18/2024
+ms.date: 12/18/2024
 ---
 
-# Tutorial: Use variant feature flags from Azure App Configuration in an ASP.NET application
+# Tutorial: Use variant feature flags in an ASP.NET Core application
 
 In this tutorial, you use a variant feature flag to manage experiences for different user segments in an example application, *Quote of the Day*. You utilize the variant feature flag created in [Use variant feature flags](./use-variant-feature-flags.md). Before proceeding, ensure you create the variant feature flag named *Greeting* in your App Configuration store.
 
@@ -28,10 +28,11 @@ In this tutorial, you use a variant feature flag to manage experiences for diffe
     dotnet new razor --auth Individual -o QuoteOfTheDay
     ```
 
-1. Create a [user secret](/aspnet/core/security/app-secrets) for the application by navigating into the *QuoteOfTheDay* folder and run the following command. This secret holds the endpoint for your App Configuration.
+1. Navigate to the *QuoteOfTheDay* directory and create a [user secret](/aspnet/core/security/app-secrets) for the application by running the following commands. Replace the `<your-App-Configuration-endpoint>` placeholder with your App Configuration store's endpoint. You can find the endpoint in your App Configuration store's **Overview** blade in the Azure portal.
 
     ```dotnetcli
-    dotnet user-secrets set Endpoints:AppConfiguration "<App Configuration Endpoint>"
+    dotnet user-secrets init
+    dotnet user-secrets set Endpoints:AppConfiguration "<your-App-Configuration-endpoint>"
     ```
 
 1. Add the latest versions of the required packages.
@@ -44,26 +45,31 @@ In this tutorial, you use a variant feature flag to manage experiences for diffe
 
 ## Connect to App Configuration for feature management
 
-1. In *Program.cs*, add the following using statements.
+1. Open *Program.cs* and add the following using statements.
 
     ```csharp
     using Azure.Identity;
     using Microsoft.Extensions.Configuration.AzureAppConfiguration;
     using Microsoft.FeatureManagement;
     ```
 
-1. In *Program.cs*, under the line `var builder = WebApplication.CreateBuilder(args);`, add the App Configuration provider, which pulls down the configuration from Azure App Configuration when the application starts. By default, the `UseFeatureFlags` method pulls down all feature flags with no label.
+1. Add the following code to connect to your App Configuration store and call `UseFeatureFlags` to pull down all feature flags with no label.
 
     You use the `DefaultAzureCredential` to authenticate to your App Configuration store. Follow the [instructions](./concept-enable-rbac.md#authentication-with-token-credentials) to assign your credential the **App Configuration Data Reader** role. Be sure to allow sufficient time for the permission to propagate before running your application.
 
     ```csharp
+    var builder = WebApplication.CreateBuilder(args); 
+
+    // Retrieve the endpoint
+    string endpoint = builder.Configuration.GetValue<string>("Endpoints:AppConfiguration")
+        ?? throw new InvalidOperationException("The setting `Endpoints:AppConfiguration` was not found.");
+
+    // Load configuration and feature flags from Azure App Configuration
     builder.Configuration
         .AddAzureAppConfiguration(options =>
         {
-            string endpoint = builder.Configuration.Get("Endpoints:AppConfiguration");
-            options.Connect(new Uri(endpoint), new DefaultAzureCredential());
-
-            options.UseFeatureFlags();
+            options.Connect(new Uri(endpoint), new DefaultAzureCredential())
+                   .UseFeatureFlags();
         });
     ```