-
Notifications
You must be signed in to change notification settings - Fork 53
Description
Is your feature request related to a problem? Please describe.
The Microsoft Teams Outbound Connector currently does not support sending Cards. This limits the ability to deliver rich, interactive messages (e.g., buttons) directly from a process to a Teams channel or chat.
Describe the solution you'd like
Extend the Microsoft Teams Outbound Connector to support sending cards via the Microsoft Graph attachments element.
Reference from Microsoft Graph documentation:
https://learn.microsoft.com/en-us/graph/api/chatmessage-post?view=graph-rest-1.0&tabs=http#example-3-send-a-message-containing-cards
Specifically, for:
Send message to channel
(Ideally also) Send message in chat
We propose adding a new optional field, for example:
Attachments JSON (Text / FEEL expression)
The value of this field should be passed into the Microsoft Graph attachments array when constructing the request body.
Describe alternatives you've considered
We considered using the REST Connector to call the Microsoft Graph API directly and post Cards. However, there are significant limitations:
- The REST Connector does not currently support refresh token authentication.
- Access tokens are short-lived, requiring token renewal.
- Microsoft Graph does not support client credentials flow for posting messages to Teams (application permissions are not sufficient for this scenario).
As a result, we would need to introduce an additional task in the process to:
Call Azure AD /oauth2/v2.0/token with grant_type=refresh_token
Obtain a new access_token
Use that token to post the Adaptive Card
This increases process complexity and introduces additional operational overhead that could be avoided if attachment element fields were built directly into the Teams Outbound Connector.
Additional context
Add any other context or screenshots about the feature request here.