Initial commit

Author: maud-lv

articles/azure-app-configuration/quickstart-dotnet-app.md

@@ -7,16 +7,16 @@ ms.service: azure-app-configuration
 ms.devlang: csharp
 ms.custom: devx-track-csharp, mode-other, devx-track-dotnet
 ms.topic: quickstart
-ms.date: 05/24/2024
+ms.date: 02/04/2025
 ms.author: malev
 #Customer intent: As a .NET Framework developer, I want to manage all my app settings in one place.
 ---
 # Quickstart: Create a .NET Framework app with Azure App Configuration
 
 There are two ways to incorporate Azure App Configuration into a .NET Framework-based app.
 
-- The configuration builder for App Configuration enables data from App Configuration to be loaded to App Settings. Your app accesses configuration as it always does via `ConfigurationManager`. You don't need to make any code change other than updates to *app.config* or *web.config* files. This quickstart will walk you through this option.
-- As is designed by the .NET Framework, the App Settings can only refresh upon application restart. The App Configuration .NET provider is a .NET Standard library. It supports caching and refreshing configuration dynamically without application restart. If the dynamic configuration is essential to you and you are willing to make code changes, see tutorials on how you can implement dynamic configuration updates in a [.NET Framework console app](./enable-dynamic-configuration-dotnet.md) or an [ASP.NET web app](./enable-dynamic-configuration-aspnet-netfx.md).
+- The configuration builder for App Configuration enables data from App Configuration to be loaded to App Settings. Your app accesses configuration as it always does via `ConfigurationManager`. You don't need to make any code change other than updates to *app.config* or *web.config* files. This quickstart walks you through this option.
+- As is designed by the .NET Framework, the App Settings can only refresh upon application restart. The App Configuration .NET provider is a .NET Standard library. It supports caching and refreshing configuration dynamically without application restart. If the dynamic configuration is essential to you and you're willing to make code changes, see tutorials on how you can implement dynamic configuration updates in a [.NET Framework console app](./enable-dynamic-configuration-dotnet.md) or an [ASP.NET web app](./enable-dynamic-configuration-aspnet-netfx.md).
 
 In this quickstart, a .NET Framework console app is used as an example, but the same technique applies to an ASP.NET Web Forms/MVC app.
 
@@ -45,6 +45,53 @@ Add the following key-value to the App Configuration store and leave **Label** a
 
 ## Connect to an App Configuration store
 
+Connect to your App Configuration store using Microsoft Entra ID (recommended), or a connection string.
+
+### [Microsoft Entra ID (recommended)](#tab/entra-id)
+
+1. Right-click your project, and select **Manage NuGet Packages**. On the **Browse** tab, search and add the following NuGet packages to your project.
+
+    - *Microsoft.Configuration.ConfigurationBuilders.AzureAppConfiguration* version 1.0.0 or later
+    - *Microsoft.Configuration.ConfigurationBuilders.Environment* version 2.0.0 or later
+    - *System.Configuration.ConfigurationManager* version 4.6.0 or later
+    - * Azure.Identity* version 1.13.0 or later
+
+1. Update the *App.config* file of your project as follows. 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. 
+
+    ```xml
+    <configSections>
+        <section name="configBuilders" type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" restartOnExternalChanges="false" requirePermission="false" />
+    </configSections>
+
+    <configBuilders>
+        <builders>
+            <add name="MyConfigStore" mode="Greedy" connectionString="${ConnectionString}" type="Microsoft.Configuration.ConfigurationBuilders.AzureAppConfigurationBuilder, Microsoft.Configuration.ConfigurationBuilders.AzureAppConfiguration" />
+            <add name="Environment" mode="Greedy" type="Microsoft.Configuration.ConfigurationBuilders.EnvironmentConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Environment" />
+        </builders>
+    </configBuilders>
+
+    <appSettings configBuilders="Environment,MyConfigStore">
+        <add key="AppName" value="Console App Demo" />
+        <add key="ConnectionString" value ="Set via an environment variable - for example, dev, test, staging, or production connection string." />
+    </appSettings>
+    ```
+
+   The connection string of your App Configuration store is read from the environment variable `ConnectionString`. Add the `Environment` configuration builder before the `MyConfigStore` in the `configBuilders` property of the `appSettings` section.
+
+1. Open *Program.cs*, and update the `Main` method to use App Configuration by calling `ConfigurationManager`.
+
+    ```csharp
+    static void Main(string[] args)
+    {
+        string message = System.Configuration.ConfigurationManager.AppSettings["TestApp:Settings:Message"];
+
+        Console.WriteLine(message);
+        Console.ReadKey();
+    }
+    ```
+
+### [Connection string](#tab/connection-string)
+
 1. Right-click your project, and select **Manage NuGet Packages**. On the **Browse** tab, search and add the following NuGet packages to your project.
 
     - *Microsoft.Configuration.ConfigurationBuilders.AzureAppConfiguration* version 1.0.0 or later
@@ -85,9 +132,37 @@ Add the following key-value to the App Configuration store and leave **Label** a
     }
     ```
 
+---
+
 ## Build and run the app
 
-1. Set an environment variable named **ConnectionString** to the read-only key connection string obtained during your App Configuration store creation.
+1. Set an environment variable.
+
+    ### [Microsoft Entra ID (recommended)](#tab/entra-id)
+
+    Set the environment variable named **APP_CONFIGURATION_ENDPOINT** to the endpoint of your App Configuration store found under the *Overview* of your store in the Azure portal.
+
+    If you use the Windows command prompt, run the following command and restart the command prompt to allow the change to take effect:
+
+    ```cmd
+    setx APP_CONFIGURATION_ENDPOINT "<endpoint-of-your-app-configuration-store>"
+    ```
+
+    If you use PowerShell, run the following command:
+
+    ```powershell
+    $Env:APP_CONFIGURATION_ENDPOINT = "<endpoint-of-your-app-configuration-store>"
+    ```
+
+    If you use macOS or Linux, run the following command:
+
+    ```bash
+    export APP_CONFIGURATION_ENDPOINT='<endpoint-of-your-app-configuration-store>'
+    ```
+
+    ### [Connection string](#tab/connection-string)
+
+   Set an environment variable named **ConnectionString** to the read-only key connection string obtained during your App Configuration store creation.
 
     If you use the Windows command prompt, run the following command:
 
@@ -100,6 +175,7 @@ Add the following key-value to the App Configuration store and leave **Label** a
     ```powershell
     $Env:ConnectionString = "<connection-string-of-your-app-configuration-store>"
     ```
+    ---
 
 1. Restart Visual Studio to allow the change to take effect.