Merge pull request #289204 from bjqian/main

Add clarification about inherited configuration of SignalR and Web PubSub replication

Author: prmerger-automator[bot]

articles/azure-signalr/howto-enable-geo-replication.md

@@ -192,3 +192,13 @@ Specifically, if your application typically broadcasts to larger groups (size >1
 To ensure effective failover management, it is recommended to set each replica's unit size to handle all traffic. Alternatively, you could enable [autoscaling](signalr-howto-scale-autoscale.md) to manage this.
 
 For more performance evaluation, refer to [Performance](signalr-concept-performance.md).
+
+## Non-Inherited and Inherited Configurations
+Replicas inherit most configurations from the primary resource; however, some settings must be configured directly on the replicas. Below is the list of those configurations:
+
+1. **SKU**: Each replica has its own SKU name and unit size. The autoscaling rules for replicas must be configured separately based on their individual metrics.
+2. **Shared private endpoints**: While shared private endpoints are automatically replicated to replicas, separate approvals are required on target private link resources. To add or remove shared private endpoints, manage them on the primary resource. **Do not** enable the replica until its shared private endpoint has been approved.
+3. **Log Destination Settings**. If not configured on the replicas, only logs from the primary resource will be transferred.
+4. **Alerts**. 
+
+All other configurations are inherited from the primary resource. For example, access keys, identity, application firewall, custom domains, private endpoints, and access control.

articles/azure-web-pubsub/howto-enable-geo-replication.md

@@ -200,4 +200,14 @@ To ensure effective failover management, it is recommended to set each replica's
 
 For more performance evaluation, refer to [Performance](concept-performance.md).
 
+## Non-Inherited and Inherited Configurations
+Replicas inherit most configurations from the primary resource; however, some settings must be configured directly on the replicas. Below is the list of those configurations:
+
+1. **SKU**: Each replica has its own SKU name and unit size. The autoscaling rules for replicas must be configured separately based on their individual metrics.
+2. **Shared private endpoints**: While shared private endpoints are automatically replicated to replicas, separate approvals are required on target private link resources. To add or remove shared private endpoints, manage them on the primary resource. **Do not** enable the replica until its shared private endpoint has been approved.
+3. **Log Destination Settings**. If not configured on the replicas, only logs from the primary resource will be transferred.
+4. **Alerts**. 
+
+All other configurations are inherited from the primary resource. For example, access keys, identity, application firewall, custom domains, private endpoints, and access control.
+