Power Automate – Unable to Post Adaptive Card to Teams Agent (Copilot Studio New Experience)

(1) Share

Report

Posted on by S-Venkadesh

1,208 Super User 2026 Season 1

Hi everyone,
I’m trying to post an Adaptive Card from a Power Automate flow to an agent hosted in Microsoft Teams.
This scenario works correctly for a Classic Agent (old Copilot Studio experience). However, it is not working for an agent developed using the new Copilot Studio experience.
I’m encountering the following error:

Error Code: 400 (Bad Request)
Error Message: We couldn't find your bot.

Has anyone experienced this issue with the new Copilot Studio agents?
Are there any changes in configuration or limitations compared to the classic experience?
Any clarification or documentation pointers would be greatly appreciated.
Thanks in advance!

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

11manish 3,210 on at

Like
a
(0)

Report
Copy link

Link copied!
Since:

The flow works with a Classic Agent.

The same flow returns "We couldn't find your bot" for a new Copilot Studio agent.

This strongly suggests the issue is related to the new agent's Teams registration or current product support, rather than the Adaptive Card payload.

Recommendation

If all configuration appears correct, this may be a current limitation or unsupported scenario with the new Copilot Studio experience.

Microsoft has changed the architecture of the new agents, and not all integrations available for classic agents have reached feature parity.

Raise the Microsoft Support ticket for more clarity.

Was this reply helpful? Yes No
Suggested answer

Assisted by AI

sannavajjala87 388 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

This is actually expected behavior with the new Copilot Studio agents.
The Teams “Post adaptive card as bot” action still relies on the Bot Framework registration, which works fine for classic agents. But the new Copilot Studio agents use a different architecture, and they’re not fully wired up for all those integrations yet.
That’s why you get “We couldn’t find your bot”, it’s not your card or flow, it’s that the new agent isn’t exposed the same way in Teams.
Bottom line:
Right now this scenario isn’t fully supported for new agents. If you need this to work, stick with a classic agent or use an alternate approach (like posting as user / webhook).
If this is critical, raising a support ticket is worth it, this is clearly a feature gap, not a config issue

Was this reply helpful? Yes No
Suggested answer

Valantis 6,656 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @S-Venkadesh,

This is a confirmed feature parity gap, not a configuration issue.

The Power Automate "Post adaptive card as the bot" and "Post adaptive card and wait for a response" actions use the Bot Framework registration to identify and post as the bot. Classic Copilot Studio agents have a traditional Bot Framework app registration that these actions can reference. The new Copilot Studio agent experience uses a different architecture and the Teams app registration is structured differently, which is why the action can't find the bot.

A community analysis from June 2026 confirms: "The channel publishing experience has changed, the new editor only has Teams, Copilot, Demo website and embed as channels to publish." The new experience is still not under General Availability, so not all classic agent integrations have feature parity yet.

Practical alternatives while this gap exists:
1. Keep using a classic agent for flows that need to post adaptive cards as a bot. Classic agents have full feature parity with the Power Automate Teams connector actions.

2. Post the adaptive card as a user instead of as the bot, using "Post an adaptive card to a Teams channel or chat" with the User option. This works regardless of agent type.

3. Use a webhook approach: post the card to a Teams incoming webhook endpoint. No bot registration needed.

4. Raise a Microsoft support ticket or submit feedback at feedbackportal.microsoft.com to register demand for feature parity in the new experience.
Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/whats-new

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

Vish WR 3,730 on at

Like
a
(0)

Report
Copy link

Link copied!

@S-Venkadesh

Hi,

Based on your description, this appears to be a limitation of the new Copilot Studio experience rather than an issue with your Adaptive Card or flow configuration.

Since the same flow works with a Classic Agent but returns “We couldn’t find your bot” for a new Copilot Studio agent, it indicates that the new agent architecture doesn’t currently support this integration in the same way. The Power Automate Teams actions that post adaptive cards as a bot rely on the Bot Framework registration, which isn’t exposed the same way for the new agents.

If your configuration is correct, I’d recommend raising a Microsoft Support ticket, as this appears to be a current feature parity gap rather than a configuration issue. In the meantime, consider using a Classic Agent or an alternative approach, such as posting the adaptive card as a user, if it meets your requirements.

Was this reply helpful? Yes No