Merge pull request #231448 from mrm9084/AppConfigurationGeoReplication

App Configuration Geo Replication GA How To

Author: denrea

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

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). 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 supports [geo-replication](./concept-geo-replication.md). 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). Utilizing geo-replication is the recommended solution for high availability.
 
 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.
 

articles/azure-app-configuration/concept-geo-replication.md

@@ -1,5 +1,5 @@
 ---
-title: Geo-replication in Azure App Configuration (Preview)
+title: Geo-replication in Azure App Configuration
 description: Details of the geo-replication feature in Azure App Configuration. 
 author: maud-lv
 ms.author: malev
@@ -9,11 +9,11 @@ ms.topic: conceptual
 ms.date: 08/01/2022
 ---
 
-# Geo-replication overview (Preview)
+# Geo-replication overview
 
 For application developers and IT engineers, a common goal is to build and run resilient applications. Resiliency is defined as the ability of your application to react to failure and still remain functional. To achieve resilience in the face of regional failures in the cloud, the first step is to build in redundancy to avoid a single point of failure. This redundancy can be achieved with geo-replication.
 
-The App Configuration geo-replication feature allows you to replicate your configuration store at-will to the regions of your choice.  Each new **replica** will be in a different region and creates a new endpoint for your applications to send requests to. The original endpoint of your configuration store is called the **Origin**. The origin can't be removed, but otherwise behaves like any replica. 
+The App Configuration geo-replication feature allows you to replicate your configuration store at-will to the regions of your choice. Each new **replica** will be in a different region and creates a new endpoint for your applications to send requests to. The original endpoint of your configuration store is called the **Origin**. The origin can't be removed, but otherwise behaves like any replica. 
 
 Changing or updating your key-values can be done in any replica. These changes will be synchronized with all other replicas following an eventual consistency model. 
 
@@ -35,7 +35,6 @@ This team would benefit from geo-replication. They can create a replica of their
 - Geo-replication isn't available in the free tier.  
 - Each replica has limits, as outlined in the [App Configuration pricing page](https://azure.microsoft.com/pricing/details/app-configuration/). These limits are isolated per replica. 
 - Azure App Configuration also supports Azure availability zones to create a resilient and highly available store within an Azure Region. Availability zone support is automatically included for a replica if the replica's region has availability zone support. The combination of availability zones for redundancy within a region, and geo-replication across multiple regions, enhances both the availability and performance of a configuration store.
-- Currently, you can only authenticate with replica endpoints with [Azure Active Directory (Azure AD)](../app-service/overview-managed-identity.md).
 <!--
 To add once these links become available: 
  - Request handling for replicas will vary by configuration provider, for further information reference [.NET Geo-replication Reference](https://azure.microsoft.com/pricing/details/app-configuration/) and [Java Geo-replication Reference](https://azure.microsoft.com/pricing/details/app-configuration/). 
@@ -50,4 +49,4 @@ Each replica created will add extra charges. Reference the [App Configuration pr
 > [!div class="nextstepaction"]
 > [How to enable Geo replication](./howto-geo-replication.md)  
 
-> [Resiliency and Disaster Recovery](./concept-disaster-recovery.md)
+> [Resiliency and Disaster Recovery](./concept-disaster-recovery.md)

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 supports [geo-replication](./concept-geo-replication.md). 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). Utilizing geo-replication is the recommended solution for high availability.
+
 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). 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.

articles/azure-app-configuration/howto-geo-replication.md

@@ -1,19 +1,19 @@
 ---
-title: Enable geo-replication (preview)
+title: Enable geo-replication
 description: Learn how to use Azure App Configuration geo replication to create, delete, and manage replicas of your configuration store. 
 services: azure-app-configuration
 author: mrm9084
 ms.service: azure-app-configuration
 ms.devlang: csharp, java
 ms.topic: how-to
-ms.date: 10/10/2022
+ms.date: 03/20/2023
 ms.author: mametcal
 ms.custom: devx-track-azurecli
 
 #Customer intent: I want to be able to list, create, and delete the replicas of my configuration store. 
 ---
 
-# Enable geo-replication (Preview)
+# Enable geo-replication
 
 This article covers replication of Azure App Configuration stores. You'll learn about how to create, use and delete a replica in your configuration store.
 
@@ -90,49 +90,69 @@ Each replica you create has its dedicated endpoint. If your application resides
 
 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.
-
-> [!NOTE]
-> You can only use Azure AD authentication to connect to replicas. Authentication with access keys is not supported during the preview.
+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 Azure Active Directory (Azure AD) authentication or a list of connection strings for access key-based authentication.
 
 ### [.NET](#tab/dotnet)
 
 Edit the call to the `AddAzureAppConfiguration` method, which is often found in the `program.cs` file of your application.
 
+**Connect with Azure AD**
+
 ```csharp
 configurationBuilder.AddAzureAppConfiguration(options =>
 {
     // Provide an ordered list of replica endpoints
     var endpoints = new Uri[] {
-        new Uri("https://<first-replica-endpoint>.azconfig.io"),
-        new Uri("https://<second-replica-endpoint>.azconfig.io") };
+        new Uri("<first-replica-endpoint>"),
+        new Uri("<second-replica-endpoint>") };
 
-    // Connect to replica endpoints using AAD authentication
+    // Connect to replica endpoints using Azure AD authentication
     options.Connect(endpoints, new DefaultAzureCredential());
 
     // Other changes to options
 });
 ```
 
+**Connect with Connection String**
+
+```csharp
+configurationBuilder.AddAzureAppConfiguration(options =>
+{
+    // Provide an ordered list of replica connection strings
+    var connectionStrings = new string[] {
+        Environment.GetEnvironmentVariable("FIRST_REPLICA_CONNECTION_STRING"),
+        Environment.GetEnvironmentVariable("SECOND_REPLICA_CONNECTION_STRING") };
+    
+    // Connect to replica endpoints using connection strings
+    options.Connect(connectionStrings);
+
+    // Other changes to options
+});
+```
+
 > [!NOTE]
-> The failover support is available if you use version **5.3.0-preview** or later of any of the following packages.
+> The failover support is available if you use version **6.0.0** or later of any of the following packages.
 > - `Microsoft.Extensions.Configuration.AzureAppConfiguration`
 > - `Microsoft.Azure.AppConfiguration.AspNetCore`
 > - `Microsoft.Azure.AppConfiguration.Functions.Worker`
 
 ### [Java Spring](#tab/spring)
 
-Edit the endpoint configuration in `bootstrap.properties`, to use endpoints which allows a list of endpoints.
+Edit the `endpoints` or `connection-strings` properties in the `bootstrap.properties` file of your application.
+
+**Connect with Azure AD**
 
 ```properties
-spring.cloud.azure.appconfiguration.stores[0].endpoints[0]="https://<first-replica-endpoint>.azconfig.io"
-spring.cloud.azure.appconfiguration.stores[0].endpoints[1]="https://<second-replica-endpoint>.azconfig.io"
+spring.cloud.azure.appconfiguration.stores[0].endpoints[0]="<first-replica-endpoint>"
+spring.cloud.azure.appconfiguration.stores[0].endpoints[1]="<second-replica-endpoint>"
 ```
+
+
 > [!NOTE]
-> The failover support is available if you use version of **2.10.0-beta.1** or later of any of the following packages.
-> - `azure-spring-cloud-appconfiguration-config`
-> - `azure-spring-cloud-appconfiguration-config-web`
-> - `azure-spring-cloud-starter-appconfiguration-config`
+> The failover support is available if you use version of **4.0.0-beta.1** or later of any of the following packages.
+> - `spring-cloud-azure-appconfiguration-config`
+> - `spring-cloud-azure-appconfiguration-config-web`
+> - `spring-cloud-azure-starter-appconfiguration-config`
 
 ---