Power Platform Community Forum Thread Details

Get notification in Microsoft Agent App in teams instead of workflows teams notification

Scenario:

I have copilot studio agent and published in teams and 365 app. Any message it will send to topic or flow and get response show in team message.

In some topic the request message is send to http action of power automate flow where it has two inputs one is requestor email and user query, it pass these two inputs invoking post method of http action flow and once that http response send back requestor email and query results and these two results sending to teams webhook http power automate flow and from body of webhook itnhas email and query results I'm passing it to post a message in a chat or channel action in flow where currently I chose flow bot and recipient is requestor email from webhook body and in message body is query results from the webhook body.

Now expected notification:

Above flow of output is sending workflow notification to user in personal chat instead I want to send this notification to copilot studio agent app which we installed

I tried this in proactive message in chat action by choosing agent bot name which I created it shows errors bad gateway or kind of not support

What is best approach to achieve above usecase? Looking for assistance on this

Categories:

General

Hey @CU14101439-0,

What you are seeing is mostly a channel / bot-identity limitation, not a configuration bug.
Right now:

Your Copilot Studio agent is one bot in Teams (the “agent app”).
Power Automate flows that “Post a message in a chat or channel” use the Power Automate (Flow) bot or a Teams app/bot configured for that action.
You cannot arbitrarily “impersonate” your Copilot Studio agent from a standard Power Automate Teams connector call.

That’s why trying to send a proactive message and selecting the Copilot agent as the bot results in errors such as “Bad Gateway / not supported”.

What is supported
To send notifications that appear to come from your Copilot Studio agent (not the Flow bot), the supported patterns are:

Use Copilot Studio’s built-in “Proactive message” / “Send message” capability
- The agent itself calls Power Automate (HTTP action or Power Automate action) to do the work.
- When the flow finishes, it returns the result to the agent.
- The agent then sends the response back to the user in the same conversation.
- In this pattern, the user always sees messages from the agent app, not from the Flow bot.
Keep Power Automate for background work, but let the agent control the user-facing messages
- Flow does the processing and returns a simple result (e.g., via HTTP response or a Dataverse/SharePoint update).
- A topic in Copilot polls or is triggered to read that result and respond to the user.
- Again, only the agent is talking to the user in Teams.
If you need out-of-band notifications (later / async)
Copilot Studio today has limited support for truly asynchronous proactive messages into Teams. The safest, supported approach is:
- Use the Flow bot or an Azure Bot Framework bot for proactive notifications,
- Or redesign the experience to have the user come back to the agent and ask, “What’s the status of X?” so the agent pulls and shows the latest result.

What you cannot reliably do (today)

Use a generic “Post message in chat or channel” Power Automate action and make it appear as if it is the Copilot Studio agent app.
Use Teams webhook → Flow → “Proactive message” to directly address the Copilot Studio agent as the sender (this is what’s giving you Bad Gateway / unsupported errors).

Those paths are not supported for Copilot Studio agents currently.

Recommended approach for your scenario
Given your description (HTTP-triggered flow, requestor email, query results):

Keep the HTTP flow to do the heavy work.
Have the flow return the result back to the agent instead of posting through the Flow bot.
Let the agent surface the response to the user in the same conversation (or on next turn) using a normal message node.

That way, all visible messages stay inside the Copilot Studio agent app, and you avoid unsupported bot-impersonation patterns.

Quick Links