Merge pull request #295433 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/communication-services/concepts/voice-video-calling/real-time-text.md

@@ -16,7 +16,7 @@ ms.subservice: calling
 # Real Time Text (RTT) Overview
 
 >[!NOTE]
->RTT is an accessibility compliance requirement for voice and video platforms in the EU. You can find more information about this here: [Directive 2019/882](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L0882)
+>RTT is an accessibility compliance requirement for voice and video platforms in the EU starting June 30, 2025. You can find more information about this here: [Directive 2019/882](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L0882)
 
 Real Time Text (RTT) provides developers with the ability to transmit text in near real-time during a call. This feature is designed to empower individuals who have difficulty speaking, ensuring their text messages are displayed prominently to other meeting participants, similar to spoken communication. RTT enhances accessibility by allowing participants to communicate effectively through typed messages that are broadcast instantly character by character, without having to press a "send" key. 
 
@@ -53,6 +53,9 @@ The `RealTimeTextInfo` (or `RealTimeTextDetails` on certain platforms) class is
 
 Developers can subscribe to RTT events through a single event subscription, allowing them to manage their own list and ordering of RTT messages. This approach aligns with the Captions API, facilitating easier integration and maintenance. The UI is responsible for binding the data to the screen, managing the display list, and handling text input interactions based on message finalization.
 
+>[!NOTE]
+>RTT Teams Interlop is not functional yet.
+
 ### Privacy Concerns
 Real-Time Text (RTT) is only available during the call or meeting. Azure Communication Services doesn't store these text exchanges anywhere. Many countries/regions and states have laws and regulations that apply to the storing of data. It is your responsibility to use RTT in compliance with the law should you choose to store any of the data generated through RTT. You must obtain consent from the parties involved in a manner that complies with the laws applicable to each participant.
 

articles/communication-services/quickstarts/voice-video-calling/get-started-with-real-time-text.md

@@ -14,10 +14,13 @@ zone_pivot_groups: acs-programming-languages-java-swift-csharp
 
 
 
-# Real Time Text
+# Quickstart RTT within your application
 
 [!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include-document.md)]
 
+>[!NOTE]
+>RTT is an accessibility compliance requirement for voice and video platforms in the EU starting June 30, 2025. You can find more information about this here: [Directive 2019/882](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L0882).
+
 Learn how to integrate Real Time Text (RTT) into your calling applications to enhance accessibility and ensure that all participants can communicate effectively during meetings.
 
 RTT allows users who have difficulty speaking to participate actively by typing their messages, which are then broadcast in near real-time to other meeting participants. This feature operates seamlessly alongside existing captions and ensures that typed messages are promptly delivered without disrupting the flow of conversation.
@@ -28,6 +31,9 @@ Real Time Text (RTT) is designed to facilitate communication for users who may h
 
 On supported platforms, RTT data can be displayed alongside captions derived from Speech to Text, providing a comprehensive view of all communications during a call.
 
+>[!NOTE]
+>RTT Teams Interlop is not functional yet.
+
 ## Naming Conventions
 
 Different platforms may use varying terminology for RTT-related properties. Below is a summary of these differences:
@@ -70,5 +76,5 @@ The `RealTimeTextInfo` (or `RealTimeTextDetails` on Windows) class encapsulates
 ## Next steps
 
 For more information, see the following articles:
-
+- [Real Time Text Conceptual Doc](../../concepts/voice-video-calling/real-time-text.md)
 - [Azure Communication Services Calling Documentation](../../concepts/voice-video-calling/calling-sdk-features.md)

articles/openshift/howto-infrastructure-nodes.md

@@ -213,6 +213,39 @@ Vnet:
 oc get machineset <machineset_name> -n openshift-machine-api -o jsonpath='{.spec.template.spec.providerSpec.value.vnet}'
 ```
 
+## DNS
+
+Follow the instructions below to enable scheduling of DNS pods on the infrastructure nodes.
+
+> [!NOTE]
+> This section is crucial to support log collection from infrastructure nodes, ensuring supportability of your deployment.
+>
+
+1. Allow the DNS pods to run on the infrastructure nodes.
+
+   ```
+   oc edit dns.operator/default
+   ```
+
+   ```
+   apiVersion: operator.openshift.io/v1
+   kind: DNS
+   metadata:
+   name: default
+   spec:
+   nodePlacement:
+     tolerations:
+     - operator: Exists
+   ```
+    
+1. Verify that DNS pods are scheduled onto all infra nodes.
+
+    ```
+    oc get ds/dns-default -n openshift-dns
+    NAME          DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
+    dns-default   7         7         7       7            7           kubernetes.io/os=linux   35d
+    ```
+
 ## Moving workloads to the new infrastructure nodes
 
 Use the instructions below to move your infrastructure workloads to the infrastructure nodes previously created.
@@ -359,30 +392,4 @@ Use this procedure for any additional ingress controllers you may have in the cl
     kube-state-metrics-574c5bfdd7-f7fjk            3/3     Running   0          2m49s   10.131.4.8    cz-cluster-hsmtw-infra-aro-machinesets-eastus-1-vr56r   <none>           <none>
     ```
 
-### DNS
-
-1. Allow the DNS pods to run on the infrastructure nodes.
-
-   ```
-   oc edit dns.operator/default
-   ```
-
-   ```
-   apiVersion: operator.openshift.io/v1
-   kind: DNS
-   metadata:
-   name: default
-   spec:
-   nodePlacement:
-     tolerations:
-     - operator: Exists
-   ```
-    
-1. Verify that DNS pods are scheduled onto all infra nodes.
-
-```
-oc get ds/dns-default -n openshift-dns
-NAME          DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
-dns-default   7         7         7       7            7           kubernetes.io/os=linux   35d
-```
    

includes/azure-virtual-network-limits.md

@@ -42,6 +42,7 @@ The following limits apply only for networking resources managed through **Azure
 | Application security groups that can be specified within all security rules of a network security group |100 |
 | User-defined route tables |200 |
 | User-defined routes per route table |400 |
+| Routes with service tag per route table | 25 |
 | Point-to-site root certificates per Azure VPN Gateway |20 |
 | Point-to-site revoked client certificates per Azure VPN Gateway |300 |
 | Virtual network TAPs |100 |