Merge branch 'main' of https://github.com/zhiyuanliang-ms/azure-docs-pr into zhiyuanliang/js-provider-update

Author: zhiyuanliang-ms

articles/azure-app-configuration/configuration-provider-overview.md

@@ -70,7 +70,7 @@ Replica Failover | [GA](./reference-dotnet-provider.md#geo-replication) | GA | G
 Replica Load Balancing | [GA](./reference-dotnet-provider.md#geo-replication) | WIP | GA | GA | [GA](./reference-javascript-provider.md#geo-replication) | WIP
 Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | WIP | [GA](./reference-javascript-provider.md#snapshot) | WIP
 Distributed Tracing | [GA](./reference-dotnet-provider.md#distributed-tracing) | WIP | WIP | WIP | WIP | WIP
-Health Check | WIP | GA | WIP | WIP | WIP | WIP 
+Health Check | [GA](./reference-dotnet-provider.md#health-check) | GA | WIP | WIP | WIP | WIP 
 Select by Tag Filters | [GA](./reference-dotnet-provider.md#load-specific-key-values-using-selectors) | WIP | WIP | GA | [GA](./reference-javascript-provider.md#tag-filters) | WIP 
 
 ## Support policy

articles/azure-app-configuration/reference-dotnet-provider.md

@@ -673,6 +673,22 @@ builder.Services.AddOpenTelemetry()
 
 For more information about OpenTelemetry in .NET, see the [OpenTelemetry .NET documentation](https://github.com/open-telemetry/opentelemetry-dotnet).
 
+## Health check
+
+The Azure App Configuration .NET provider supports [.NET app health checks](/dotnet/core/diagnostics/diagnostic-health-checks). To enable health checks, you can call `AddAzureAppConfiguration()` method on `IHealthChecksBuilder`, which will add an `IHealthCheck` with a default registration name of `"Microsoft.Extensions.Configuration.AzureAppConfiguration"`.
+
+```C#
+builder.Configuration.AddAzureAppConfiguration(options => 
+    options.Connect(new Uri(appConfigEndpoint), new DefaultAzureCredential()));
+
+builder.Services.AddHealthChecks()
+    .AddAzureAppConfiguration();
+```
+
+The .NET provider will be considered as unhealthy when the last load or refresh attempt failed.
+
+For more information about health checks in .NET, see the [.NET health monitoring documentation](/dotnet/architecture/microservices/implement-resilient-applications/monitor-app-health).
+
 ## Next steps
 
 To learn how to use the .NET configuration provider, continue to the following tutorial.

articles/reliability/media/reliability-container-registry/multi-region-normal-operations.png

@@ -32,7 +32,7 @@ For production workloads, we recommend that you take the following actions:
 
 Container Registry is built on distributed Azure infrastructure to provide high availability and data durability. The service consists of several key components that work together to ensure reliability. The following diagram illustrates the core service architecture.
 
-<!-- :::image type="content" source="./media/reliability-acr/acr-service-architecture.png" alt-text="Diagram that shows Container Registry service architecture with client access, control plane, data plane, and storage layer components." lightbox="./media/reliability-acr/acr-service-architecture.png" border="false":::-->
+:::image type="content" source="./media/reliability-container-registry/service-architecture.png" alt-text="Diagram that shows Container Registry service architecture with client access, control plane, data plane, and storage layer components." border="false":::
 
 - **The control plane** is a centralized management component in the home region for registry configuration, authentication configuration, and replication policies.
 
@@ -111,7 +111,7 @@ Zone redundancy is included with Premium tier registries at no extra cost. The P
 
 This section describes what to expect when Container Registry resources are configured for zone redundancy and all availability zones are operational.
 
-<!-- :::image type="content" source="./media/reliability-acr/acr-zone-redundancy-normal-operations.png" alt-text="Diagram that shows Container Registry zone redundancy during normal operations." lightbox="./media/reliability-acr/acr-zone-redundancy-normal-operations.png" border="false"::: -->
+:::image type="content" source="./media/reliability-container-registry/zone-redundancy-normal-operations.png" alt-text="Diagram that shows Container Registry zone redundancy during normal operations." border="false":::
 
 - **Traffic routing between zones:** Container Registry uses internal routing functionality to automatically distribute data plane operations across all availability zones within a region. The registry service automatically routes requests to healthy zones without requiring external load balancers.
 
@@ -123,7 +123,7 @@ This section describes what to expect when Container Registry resources are conf
 
 When a zone becomes unavailable, Container Registry automatically handles the failover process with minimal impact to registry operations.
 
-<!-- :::image type="content" source="./media/reliability-acr/acr-zone-redundancy-zone-failure.png" alt-text="Diagram that shows Container Registry behavior during zone failure. Automatic failover routes to healthy zones. One zone is marked as unavailable." lightbox="./media/reliability-acr/acr-zone-redundancy-zone-failure.png" border="false"::: -->
+:::image type="content" source="./media/reliability-container-registry/zone-redundancy-zone-failure.png" alt-text="Diagram that shows Container Registry behavior during zone failure. Automatic failover routes to healthy zones. One zone is marked as unavailable." border="false":::
 
 - **Detection and response:** The Container Registry platform automatically detects failures in an availability zone and initiates a response. The service automatically routes traffic to the remaining healthy zones. No manual intervention is required to initiate a zone failover.
 
@@ -195,7 +195,7 @@ Geo-replication can be configured during registry creation or added to existing
 
 This section describes what to expect when a registry is configured for geo-replication and all regions are operational.
 
-<!-- :::image type="content" source="./media/reliability-acr/acr-multi-region-normal-operations.png" alt-text="Diagram showing Container Registry multi-region operations. Global clients connect via Traffic Manager to registry endpoints across multiple regions." lightbox="./media/reliability-acr/acr-multi-region-normal-operations.png" border="false"::: -->
+:::image type="content" source="./media/reliability-container-registry/multi-region-normal-operations.png" alt-text="Diagram showing Container Registry multi-region operations. Global clients connect via Traffic Manager to registry endpoints across multiple regions." border="false":::
 
 - **Traffic routing between regions:** Container Registry operates in an active-active configuration where each regional endpoint can serve all data plane operations independently, including reads and writes. Data plane operations, such as container push and pull operations, are automatically routed by using Traffic Manager with performance-based criteria to determine the optimal regional endpoint for performance.
 
@@ -209,7 +209,7 @@ This section describes what to expect when a registry is configured for geo-repl
 
 When a region becomes unavailable, container operations can continue to use alternative regional endpoints.
 
-<!-- :::image type="content" source="./media/reliability-acr/acr-multi-region-region-failure.png" alt-text="Diagram that shows Container Registry behavior during regional failure." lightbox="./media/reliability-acr/acr-multi-region-region-failure.png" border="false"::: -->
+:::image type="content" source="./media/reliability-container-registry/multi-region-region-failure.png" alt-text="Diagram that shows Container Registry behavior during regional failure." border="false":::
 
 - **Detection and response:** Container Registry monitors the health of each regional replica and is responsible for redirecting traffic to another region.