Copilot Studio new: Post Adaptive Card to Teams agent via Teams connector and wait for response

(2) Share

Report

Posted on by S-Venkadesh

1,208 Super User 2026 Season 1

Hi Everyone,

I’m trying to post an Adaptive Card to an agent hosted in Microsoft Teams using the Teams Connector (Post Adaptive Card and wait for response) in Copilot Studio.
In the new Copilot Studio experience, I only see 3 input parameters available to configure for the Teams connector.
However, in the old experience, there were 4 key parameters, as shown below:
Old Experience Configuration:

Post as: Microsoft Copilot Studio Agent
Post in: Chat with Agent
Recipient: user@contoso.com
Message: <adaptive-card-json>
Update Message:

In the new experience, I only see:

Recipient
Message
Update Message

I’m trying to understand:

What happened to the “Post as” and “Post in” parameters in the new experience?
Are these handled implicitly now, or is there a different way to configure them?

Old Experience:

NEW Experience:

Any clarification or documentation pointers would be really helpful.
Thanks in advance!

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

sannavajjala87 388 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

what you’re seeing is expected in the new Copilot Studio experience. The “Post as” and “Post in” parameters haven’t been removed but are now handled implicitly by the platform based on the execution context. In other words, the action automatically posts as the Copilot Studio agent and sends the adaptive card in the current conversation (such as a Teams chat) without requiring explicit configuration. The new UI simplifies the setup by only exposing the fields you need to control. Recipient, Message, and Update Message, while the rest is inferred by the runtime.

Was this reply helpful? Yes No
Suggested answer

sannavajjala87 388 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

what you’re seeing is expected in the new Copilot Studio experience. The “Post as” and “Post in” parameters haven’t been removed but are now handled implicitly by the platform based on the execution context. In other words, the action automatically posts as the Copilot Studio agent and sends the adaptive card in the current conversation (such as a Teams chat) without requiring explicit configuration. The new UI simplifies the setup by only exposing the fields you need to control. Recipient, Message, and Update Message, while the rest is inferred by the runtime.

Was this reply helpful? Yes No
Suggested answer

Haque 3,596 on at

Like
a
(1)

Report
Copy link

Link copied!
Q-1: What happened to the “Post as” and “Post in” parameters in the new experience?

A-1: Both parameters have been removed from the “Post adaptive card and wait for response” action. They are now handled implicitly by the platform. So the card is always posted as the Microsoft Copilot Studio Agent (the bot identity is fixed). Also, the card is always posted in a 1:1 chat with the specified recipient ( Note: posting in channels or group chats is not supported by this action).

Q-2: Are these handled implicitly now, or is there a different way to configure them?

A-2: Answered in Q-1, Yes, these parameters are now handled implicitly by the platform and cannot be configured directly in the new experience.

Reference:

Post adaptive card and wait for a response

Adaptive Cards overview

Was this reply helpful? Yes No