Merge pull request #294506 from MicrosoftDocs/main

Publish to live, Wednesday 4AM PST, 2/12

Author: PMEds28

articles/automation/how-to/automation-region-dns-records.md

@@ -10,7 +10,7 @@ ms.service: azure-automation
 
 # DNS records for Azure regions used by Azure Automation
 
-The [Azure Automation](../automation-intro.md) service uses many DNS (Domain Name System) records for features to connect to the service. If you have an Automation account configured for a specific region, you can restrict communication to that regional datacenter. You might need to know these records to allow the following Automation features to work when it's hosted behind a firewall:
+The [Azure Automation](../automation-intro.md) service uses many Domain Name System (DNS) records for features to connect to the service. If you have an Automation account configured for a specific region, you can restrict communication to that regional datacenter. You might need to know these records to allow the following Automation features to work when it's hosted behind a firewall:
 
 * Hybrid Runbook Worker
 * State Configuration

articles/azure-app-configuration/TOC.yml

@@ -310,6 +310,8 @@
       href: https://go.microsoft.com/fwlink/?linkid=2180917
     - name: Python provider
       href: https://pypi.org/project/azure-appconfiguration-provider/
+    - name: JavaScript provider
+      href: ./reference-javascript-provider.md
     - name: Azure SDK for .NET
       href: https://go.microsoft.com/fwlink/?linkid=2092056
     - name: Azure SDK for Java

articles/azure-app-configuration/enable-dynamic-configuration-javascript.md

@@ -221,3 +221,8 @@ In this tutorial, you enabled your JavaScript app to dynamically refresh configu
 
 > [!div class="nextstepaction"]
 > [Managed identity integration](./howto-integrate-azure-managed-service-identity.md)
+
+For the full feature rundown of the JavaScript configuration provider library, continue to the following document.
+
+> [!div class="nextstepaction"]
+> [JavaScript configuration provider](./reference-javascript-provider.md)

articles/azure-app-configuration/feature-management-dotnet-reference.md

@@ -1191,8 +1191,6 @@ ActivitySource.AddActivityListener(new ActivityListener()
 
 For more information, please go to [Collect a distributed trace](/dotnet/core/diagnostics/distributed-tracing-collection-walkthroughs).
 
-
-
 ### Application Insights Telemetry
 
 The `Microsoft.FeatureManagement.Telemetry.ApplicationInsights` package provides a built-in telemetry publisher that sends feature flag evaluation data to [Application Insights](/azure/azure-monitor/app/app-insights-overview). The `Microsoft.FeatureManagement.Telemetry.ApplicationInsights` package also provides a telemetry initializer that automatically tags all events with `TargetingId` so that events may be linked to flag evaluations. To take advantage of this, add a reference to the package and register the Application Insights telemetry as in the following example.

articles/azure-app-configuration/index.yml

@@ -188,7 +188,7 @@ landingContent:
         - text: Python provider
           url: https://pypi.org/project/azure-appconfiguration-provider/
         - text: JavaScript provider
-          url: https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/appconfiguration/app-configuration
+          url: reference-javascript-provider.md
         - text: Kubernetes provider
           url: reference-kubernetes-provider.md
       - linkListType: reference

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,33 +45,63 @@ Add the following key-value to the App Configuration store and leave **Label** a
 
 ## Connect to an App Configuration store
 
-1. Right-click your project, and select **Manage NuGet Packages**. On the **Browse** tab, search and add the following NuGet packages to your project.
+Connect to your App Configuration store using Microsoft Entra ID (recommended), or a connection string.
 
-    - *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
+1. Right-click your project, and select **Manage NuGet Packages**. On the **Browse** tab, search and add the latest stable versions of following NuGet packages to your project.
 
-1. Update the *App.config* file of your project as follows:
+    - Microsoft.Configuration.ConfigurationBuilders.AzureAppConfiguration
+    - Microsoft.Configuration.ConfigurationBuilders.Environment
+    - System.Configuration.ConfigurationManager
 
+1. Update the *App.config* file of your project as follows. You can connect to your App Configuration store using Microsoft Entra ID (recommended), or a connection string.
+
+    ### [Microsoft Entra ID (recommended)](#tab/entra-id)
+    
+    The `DefaultAzureCredential` is used to authenticate to your App Configuration store by default. 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" endpoint="${Endpoint}" 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="Endpoint" value ="Set via an environment variable - for example, dev, test, staging, or production endpoint." />
+    </appSettings>
+    ```
+    
+    The endpoint value of your App Configuration store is read from the environment variable `Endpoint`. You also add the `Environment` configuration builder before the `MyConfigStore` in the `configBuilders` property of the `appSettings` section.
+    
+    ### [Connection string](#tab/connection-string)
+    
+    ```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.
+    
+    The connection string of your App Configuration store is read from the environment variable `ConnectionString`. You also 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`.
 
@@ -87,7 +117,33 @@ 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 an environment variable named **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 Endpoint "<endpoint-of-your-app-configuration-store>"
+    ```
+
+    If you use PowerShell, run the following command:
+
+    ```powershell
+    $Env:Endpoint = "<endpoint-of-your-app-configuration-store>"
+    ```
+
+    If you use macOS or Linux, run the following command:
+
+    ```bash
+    export Endpoint='<endpoint-of-your-app-configuration-store>'
+    ```
+
+    ### [Connection string](#tab/connection-string)
+
+   Set an environment variable named **ConnectionString** to the read-only connection string of your App Configuration store found under **Access settings** of your store in the Azure portal.
 
     If you use the Windows command prompt, run the following command:
 
@@ -101,6 +157,13 @@ Add the following key-value to the App Configuration store and leave **Label** a
     $Env:ConnectionString = "<connection-string-of-your-app-configuration-store>"
     ```
 
+    If you use macOS or Linux, run the following command:
+
+    ```bash
+    export ConnectionString='<connection-string-of-your-app-configuration-store>'
+    ```
+    ---
+
 1. Restart Visual Studio to allow the change to take effect.
 
 1. Press Ctrl + F5 to build and run the console app. You should see the message from App Configuration outputs in the console.

articles/azure-app-configuration/quickstart-javascript-provider.md

@@ -408,4 +408,9 @@ run().catch(console.error);
 In this quickstart, you created a new App Configuration store and learned how to access key-values using the App Configuration JavaScript provider in a Node.js app. To learn how to configure your app to dynamically refresh configuration settings, continue to the next tutorial.
 
 > [!div class="nextstepaction"]
-> [Enable dynamic configuration](./enable-dynamic-configuration-javascript.md)
+> [Enable dynamic configuration](./enable-dynamic-configuration-javascript.md)
+
+For the full feature rundown of the JavaScript configuration provider library, continue to the following document.
+
+> [!div class="nextstepaction"]
+> [JavaScript configuration provider](./reference-javascript-provider.md)