Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into packet-core-4.15

Author: b-branco

articles/azure-arc/vmware-vsphere/overview.md

@@ -26,7 +26,7 @@ To deliver this experience, you need to deploy the [Azure Arc resource bridge](.
 
 ## Supported VMware vSphere versions
 
-Azure Arc-enabled VMware vSphere (preview) works with VMware vSphere version 7.
+Azure Arc-enabled VMware vSphere (preview) works with VMware vSphere version 6.7 and 7.
 
 > [!NOTE]
 > Azure Arc-enabled VMware vSphere  (preview)  supports vCenters with a maximum of 2500 VMs. If your vCenter has more than 2500 VMs, it is not recommended to use Arc-enabled VMware vSphere with it at this point.

articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md

@@ -24,7 +24,7 @@ First, the script deploys a virtual appliance called [Azure Arc resource bridge
 
 ### vCenter Server
 
-- vCenter Server version 7.
+- vCenter Server version 6.7 or 7.
 
 - A virtual network that can provide internet access, directly or through a proxy. It must also be possible for VMs on this network to communicate with the vCenter server on TCP port (usually 443).
 

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

@@ -18,11 +18,11 @@ ms.subservice: teams-interop
 
 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.
+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. Contoso builds multi-tenant SaaS product that Fabrikam's administrator purchases for its employees. 
 
 ## 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 Azure Communication Services support Teams identities.
+Voice, video, and screen-sharing capabilities are provided via [Azure Communication Services Calling SDKs](./interop/teams-user-calling.md). 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. You can learn more details about the [authentication](./interop/custom-teams-endpoint-authentication-overview.md) and [used packages](../quickstarts/manage-teams-identity.md). 
 
 ![Diagram of the process to integrate the calling capabilities into your product with Azure Communication Services.](./media/teams-identities/teams-identity-calling-overview.svg)
 
@@ -56,6 +56,8 @@ Find more details in [Azure Active Directory documentation](../../active-directo
 ## Next steps
 
 > [!div class="nextstepaction"]
+> [Check use cases for communication as a Teams user](./interop/custom-teams-endpoint-use-cases.md)
 > [Issue a Teams access token](../quickstarts/manage-teams-identity.md)
+> [Start a call with Teams user as a Teams user](../quickstarts/voice-video-calling/get-started-with-voice-video-calling-custom-teams-client.md)
 
-Learn about [Teams interoperability](./teams-interop.md).
+Learn about [Teams interoperability](./teams-interop.md).

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

@@ -29,7 +29,7 @@ Azure Communication Services can be used to build custom applications and experi
 
 Azure Communication Services supports two types of Teams interoperability depending on the identity of the user:
 
-- **[Bring your own identity (BYOI)](#bring-your-own-identity).** You control user authentication and users of your custom applications don't need to have Azure Active Directory identities or Teams licenses. This model allows you to build custom applications for non-Teams users to connect and communicate with Teams users.
+- **[Guest/Bring your own identity (BYOI)](#guestbring-your-own-identity).** You control user authentication and users of your custom applications don't need to have Azure Active Directory identities or Teams licenses. This model allows you to build custom applications for non-Teams users to connect and communicate with Teams users.
 - **[Teams identity](#teams-identity).** User authentication is controlled by Azure Active Directory and users of your custom application must have Teams licenses. This model allows you to build custom applications for Teams users to enable specialized workflows or experiences that are not possible with the existing Teams clients.
 
 Applications can implement both authentication models and leave the choice of authentication up to the user. The following table compares two models:
@@ -47,7 +47,7 @@ Applications can implement both authentication models and leave the choice of au
 
 \* Server logic issuing access tokens can perform any custom authentication and authorization of the request.
 
-## Bring your own identity
+## Guest/Bring your own identity
 
 The bring your own identity (BYOI) authentication model allows you to build custom applications for non-Teams users to connect and communicate with Teams users. You control user authentication and users of your custom applications don't need to have Azure Active Directory identities or Teams licenses. The first scenario that has been enabled allows users of your application to join Microsoft Teams meetings as external accounts, similar to [anonymous users that join meetings](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings) using the Teams web application. This is ideal for business-to-consumer applications that bring together employees (familiar with Teams) and external users (using a custom application) into a meeting experience. In the future, we will be enabling additional scenarios including direct calling and chat which will allow your application to initiate calls and chats with Teams users outside the context of a Teams meeting.
 
@@ -57,7 +57,7 @@ It is currently not possible for a Teams user to join a call that was initiated
 
 ## Teams identity
 
-Developers can use Communication Services Calling SDK with Teams identity to build custom applications for Teams users. Custom applications can enable specialized workflows for Teams users such as management of incoming and outgoing PSTN calls or bring Teams calling experience into devices that are not supported with the standard Teams client. Teams identities are authenticated by Azure Active Directory, and all attributes and details about the user are bound to their Azure Active Directory account.
+Developers can use [Communication Services Calling SDK with Teams identity](./interop/teams-user-calling.md) to build custom applications for Teams users. Custom applications can enable specialized workflows for Teams users such as management of incoming and outgoing PSTN calls or bring Teams calling experience into devices that are not supported with the standard Teams client. Teams identities are authenticated by Azure Active Directory, and all attributes and details about the user are bound to their Azure Active Directory account.
 
 When a Communication Services endpoint connects to a Teams meeting or Teams call using a Teams identity, the endpoint is treated like a Teams user with a Teams client and the experience is driven by policies assigned to users within and outside of the organization. Teams users can join Teams meetings, place calls to other Teams users, receive calls from phone numbers, transfer an ongoing call to the Teams call queue or share screen. 
 
@@ -69,7 +69,7 @@ There are several ways that users can join a Teams meeting:
 
 - Via Teams clients as authenticated **Teams users**. This includes the desktop, mobile, and web Teams clients.
 - Via Teams clients as unauthenticated **Anonymous users**. 
-- Via custom Communication Services applications as **BYOI users** using the bring your own identity authentication model. 
+- Via custom Communication Services applications as **Guest/BYOI users** using the bring your own identity authentication model. 
 - Via custom Communication Services applications as **Teams users** using the Teams identity authentication model.
 
 ![Overview of multiple interoperability scenarios within Azure Communication Services](./media/teams-identities/teams-interop-overview-v2.png)
@@ -83,7 +83,7 @@ Interoperability between Azure Communication Services and Microsoft Teams enable
 Microsoft will indicate to you via the Azure Communication Services API that recording or transcription has commenced and you must communicate this fact, in real-time, to your users within your application's user interface. You agree to indemnify Microsoft for all costs and damages incurred as a result of your failure to comply with this obligation.
 
 ## Pricing
-All usage of Azure Communication Service APIs and SDKs increments [Azure Communication Service billing meters](https://azure.microsoft.com/pricing/details/communication-services/). Interactions with Microsoft Teams, such as joining a meeting or initiating a phone call using a Teams allocated number, will increment these meters but there is no additional fee for the Teams interoperability capability itself, and there is no pricing distinction between the BYOI and Microsoft 365 authentication options.
+All usage of Azure Communication Service APIs and SDKs increments [Azure Communication Service billing meters](https://azure.microsoft.com/pricing/details/communication-services/). Interactions with Microsoft Teams, such as joining a meeting or initiating a phone call using a Teams allocated number, will increment these meters but there is no additional fee for the Teams interoperability capability itself, and there is no pricing distinction between the Guest/BYOI and Microsoft 365 authentication options.
 
 If your Azure application has a user spend 10 minutes in a meeting with a user of Microsoft Teams, those two users combined consumed 20 calling minutes. The 10 minutes exercised through the custom application and using Azure APIs and SDKs will be billed to your resource. However, the 10 minutes consumed by the user in the native Teams application is covered by the applicable Teams license and is not metered by Azure.
 
@@ -93,4 +93,8 @@ Azure Communication Services interoperability isn't compatible with Teams deploy
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Enable Teams access tokens](../quickstarts/manage-teams-identity.md)
+> [Get access tokens for Guest/BYOI](../quickstarts/access-tokens.md)
+> [Join Teams meeting call as a Guest/BYOI](../quickstarts/voice-video-calling/get-started-teams-interop.md)
+> [Join Teams meeting chat as a Guest/BYOI](../quickstarts/chat/meeting-interop.md)
+> [Get access tokens for Teams users](../quickstarts/manage-teams-identity.md)
+> [Make a call as a Teams users to a Teams user](../quickstarts/voice-video-calling/get-started-with-voice-video-calling-custom-teams-client.md)

articles/communication-services/how-tos/cte-calling-sdk/includes/manage-calls/manage-calls-web.md

@@ -166,6 +166,12 @@ const identifier = remoteParticipant.identifier;
 |`Disconnected` | Final state | The participant is disconnected from the call. If the remote participant loses their network connectivity, their state changes to `Disconnected` after two minutes. |
 
 
+States of remote participants in one-to-one or group calls:
+![Diagram of remote participant's call states for one-to-one or group calls.](../media/participants-call-states.svg)
+
+States of remote participants in Teams meetings:
+![Diagram of remote participant's call states for Teams meetings.](../media/participants-meeting-states.svg)
+
 ```js
 const state = remoteParticipant.state;
 ```
@@ -236,6 +242,8 @@ const callerIdentity = call.callerInfo.displayName;
 ```
 
 •	`state`: Returns a string representing the state of the call. The property can have one of the following values:
+
+
 | State value | When | Description |
 |-------------|------| ----------- |
 |`None` | Initial state | The initial state of the call.|
@@ -249,6 +257,11 @@ const callerIdentity = call.callerInfo.displayName;
 |`Disconnecting`| After any state | The transition state before the call goes to a `Disconnected` state.|
 | `Disconnected`| Final state | The final state of the call. If the network connection is lost, the state changes to `Disconnected` after two minutes.|
 
+States for one-to-one or group calls:
+![Diagram with call's states for one-to-one or group calls.](../media/call-states.svg)
+
+States for Teams meetings:
+![Diagram with call's states for Teams meetings.](../media/meeting-states.svg)
 
 ```js
 const callState = call.state;