Merge pull request #208706 from tomaschladek/cte-12

Removal of preview labels

Author: prmerger-automator[bot]

articles/communication-services/concepts/interop/teams-user-calling.md

@@ -14,8 +14,6 @@ ms.subservice: calling
 ---
 # Support for Teams identity in Calling SDK
 
-[!INCLUDE [Communication services support for Teams identity eligibility notice](../../includes/public-preview-include.md)]
-
 The Azure Communication Services Calling SDK for JavaScript enables Teams user devices to drive voice and video communication experiences. This page provides detailed descriptions of Calling features, including platform and browser support information. To get started right away, check out [Calling quickstarts](../../quickstarts/voice-video-calling/get-started-with-voice-video-calling-custom-teams-client.md). 
 
 Key features of the Calling SDK:

articles/communication-services/concepts/join-teams-meeting.md

@@ -12,9 +12,6 @@ ms.subservice: teams-interop
 
 # Join a Teams meeting
 
-> [!IMPORTANT]
-> BYOI interoperability is now generally available to all Communication Services applications and Teams organizations.
-
 Azure Communication Services can be used to build applications that enable users to join and participate in Teams meetings. [Standard Azure Communication Services pricing](https://azure.microsoft.com/pricing/details/communication-services/) applies to these users, but there's no additional fee for the interoperability capability itself. With the bring your own identity (BYOI) model, you control user authentication and users of your applications don't need Teams licenses to join Teams meetings. This is ideal for applications that enable licensed Teams users and external users using a custom application to join into a virtual consultation experience. For example, healthcare providers using Teams can conduct teleheath virtual visits with their patients who use a custom application. 
 
 It's also possible to use Teams identities with the Azure Communication Services SDKs. More information is available [here](./teams-interop.md).
@@ -74,4 +71,4 @@ Microsoft will indicate to you via the Azure Communication Services API that rec
 
 - [How-to: Join a Teams meeting](../how-tos/calling-sdk/teams-interoperability.md)
 - [Quickstart: Join a BYOI calling app to a Teams meeting](../quickstarts/voice-video-calling/get-started-teams-interop.md)
-- [Quickstart: Join a BYOI chat app to a Teams meeting](../quickstarts/chat/meeting-interop.md)
+- [Quickstart: Join a BYOI chat app to a Teams meeting](../quickstarts/chat/meeting-interop.md)

articles/communication-services/concepts/teams-endpoint.md

@@ -14,8 +14,6 @@ ms.subservice: teams-interop
 ---
 # Communication as Teams user
 
-[!INCLUDE [Public Preview](../includes/public-preview-include-document.md)]
-
 You can use Azure Communication Services and Graph API to integrate communication as Teams users into your products. Teams users can communicate with other people in and outside their organization. The benefits for enterprises are:
 - No requirement to download Teams desktop, mobile or web clients for Teams users
 - Teams users don't lose context by switching between applications for day-to-day work and Teams client for communication

articles/communication-services/concepts/teams-interop.md

@@ -12,13 +12,6 @@ ms.subservice: teams-interop
 
 # Teams interoperability
 
-> [!IMPORTANT]
-> Teams external users interoperability for Teams meetings is now generally available to all Communication Services applications and Teams organizations.
->
-> Support for Teams users in Azure Communication Services SDK is in public preview and available to Web-based applications.
->
-> Preview APIs and SDKs are provided without a service-level agreement and are not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
-
 Azure Communication Services can be used to build custom applications and experiences that enable interaction with Microsoft Teams users over voice, video, chat, and screen sharing. The [Communication Services UI Library](ui-library/ui-library-overview.md) provides customizable, production-ready UI components that can be easily added to these applications. The following video demonstrates some of the capabilities of Teams interoperability:
 
 <br>

articles/communication-services/quickstarts/manage-teams-identity.md

@@ -15,8 +15,6 @@ ms.custom: mode-other
 ---
 # Quickstart: Set up and manage access tokens for Teams users
 
-[!INCLUDE [Public Preview](../../communication-services/includes/public-preview-include-document.md)]
-
 In this quickstart, you'll build a .NET console application to authenticate a Microsoft 365 user by using the Microsoft Authentication Library (MSAL) and retrieving a Microsoft Azure Active Directory (Azure AD) user token. You'll then exchange that token for an access token of Teams user with the Azure Communication Services Identity SDK. The access token for Teams user can then be used by the Communication Services Calling SDK to integrate calling capability as Teams user.
 
 > [!NOTE]

articles/communication-services/quickstarts/voice-video-calling/get-started-with-voice-video-calling-custom-teams-client.md

@@ -13,8 +13,6 @@ ms.custom: mode-other
 
 # QuickStart: Add 1:1 video calling as a Teams user to your application
 
-[!INCLUDE [Public Preview](../../../communication-services/includes/public-preview-include-document.md)]
-
 [!INCLUDE [Video calling with JavaScript](./includes/custom-teams-endpoint/voice-video-calling-cte-javascript.md)]
 
 ## Clean up resources