Updating Section Names, ENV usage

mrm9084 · mrm9084 · commit 01b4f38357b3 · 2023-03-21T15:09:23.000-07:00
diff --git a/articles/azure-app-configuration/TOC.yml b/articles/azure-app-configuration/TOC.yml
@@ -35,7 +35,7 @@
           href: quickstart-feature-flag-aspnet-core.md
         - name: .NET Framework
           href: quickstart-feature-flag-dotnet.md
-        - name: Azure Functions in .NET Core 
+        - name: Azure Functions in .NET Core
           href: quickstart-feature-flag-azure-functions-csharp.md
         - name: Java Spring
           href: quickstart-feature-flag-spring-boot.md
@@ -140,7 +140,7 @@
       href: concept-app-configuration-event.md
     - name: Soft delete
       href: concept-soft-delete.md
-    - name: Geo-replication 
+    - name: Geo-replication
       href: concept-geo-replication.md
     - name: Reliability
       items:
@@ -180,16 +180,16 @@
       href: howto-integrate-azure-managed-service-identity.md
     - name: Update to the New Spring Boot Library
       href: howto-convert-to-the-new-spring-boot.md
-    - name: Move a resource between Azure regions 
+    - name: Move a resource between Azure regions
       href: howto-move-resource-between-regions.md
     - name: Recover or purge deleted App Configuration stores
       href: howto-recover-deleted-stores-in-azure-app-configuration.md
-    - name: Enable geo-replication (Preview)
+    - name: Enable geo-replication
       href: howto-geo-replication.md
     - name: Disable public access
       href: howto-disable-public-access.md
     - name: Set up private access
-      href: howto-set-up-private-access.md   
+      href: howto-set-up-private-access.md
 - name: Reference
   items:
     - name: Client libraries
@@ -236,46 +236,46 @@
               href: rest-api.md
             - name: Resources
               items:
-              - name: Keys
-                href: ./rest-api-keys.md
-              - name: Key-values
-                href: ./rest-api-key-value.md
-              - name: Labels
-                href: ./rest-api-labels.md
-              - name: Locks
-                href: ./rest-api-locks.md
-              - name: Revisions
-                href: ./rest-api-revisions.md
+                - name: Keys
+                  href: ./rest-api-keys.md
+                - name: Key-values
+                  href: ./rest-api-key-value.md
+                - name: Labels
+                  href: ./rest-api-labels.md
+                - name: Locks
+                  href: ./rest-api-locks.md
+                - name: Revisions
+                  href: ./rest-api-revisions.md
             - name: Protocol
               items:
-              - name: Authentication
-                href: ./rest-api-authentication-index.md
-                items:
-                  - name: Azure Active Directory authentication
-                    href: rest-api-authentication-azure-ad.md
-                  - name: HMAC Authentication
-                    href: rest-api-authentication-hmac.md
-              - name: Authorization
-                href: ./rest-api-authorization-index.md
-                items:
-                  - name: Azure Active Directory authorization
-                    href: rest-api-authorization-azure-ad.md
-                  - name: HMAC authorization
-                    href: rest-api-authorization-hmac.md
-              - name: Consistency model
-                href: ./rest-api-consistency.md
-              - name: Common headers
-                href: ./rest-api-headers.md
-              - name: Throttling
-                href: ./rest-api-throttling.md
-              - name: Versioning
-                href: ./rest-api-versioning.md
+                - name: Authentication
+                  href: ./rest-api-authentication-index.md
+                  items:
+                    - name: Azure Active Directory authentication
+                      href: rest-api-authentication-azure-ad.md
+                    - name: HMAC Authentication
+                      href: rest-api-authentication-hmac.md
+                - name: Authorization
+                  href: ./rest-api-authorization-index.md
+                  items:
+                    - name: Azure Active Directory authorization
+                      href: rest-api-authorization-azure-ad.md
+                    - name: HMAC authorization
+                      href: rest-api-authorization-hmac.md
+                - name: Consistency model
+                  href: ./rest-api-consistency.md
+                - name: Common headers
+                  href: ./rest-api-headers.md
+                - name: Throttling
+                  href: ./rest-api-throttling.md
+                - name: Versioning
+                  href: ./rest-api-versioning.md
             - name: Development
               items:
-              - name: Fiddler
-                href: ./rest-api-fiddler.md
-              - name: Postman
-                href: ./rest-api-postman.md
+                - name: Fiddler
+                  href: ./rest-api-fiddler.md
+                - name: Postman
+                  href: ./rest-api-postman.md
         - name: Azure CLI
           href: /cli/azure/appconfig
     - name: Deployment
diff --git a/articles/azure-app-configuration/concept-disaster-recovery.md b/articles/azure-app-configuration/concept-disaster-recovery.md
@@ -11,7 +11,7 @@ ms.date: 07/09/2020
 # Resiliency and disaster recovery
 
 > [!IMPORTANT]
-> Azure App Configuration added [geo-replication](./concept-geo-replication.md) support recently. You can enable replicas of your data across multiple locations for enhanced resiliency to regional outages. You can also leverage App Configuration provider libraries in your applications for [automatic failover](./howto-geo-replication.md#use-replicas-aad). The geo-replication feature is currently under preview. It will be the recommended solution for high availability when the feature is generally available.
+> Azure App Configuration added [geo-replication](./concept-geo-replication.md) support recently. You can enable replicas of your data across multiple locations for enhanced resiliency to regional outages. You can also leverage App Configuration provider libraries in your applications for [automatic failover](./howto-geo-replication.md#use-replicas). The geo-replication feature is currently under preview. It will be the recommended solution for high availability when the feature is generally available.
 
 Currently, Azure App Configuration is a regional service. Each configuration store is created in a particular Azure region. A region-wide outage affects all stores in that region. App Configuration doesn't offer automatic failover to another region. This article provides general guidance on how you can use multiple configuration stores across Azure regions to increase the geo-resiliency of your application.
 
diff --git a/articles/azure-app-configuration/howto-backup-config-store.md b/articles/azure-app-configuration/howto-backup-config-store.md
@@ -17,13 +17,13 @@ ms.author: avgupta
 
 # Back up App Configuration stores automatically
 
+> [!IMPORTANT]
+> Azure App Configuration added [geo-replication](./concept-geo-replication.md) support recently. You can enable replicas of your data across multiple locations for enhanced resiliency to regional outages. You can also leverage App Configuration provider libraries in your applications for [automatic failover](./howto-geo-replication.md#use-replicas). The geo-replication feature is currently under preview. It will be the recommended solution for high availability when the feature is generally available.
+
 In this article, you'll learn how to set up an automatic backup of key-values from a primary Azure App Configuration store to a secondary store. The automatic backup uses the integration of Azure Event Grid with App Configuration.
 
 After you set up the automatic backup, App Configuration will publish events to Azure Event Grid for any changes made to key-values in a configuration store. Event Grid supports various Azure services from which users can subscribe to the events emitted whenever key-values are created, updated, or deleted.
 
-> [!IMPORTANT]
-> Azure App Configuration added [geo-replication](./concept-geo-replication.md) support recently. You can enable replicas of your data across multiple locations for enhanced resiliency to regional outages. You can also leverage App Configuration provider libraries in your applications for [automatic failover](./howto-geo-replication.md#use-replicas-aad). The geo-replication feature is currently under preview. It will be the recommended solution for high availability when the feature is generally available.
-
 ## Overview
 
 In this article, you'll use Azure Queue storage to receive events from Event Grid and use a timer-trigger of Azure Functions to process events in the queue in batches.
diff --git a/articles/azure-app-configuration/howto-geo-replication.md b/articles/azure-app-configuration/howto-geo-replication.md
@@ -84,15 +84,17 @@ To delete a replica in the portal, follow the steps below.
 
 --- -->
 
-## Use replicas with AAD
+## Use replicas
 
 Each replica you create has its dedicated endpoint. If your application resides in multiple geolocations, you can update each deployment of your application in a location to connect to the replica closer to that location, which helps minimize the network latency between your application and App Configuration. Since each replica has its separate request quota, this setup also helps the scalability of your application while it grows to a multi-region distributed service.
 
 When geo-replication is enabled, and if one replica isn't accessible, you can let your application failover to another replica for improved resiliency. App Configuration provider libraries have built-in failover support by accepting multiple replica endpoints. You can provide a list of your replica endpoints in the order of the most preferred to the least preferred endpoint. When the current endpoint isn't accessible, the provider library will fail over to a less preferred endpoint, but it will try to connect to the more preferred endpoints from time to time. When a more preferred endpoint becomes available, it will switch to it for future requests.
 
-Assuming you have an application using Azure App Configuration, you can update it as the following sample code to take advantage of the failover feature.
+Assuming you have an application using Azure App Configuration, you can update it as the following sample code to take advantage of the failover feature. You can either provide a list of endpoints for AAD authentication or a list of connection strings for access key-based authentication.
 
-### [.NET](#tab/dotnet)
+### With AAD
+
+#### [.NET](#tab/dotnet)
 
 Edit the call to the `AddAzureAppConfiguration` method, which is often found in the `program.cs` file of your application.
 
@@ -117,7 +119,7 @@ configurationBuilder.AddAzureAppConfiguration(options =>
 > - `Microsoft.Azure.AppConfiguration.AspNetCore`
 > - `Microsoft.Azure.AppConfiguration.Functions.Worker`
 
-### [Java Spring](#tab/spring)
+#### [Java Spring](#tab/spring)
 
 Edit the endpoint configuration in `bootstrap.properties`, to use endpoints which allows a list of endpoints.
 
@@ -133,11 +135,9 @@ spring.cloud.azure.appconfiguration.stores[0].endpoints[1]="<second-replica-endp
 
 ---
 
-## Use replicas with Access Keys
-
-If you are using access keys to connect to your App Configuration store, you can use the failover feature by providing a list of replica connection strings in the order of the most preferred to the least preferred endpoint. When the current endpoint isn't accessible, the provider library will fail over to a less preferred endpoint, but it will try to connect to the more preferred endpoints from time to time. When a more preferred endpoint becomes available, it will switch to it for future requests.
+### With Access Keys
 
-### [.NET](#tab/dotnet)
+#### [.NET](#tab/dotnet)
 
 Edit the call to the `AddAzureAppConfiguration` method, which is often found in the `program.cs` file of your application.
 
@@ -160,13 +160,13 @@ configurationBuilder.AddAzureAppConfiguration(options =>
 > - `Microsoft.Azure.AppConfiguration.AspNetCore`
 > - `Microsoft.Azure.AppConfiguration.Functions.Worker`
 
-### [Java Spring](#tab/spring)
+#### [Java Spring](#tab/spring)
 
 Edit the connection string configuration in `bootstrap.properties`, to use connection strings which allows a list of connection strings.
 
 ```properties
-spring.cloud.azure.appconfiguration.stores[0].connection-strings[0]="<first-replica-connection-string>"
-spring.cloud.azure.appconfiguration.stores[0].connection-strings[1]="<second-replica-connection-string>"
+spring.cloud.azure.appconfiguration.stores[0].connection-strings[0]="${FIRST_REPLICA_CONNECTION_STRING}"
+spring.cloud.azure.appconfiguration.stores[0].connection-strings[1]="${SECOND_REPLICA_CONNECTION_STRING}"
 ```
 
 > [!NOTE]
