Merge pull request #264301 from MicrosoftDocs/main

1/26 11:00 AM IST Publish

Author: Saisang

CODEOWNERS

@@ -45,7 +45,8 @@ You can use the SSML via the [Speech SDK](./get-started-text-to-speech.md), [RES
 
 ## Reference documentation
 
-The API reference documentation is made available to approved customers. You can apply for access [here](https://aka.ms/customneural).
+> [!div class="nextstepaction"]
+> [Custom voice API specification - 2023-12-01-preview](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/data-plane/Speech/TextToSpeech/preview/2023-12-01-preview/texttospeech.json/)
 
 ## Next steps
 

articles/ai-services/speech-service/personal-voice-how-to-use.md

@@ -43,6 +43,8 @@ This article shows you how to use Azure CNI networking to create and use a virtu
 
 ## Configure networking
 
+For information on planning IP addressing for your AKS cluster, see [Plan IP addressing for your cluster](./azure-cni-overview.md#plan-ip-addressing-for-your-cluster).
+
 # [**Portal**](#tab/configure-networking-portal)
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).

articles/aks/configure-azure-cni.md

@@ -66,7 +66,7 @@ You can create and use an internal load balancer to restrict access to your appl
 
 ## Specify an IP address
 
-When you specify an IP address for the load balancer, the specified IP address must reside in the same subnet as the AKS cluster, but it can't already be assigned to a resource. For example, you shouldn't use an IP address in the range designated for the Kubernetes subnet within the AKS cluster.
+When you specify an IP address for the load balancer, the specified IP address must reside in the same virtual network as the AKS cluster, but it can't already be assigned to another resource in the virtual network. For example, you shouldn't use an IP address in the range designated for the Kubernetes subnet within the AKS cluster. Using an IP address that's already assigned to another resource in the same virtual network can cause issues with the load balancer.
 
 You can use the [`az network vnet subnet list`][az-network-vnet-subnet-list] Azure CLI command or the [`Get-AzVirtualNetworkSubnetConfig`][get-azvirtualnetworksubnetconfig] PowerShell cmdlet to get the subnets in your virtual network.
 

articles/aks/internal-lb.md

@@ -1,7 +1,7 @@
 ---
-title: Teams calling and chat interoperability
+title: Teams calling interoperability
 titleSuffix: An Azure Communication Services concept document
-description: Teams calling and chat interoperability
+description: Teams calling interoperability
 author: tomaschladek
 ms.author: tchladek
 ms.date: 10/15/2021
@@ -10,23 +10,18 @@ ms.service: azure-communication-services
 ms.subservice: teams-interop
 ---
 
-# Teams Interoperability: Calling and chat
+# Teams Interoperability: Calling
 
-> [!IMPORTANT]
-> Calling and chat interoperability is in private preview and restricted to a limited number of Azure Communication Services early adopters. You can [submit this form to request participation in the preview](https://forms.office.com/r/F3WLqPjw0D), and we'll review your scenario(s) and evaluate your participation in the preview.
->
-> Private Preview APIs and SDKs are provided without a service-level agreement, aren't appropriate for production workloads, and should only be used with test users and data. Certain features may not be supported or have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
-> 
-> For support, questions, or to provide feedback or report issues, please use the [Teams interop ad hoc calling and chat channel](https://teams.microsoft.com/l/channel/19%3abfc7d5e0b883455e80c9509e60f908fb%40thread.tacv2/Teams%2520Interop%2520ad%2520hoc%2520calling%2520and%2520chat?groupId=d78f76f3-4229-4262-abfb-172587b7a6bb&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47). You must be a member of the Azure Communication Service TAP team.
+[!INCLUDE [Public Preview](../../../communication-services/includes/public-preview-include-document.md)]
 
-As part of this preview, the Azure Communication Services SDKs can be used to build applications that enable bring your own identity (BYOI) users to start 1:1 calls or 1:n chats with Teams users. [Standard Azure Communication Services pricing](https://azure.microsoft.com/pricing/details/communication-services/) applies to these users, but there's no extra fee for the interoperability capability. Custom applications built with Azure Communication Services to connect and communicate with Teams users or Teams voice applications can be used by end users or by bots, and there's no differentiation in how they appear to Teams users in Teams applications unless explicitly indicated by the developer of the application with a display name.
+As part of this preview, the Azure Communication Services SDKs can be used to build applications that enable bring your own identity (BYOI) users to start 1:1 calls with Teams users. [Standard Azure Communication Services pricing](https://azure.microsoft.com/pricing/details/communication-services/) applies to these users, but there's no extra fee for the interoperability capability. Custom applications built with Azure Communication Services to connect and communicate with Teams users or Teams voice applications can be used by end users or by bots, and there's no differentiation in how they appear to Teams users in Teams applications unless explicitly indicated by the developer of the application with a display name.
 
-To enable calling and chat between your Communication Services users and Teams tenant, allow your tenant via the [form](https://forms.office.com/r/F3WLqPjw0D) and enable the connection between the tenant and Communication Services resource.
+To enable calling between your Communication Services users and Teams tenant, allow your tenant via the [form](https://forms.office.com/r/F3WLqPjw0D) and enable the connection between the tenant and Communication Services resource.
 
 [!INCLUDE [Enable interoperability in your Teams tenant](./../includes/enable-interoperability-for-teams-tenant.md)]
 ## Get Teams user ID
 
-To start a call or chat with a Teams user or Teams Voice application, you need an identifier of the target. You have the following options to retrieve the ID:
+To start a call with a Teams user or Teams Voice application, you need an identifier of the target. You have the following options to retrieve the ID:
 - User interface of [Microsoft Entra ID](../troubleshooting-info.md?#getting-user-id) or with on-premises directory synchronization [Microsoft Entra Connect](../../../active-directory/hybrid/how-to-connect-sync-whatis.md)
 - Programmatically via [Microsoft Graph API](/graph/api/resources/users)
 
@@ -60,39 +55,7 @@ const call = callAgent.startCall([teamsCallee]);
 - Many features in the Teams client don't work as expected during 1:1 calls with Communication Services users.
 - Third-party [devices for Teams](/MicrosoftTeams/devices/teams-ip-phones) and [Skype IP phones](/skypeforbusiness/certification/devices-ip-phones) aren't supported.
 
-## Chat
-With the Chat SDK, Communication Services users or endpoints can have group chats with Teams users, identified by their Microsoft Entra object ID. You can easily modify an existing application that creates chats with other Communication Services users to create chats with Teams users instead. Here is an example of how to use the Chat SDK to add Teams users as participants. To learn how to use Chat SDK to send a message, manage participants, and more, see our [quickstart](../../quickstarts/chat/get-started.md?pivots=programming-language-javascript).
-
-Creating a chat with a Teams user:
-```js
-async function createChatThread() { 
-const createChatThreadRequest = {  topic: "Hello, World!"  }; 
-const createChatThreadOptions = {
-    participants: [ { 
-        id: { microsoftTeamsUserId: '<Teams User AAD Object ID>' }, 
-        displayName: '<USER_DISPLAY_NAME>' }
-    ] }; 
-const createChatThreadResult = await chatClient.createChatThread( 
-createChatThreadRequest, createChatThreadOptions ); 
-const threadId = createChatThreadResult.chatThread.id; return threadId; }
-```                                         
-
-To make testing easier, we've published a sample app [here](https://github.com/Azure-Samples/communication-services-web-chat-hero/tree/teams-interop-chat-adhoc). Update the app with your Communication Services resource, and interop enabled Teams tenant to get started. 
-
-**Limitations and known issues** </br>
-While in private preview, a Communication Services user can do various actions using the Communication Services Chat SDK, including sending and receiving plain and rich text messages, typing indicators, read receipts, real-time notifications, and more. However, most of the Teams chat features aren't supported. Here are some key behaviors and known issues:
-- Communication Services users can only initiate chats. 
--    Communication Services users can't send images, or files to the Teams user. But they can receive images and files from the Teams user. Links to files and images can also be shared.
--    Communication Services users can delete the chat. This action removes the Teams user from the chat thread and hides the message history from the Teams client.
-- Known issue: Communication Services users aren't displayed correctly in the participant list. They're currently displayed as External, but their people cards show inconsistent data. In addition, their displayname might not be shown properly in the Teams client.
-- Known issue: The typing event from Teams side might contain a blank display name.
-- Known issue: Read receipts aren't supported for Teams users.
-- Known issue: A chat can't be escalated to a call from within the Teams app. 
-- Known issue: Editing of messages by the Teams user isn't supported.
-
-Please refer to [Chat Capabilities](../interop/guest/capabilities.md) to learn more. 
-
 ## Privacy
-Interoperability between Azure Communication Services and Microsoft Teams enables your applications and users to participate in Teams calls, meetings, and chats. It is your responsibility to ensure that the users of your application are notified when recording or transcription are enabled in a Teams call or meeting.
+Interoperability between Azure Communication Services and Microsoft Teams enables your applications and users to participate in Teams calls and meetings. It is your responsibility to ensure that the users of your application are notified when recording or transcription are enabled in a Teams call or meeting.
 
 Microsoft will indicate via the Azure Communication Services API that recording or transcription has commenced. 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 due to your failure to comply with this obligation.

articles/azure-maps/how-to-dev-guide-js-sdk.md

@@ -37,7 +37,7 @@ Following this tutorial will:
 - [Visual Studio Code](https://code.visualstudio.com/) on one of the [supported platforms](https://code.visualstudio.com/docs/supporting/requirements#_platforms).
 - [Node.js](https://nodejs.org/), Active LTS and Maintenance LTS versions [Node 18 LTS](https://nodejs.org/en) is recommended. Use the `node --version` command to check your version.
 - An Azure Communication Services resource. [Create a Communications Resource](../../quickstarts/create-communication-resource.md)
-- Complete the Teams tenant setup in [Teams calling and chat interoperability](../../concepts/interop/calling-chat.md)
+- Complete the Teams tenant setup in [Teams Call Queues](../../quickstarts/voice-video-calling/get-started-teams-call-queue.md)
 - Working with [Teams Call Queues](../../quickstarts/voice-video-calling/get-started-teams-call-queue.md) and Azure Communication Services.
 - Working with [Teams Auto Attendants](../../quickstarts/voice-video-calling/get-started-teams-auto-attendant.md) and Azure Communication Services.
 

articles/communication-services/concepts/interop/calling-chat.md

@@ -40,9 +40,6 @@ Be careful to restrict assignment of these roles only to those who require the a
 
 When a client sends a request to an Event Grid topic or domain, the client establishes a connection with the Event Grid topic or domain endpoint first, before processing any requests. The minimum TLS version setting is checked after the TLS connection is established. If the request uses an earlier version of TLS than that specified by the setting, the connection continues to succeed, but the request will eventually fail.
 
-> [!NOTE]
-> Due to limitations in the confluent library, errors coming from an invalid TLS version will not surface when connecting through the Kafka protocol. Instead a general exception will be shown.
-
 Here are a few important points to consider:
 
 - A network trace would show the successful establishment of a TCP connection and successful TLS negotiation, before a 401 is returned if the TLS version used is less than the minimum TLS version configured.

articles/communication-services/tutorials/calling-widget/calling-widget-tutorial.md

@@ -64,8 +64,7 @@ The Azure API for FHIR supports the following query parameters. All of these par
 | \_typefilter | Yes | To request finer-grained filtering, you can use \_typefilter along with the \_type parameter. The value of the _typeFilter parameter is a comma-separated list of FHIR queries that further restrict the results |
 | \_container | No |  Specifies the container within the configured storage account where the data should be exported. If a container is specified, the data will be exported into a folder into that container. If the container isn’t specified, the data will be exported to a new container. |
 | \_till | No |  Allows you to only export resources that have been modified till the time provided. This parameter is applicable to only System-Level export. In this case, if historical versions have not been disabled or purged, export guarantees true snapshot view, or, in other words, enables time travel. |
-|\_includeHistory | No | Allows you to export versioned resources. This filter does'nt work with '_typeFilter' query parameter. |
-|\_includeDeleted | No | Allows you to export soft deleted resources. To learn more about delete, refer to [delete using FHIR specification](https://www.hl7.org/fhir/http.html#delete). This filter does'nt work with '_typeFilter' query parameter. |
+|\includeAssociatedData | No | Allows you to export history and soft deleted resources. This filter doesn't work with '_typeFilter' query parameter. Include value as 'history' to export history/ non latest versioned resources. Include value as 'deleted' to export soft deleted resources. |
 
 > [!NOTE]
 > Only storage accounts in the same subscription as that for Azure API for FHIR are allowed to be registered as the destination for $export operations.

articles/event-grid/transport-layer-security-enforce-minimum-version.md

@@ -66,8 +66,7 @@ The FHIR service supports the following query parameters for filtering exported
 | `_typeFilter` | Yes | To request finer-grained filtering, you can use `_typeFilter` along with the `_type` parameter. The value of the `_typeFilter` parameter is a comma-separated list of FHIR queries that further limit the results. |
 | `_container` | No |  Specifies the name of the container in the configured storage account where the data should be exported. If a container is specified, the data will be exported into a folder in that container. If the container isn't specified, the data will be exported to a new container with an autogenerated name. |
 | `_till` | No |  Allows you to export resources that have been modified till the specified time. This parameter is applicable only with System-Level export. In this case, if historical versions have not been disabled or purged, export guarantees true snapshot view, or, in other words, enables time travel. |
-|`__includeHistory` | No | Allows you to export versioned resources. This filter does'nt work with '_typeFilter' query parameter. |
-|`_includeDeleted` | No | Allows you to export soft deleted resources. To learn more about delete, refer to [delete using FHIR specification](https://www.hl7.org/fhir/http.html#delete). This filter does'nt work with '_typeFilter' query parameter. |
+|`includeAssociatedData` | No | Allows you to export history and soft deleted resources. This filter doesn't work with '_typeFilter' query parameter. Include value as 'history' to export history/ non latest versioned resources. Include value as 'deleted' to export soft deleted resources. |
 > [!NOTE]
 > Only storage accounts in the same subscription as the FHIR service are allowed to be registered as the destination for `$export` operations.