Merge pull request #204565 from MicrosoftDocs/main

7/13 OOB Publish at 8AM

Author: huypub

articles/azure-monitor/alerts/alerts-types.md

@@ -70,7 +70,7 @@ You may also decide not to split when you want a condition applied to multiple r
 
 You can monitor at scale by applying the same metric alert rule to multiple resources of the same type for resources that exist in the same Azure region. Individual notifications are sent for each monitored resource.
 
-These platform metrics for these services in the following Azure clouds are supported:
+The platform metrics for these services in the following Azure clouds are supported:
 
 | Service                      | Global Azure | Government | China   |
 |:-----------------------------|:-------------|:-----------|:--------|
@@ -85,7 +85,9 @@ These platform metrics for these services in the following Azure clouds are supp
 | Recovery Services vaults     | Yes      | No     | No  |
 
   > [!NOTE]
-  > Platform metrics are not supported for virtual machine network metrics (Network In Total, Network Out Total, Inbound Flows, Outbound Flows, Inbound Flows Maximum Creation Rate, Outbound Flows Maximum Creation Rate).
+  > Multi-resource metric alerts are not supported for the following scenarios:
+  > - Alerting on virtual machines' guest metrics
+  > - Alerting on virtual machines' network metrics (Network In Total, Network Out Total, Inbound Flows, Outbound Flows, Inbound Flows Maximum Creation Rate, Outbound Flows Maximum Creation Rate).
 
 You can specify the scope of monitoring with a single metric alert rule in one of three ways. For example, with virtual machines you can specify the scope as:  
 

articles/communication-services/concepts/interop/custom-teams-endpoint-use-cases.md

@@ -1,7 +1,7 @@
 ---
-title: Use cases for custom Teams endpoint
+title: Use cases for Azure Communication Services support Teams identities
 titleSuffix: An Azure Communication Services concept document
-description: This article describes use cases for a custom Teams endpoint.
+description: This article describes use cases for Azure Communication Services support Teams identities.
 author: tomaschladek
 manager: nmurav
 services: azure-communication-services
@@ -13,7 +13,7 @@ ms.service: azure-communication-services
 ms.subservice: teams-interop
 ---
 
-# Custom Teams Endpoint — Use cases
+# Azure Communication Services support Teams identities — Use cases
 
 Microsoft Teams provides identities managed by Azure Active Directory and calling experiences controlled by Teams Admin Center and policies. Users might have assigned licenses to enable PSTN connectivity and advanced calling capabilities of Teams Phone System. Azure Communication Services are supporting Teams identities for managing Teams VoIP calls, Teams PSTN calls, and join Teams meetings. Developers might extend the Azure Communication Services with Graph API to provide contextual data from Microsoft 365 ecosystem. This page is providing inspiration on how to use existing Microsoft technologies to provide an end-to-end experience for calling scenarios with Teams users and Azure Communication Services calling SDKs. 
 

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

@@ -1,7 +1,7 @@
 ---
-title: Build a custom Teams endpoint
+title: Integrate communication as Teams user with Azure Communication Services
 titleSuffix: An Azure Communication Services concept document
-description: This article discusses how to build a custom Teams endpoint.
+description: This article discusses how to integrate communication as Teams user with Azure Communication Services.
 author: tomaschladek
 manager: nmurav
 services: azure-communication-services
@@ -12,25 +12,25 @@ ms.topic: conceptual
 ms.service: azure-communication-services
 ms.subservice: teams-interop
 ---
-# Build a custom Teams endpoint
+# Integrate communication as Teams user with Azure Communication Services and Graph API
 
 [!INCLUDE [Public Preview](../includes/public-preview-include-document.md)]
 
-You can use Azure Communication Services and Graph API to build custom Teams endpoints to communicate with the Microsoft Teams client or other custom Teams endpoints. With a custom Teams endpoint, you can customize a voice, video, chat, and screen-sharing experience for Teams users.
+You can use Azure Communication Services and Graph API to integrate communication as Teams user into your products to communicate with other people in and outside your organization. With Azure Communication Services supporting Teams identities and Graph API, you can customize a voice, video, chat, and screen-sharing experience for Teams users.
 
 You can use the Azure Communication Services Identity SDK to exchange Azure Active Directory (Azure AD) access tokens of Teams users for Communication Identity access tokens. The diagrams in the next sections demonstrate multitenant use cases, where fictional company Fabrikam is the customer of fictional company Contoso.
 
 ## Calling 
 
-Voice, video, and screen-sharing capabilities are provided via Azure Communication Services Calling SDKs. The following diagram shows an overview of the process you'll follow as you integrate your calling experiences with custom Teams endpoints.
+Voice, video, and screen-sharing capabilities are provided via Azure Communication Services Calling SDKs. The following diagram shows an overview of the process you'll follow as you integrate your calling experiences with Azure Communication Services support Teams identities.
 
-![Diagram of the process of enabling the calling feature for a custom Teams endpoint experience.](./media/teams-identities/teams-identity-calling-overview.svg)
+![Diagram of the process to integrate the calling capabilities into your product with Azure Communication Services.](./media/teams-identities/teams-identity-calling-overview.svg)
 
 ## Chat
 
-Optionally, you can also use custom Teams endpoints to integrate chat capabilities by using Graph APIs. For more information about the Graph API, see the [chat resource type](/graph/api/channel-post-messages) documentation. 
+Optionally, you can also use Graph API to integrate chat capabilities into your product. For more information about the Graph API, see the [chat resource type](/graph/api/channel-post-messages) documentation. 
 
-![Diagram of the process of enabling the chat feature for a custom Teams endpoint experience.](./media/teams-identities/teams-identity-chat-overview.png)
+![Diagram of the process to integrate the chat capabilities into your product with Graph API.](./media/teams-identities/teams-identity-chat-overview.png)
 
 ## Azure Communication Services permissions
 

articles/communication-services/quickstarts/eligible-teams-licenses.md

@@ -44,5 +44,5 @@ The following articles might be of interest to you:
 
 - Try [quickstart for authentication of Teams users](./manage-teams-identity.md).
 - Try [quickstart for calling to a Teams user](./voice-video-calling/get-started-with-voice-video-calling-custom-teams-client.md).
-- Learn more about [Custom Teams endpoint](../concepts/teams-endpoint.md)
+- Learn more about [Azure Communication Services support Teams identities](../concepts/teams-endpoint.md)
 - Learn more about [Teams interoperability](../concepts/teams-interop.md)

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

@@ -17,7 +17,7 @@ ms.custom: mode-other
 
 [!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 build a custom Teams endpoint.
+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]
 > When you're in a production environment, we recommend that you implement this exchange mechanism in back-end services, because requests for an exchange are signed with a secret.
@@ -37,7 +37,7 @@ The following sections will guide you through the steps for administrators, deve
 
 The Administrator role has extended permissions in Azure AD. Members of this role can set up resources and can read information from the Azure portal. In the following diagram, you can see all actions that have to be executed by Administrators.
 
-![Administrator actions to enable custom Teams endpoint experience](./media/teams-identities/teams-identity-admin-overview.svg)
+![Administrator actions to enable Azure Communication Services support for Teams identities.](./media/teams-identities/teams-identity-admin-overview.svg)
 
 1. The Contoso Administrator creates or selects an existing *application* in Azure Active Directory. The property *Supported account types* defines whether users from various tenants can authenticate to the application. The property *Redirect URI* redirects a successful authentication request to the Contoso *server*.
 1. The Contoso Administrator adds API permissions to `Teams.ManageCalls` and `Teams.ManageChats` from Communication Services. 
@@ -112,7 +112,7 @@ The Contoso developer needs to set up the *client application* to authenticate u
 
 The developer's required actions are shown in following diagram:
 
-![Diagram of developer actions to enable the custom Teams endpoint experience.](./media/teams-identities/teams-identity-developer-overview.svg)
+![Diagram of developer actions to enable Azure Communication Services support for Teams identities.](./media/teams-identities/teams-identity-developer-overview.svg)
 
 1. The Contoso developer configures the Microsoft Authentication Library (MSAL) to authenticate the user for the application that was created earlier by the Administrator for Communication Services Teams.ManageCalls and Teams.ManageChats permissions.
 1. The Contoso developer initializes the Communication Services Identity SDK and exchanges the incoming Azure AD user token for the access token of Teams user via the identity SDK. The access token of Teams user is then returned to the *client application*.
@@ -145,14 +145,14 @@ For more information about setting up environments in public documentation, see
 
 The user represents the Fabrikam users of the Contoso application. The user experience is shown in the following diagram:
 
-![Diagram of user actions to enable the custom Teams endpoint experience.](./media/teams-identities/teams-identity-user-overview.svg)
+![Diagram of user actions to enable Azure Communication Services support for Teams identities.](./media/teams-identities/teams-identity-user-overview.svg)
 
 1. The Fabrikam user uses the Contoso *client application* and is prompted to authenticate.
 1. The Contoso *client application* uses the MSAL to authenticate the user against the Fabrikam Azure AD tenant for the Contoso application with Communication Services Teams.ManageCalls and Teams.ManageChats permissions. 
 1. Authentication is redirected to the *server*, as defined in the property *Redirect URI* in the MSAL and the Contoso application.
 1. The Contoso *server* exchanges the Azure AD user token for the access token of Teams user by using the Communication Services Identity SDK and returns the access token of Teams user to the *client application*.
 
-With a valid access token for Teams user in the *client application*, developers can integrate the Communication Services Calling SDK and build a custom Teams endpoint.
+With a valid access token for Teams user in the *client application*, developers can integrate the Communication Services Calling SDK and manage calls as Teams user.
 
 ## Next steps
 
@@ -165,5 +165,5 @@ In this quickstart, you learned how to:
 
 Learn about the following concepts:
 
-- [Custom Teams endpoint](../concepts/teams-endpoint.md)
+- [Azure Communication Services support Teams identities](../concepts/teams-endpoint.md)
 - [Teams interoperability](../concepts/teams-interop.md)

articles/communication-services/samples/trusted-auth-sample.md

@@ -27,7 +27,7 @@ This repository provides a sample of a server implementation of an authenticatio
 
 This sample can help you in the following scenarios:
 - As a developer, you need to enable an authentication flow to generate Azure Communication Services user identities mapped to an Azure Active Directory identity. Using this identity you then will provision access tokens to be used in calling and chat experiences.
-- As a developer, you need to enable an authentication flow for Custom Teams Endpoint, which is done by using an Microsoft 365 Azure Active Directory identity of a Teams' user to fetch an Azure Communication Services token to be able to join Teams calling/chat.
+- As a developer, you need to enable an authentication flow for Azure Communication Services support Teams identities, which is done by using an Microsoft 365 Azure Active Directory identity of a Teams' user to fetch an Azure Communication Services token to be able to join Teams calling/chat.
 
 > [!NOTE]
 >If you are looking to get started with Azure Communication Services, but are still in learning / prototyping phases, check out our [quickstarts for getting started with Azure communication services users and access tokens](../quickstarts/access-tokens.md?pivots=programming-language-csharp).

articles/communication-services/toc.yml

@@ -238,7 +238,7 @@ items:
         href: concepts/teams-interop.md
       - name: Join a Teams meeting
         href: concepts/join-teams-meeting.md
-      - name: Custom Teams endpoint
+      - name: Communication for Teams identities
         items:
           - name: Overview
             href: concepts/teams-endpoint.md