You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Service Name: IC3 ACS Chat Review Created By: Cheuk Chuen Siow Review Date: 01/14/2025 01:00 PM PT Release Plan: PR: #31243 Hero Scenarios Link: Not Provided Core Concepts Doc Link: Not Provided
Description: ACS Chat faces several concerns regarding the existing bot channel implementation:
Only partial support to a subset of bot activities
Certain properties of supported bot activities are being discarded during transit
Inability to enrich messages for bots to consume
Unable to propagate thread and participant metadata to bots
The way we currently implement bot channel integration is not ideal. We're reserving a space in chat message metadata that is meant to be reserved for Contoso's usage, and having json string payload in the message content.
We're introducing new message types (AzureBotActivity and AzureBotCommand) in ChatMessageType enum, enabling ACS Chat to act as transport layer so that the entire bot payload can be sent and received by Azure bots in the form of bot activity.
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here
The text was updated successfully, but these errors were encountered:
Azure Versioning policy requires any change to service behavior / API surface be done in a new API version. Please make the proposed changes in a new API version or explain why this is not possible / practical.
New API Review meeting has been requested.
Service Name: IC3 ACS Chat
Review Created By: Cheuk Chuen Siow
Review Date: 01/14/2025 01:00 PM PT
Release Plan:
PR: #31243
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: ACS Chat faces several concerns regarding the existing bot channel implementation:
The way we currently implement bot channel integration is not ideal. We're reserving a space in chat message metadata that is meant to be reserved for Contoso's usage, and having json string payload in the message content.
We're introducing new message types (AzureBotActivity and AzureBotCommand) in ChatMessageType enum, enabling ACS Chat to act as transport layer so that the entire bot payload can be sent and received by Azure bots in the form of bot activity.
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here
The text was updated successfully, but these errors were encountered: