Skip to content

Commit 4685be4

Browse files
Merge pull request #262995 from tomaschladek/turn-deprecation
ACS Turn deprecation
2 parents a88e130 + f519780 commit 4685be4

File tree

5 files changed

+17
-0
lines changed

5 files changed

+17
-0
lines changed

articles/communication-services/concepts/analytics/logs/network-traversal-logs.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ ms.subservice: data
1515

1616
Azure Communication Services offers logging capabilities that you can use to monitor and debug your Communication Services solution. These capabilities can be configured through the Azure portal.
1717

18+
[!INCLUDE [TURN retirment](../../../includes/turn-retirement.md)]
19+
1820
> [!IMPORTANT]
1921
> The following refers to logs enabled through [Azure Monitor](../../../../azure-monitor/overview.md) (see also [FAQ](../../../../azure-monitor/overview.md#frequently-asked-questions)). To enable these logs for your Communications Services, see: [Enable logging in Diagnostic Settings](../enable-logging.md)
2022

articles/communication-services/concepts/analytics/turn-metrics.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ Azure Communication Services currently provides metrics for all Communication Se
1919
- Investigate abnormalities in your metric values.
2020
- Understand your API traffic by using the metrics data that Chat requests emit.
2121

22+
[!INCLUDE [TURN retirment](../../includes/turn-retirement.md)]
23+
2224
## Where to find metrics
2325

2426
Primitives in Communication Services emit metrics for API requests. To find these metrics, see the **Metrics** tab under your Communication Services resource. You can also create permanent dashboards by using the workbooks tab under your Communication Services resource.

articles/communication-services/concepts/network-traversal.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ Real-time Relays solve the problem of NAT (Network Address Translation) traversa
1818
* STUN (Session Traversal Utilities for NAT) offers a protocol to allow devices to exchange external IPs on the internet. If the clients can see each other, there is typically no need for a relay through a TURN service since the connection can be made peer-to-peer. A STUN server's job is to respond to request for a device's external IP.
1919
* TURN (Traversal Using Relays around NAT) is an extension of the STUN protocol that also relays the data between two endpoints through a mutually visible server.
2020

21+
[!INCLUDE [TURN retirment](../includes/turn-retirement.md)]
22+
2123
## Azure Communication Services Network Traversal Overview
2224

2325
WebRTC(Web Real-Time Technologies) allow web browsers to stream audio, video, and data between devices without needing to have a gateway in the middle. Some of the common use cases here are voice, video, broadcasting, and screen sharing. To connect two endpoints on the internet, their external IP address is required. External IP is typically not available for devices sitting behind a corporate firewall. The protocols like STUN (Session Traversal Utilities for NAT) and TURN (Traversal Using Relays around NAT) are used to help the endpoints communicate.
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
author: tomaschladek
3+
ms.author: tchladek
4+
ms.service: azure-communication-services
5+
ms.topic: include
6+
ms.date: 1/1/2024
7+
---
8+
> [!IMPORTANT]
9+
> Azure Communication Services Network Traversal (TURN) Public Preview is retiring. Azure Communication Services Network Traversal (TURN) currently provides tokens to access our Transport Relays to use data transfer services. After 31 March 2024, your TURN issued tokens will no longer be supported. Please transition to a third-party service before this date to avoid service disruption. If you have questions, get answers from community experts in [Microsoft Q&A](https://aka.ms/AAjoeog). If you have a support plan and require further assistance, please create a [support ticket](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview). You can find more details about retirement in the [announcement](https://azure.microsoft.com/updates/retirement-notice-azure-communication-services-network-traversal-turn-public-preview-is-retiring/).

articles/communication-services/quickstarts/relay-token.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ ms.custom: mode-other, devx-track-extended-java, devx-track-js, devx-track-pytho
1515

1616
This quickstart shows how to retrieve a network relay token to access Azure Communication Services TURN servers.
1717

18+
[!INCLUDE [TURN retirment](../includes/turn-retirement.md)]
19+
1820
## Prerequisites
1921

2022
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free)

0 commit comments

Comments
 (0)