Issues with agent deployed to teams/365

(0) Share

Report

Posted on by DC-12021822-0

I have an agent that uses a custom connector for an MCP and it uses Oauth for authentication (Entra ID). It uses user credentials - we cannot use owner credentials. The agent is deployed through teams/365 channel

Issue #1 : When some users try to interact with the bot it will attempt to establish a connection but they get an error "create and authorize oauth connection failed" from the connector

Issue #2 : When I try to upload an image for use with the MCP, it only works on teams. When attaching an image in 365 the agent always replies with it not seeing any image. The image is a 20kb PNG file

Categories:

Publish & channel management

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Sam_Fawzi 917 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @DC-12021822-0

A couple of things would help narrow this down.
For Issue #1 (OAuth connection failed):

Are the affected users able to manually create the connector connection in Power Platform?

Does the custom connector use user delegated permissions in Entra ID?

Are the users assigned the same security roles / environment access as the users where it works?

Is the connector configured to allow shared connections, or does each user need to create their own connection on first use?

For Issue #2 (image not detected in M365 channel):

Can you confirm which Microsoft 365 channel you're using (Copilot / M365 chat / Outlook / etc.)?

Are you referencing the image through the message attachment object or expecting the agent to read it directly from the prompt?

If possible, sharing the activity payload or screenshot of the message structure would help confirm whether the attachment is being passed to the agent.

This should help determine whether the issue is channel limitations, connector permissions, or attachment handling differences between Teams and M365.

Was this reply helpful? Yes No
DC-12021822-0 10 on at

Like
a
(0)

Report
Copy link

Link copied!

@Sam_Fawzi we've resolved issue #1 it was a permissions problem.

For #2, this is for M365 chat - the chat that shows up when you go to https://m365.cloud.microsoft/
The image is uploaded directly by the user to the agent via "upload images and files"

I'm not sure how to find the activity payload or message structure from something outside of the copilot studio dashboard

Was this reply helpful? Yes No
Suggested answer

Sam_Fawzi 917 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @

For Issue #2, what you’re seeing is unfortunately a current limitation of the M365 Copilot Chat channel, not your agent or MCP implementation.
In short:

Teams bot channel supports user‑uploaded images and passes them through System.Activity.Attachments (with some size/type limits).

M365 Copilot Chat (https://m365.cloud.microsoft) does not reliably deliver image/file uploads to Copilot Studio agents today, even though the UI allows “Upload images and files”.

This is why:

The same agent works in Teams but reports “no image” in M365 chat.

The image never appears in the activity payload / attachments collection for the agent in M365.

The issue occurs regardless of file size (even small PNGs like your 20 KB file).

Microsoft has acknowledged this behavior in multiple community threads — at the moment, image uploads are effectively not supported for Copilot Studio agents in M365 Copilot Chat, whereas Teams is the supported path.

Recommended workarounds:

If image ingestion is required → use the Teams bot channel for that scenario.

For M365 chat → have users paste a SharePoint / OneDrive link to the image instead of uploading it directly.

Alternatively, embed the image in a document (PDF, DOCX) that the agent can access via connectors or knowledge sources.

Teams-only for image flows: If image input is core to the use case, consider restricting that capability to the Teams channel where attachment handling is supported.

Check for updates: Microsoft has been iterating on M365 channel capabilities — worth checking the Copilot Studio release notes to see if attachment support has been added recently.

Regarding activity payload visibility: there isn’t a supported way to inspect raw message payloads from M365 Copilot Chat outside of what Copilot Studio exposes — so you’re not missing anything there.

Hopefully that clarifies why you’re seeing the channel difference. You’ve already validated the agent side by confirming it works in Teams.

Ref: Solved: Agent does not identify images uploaded in deployed channels

Was this reply helpful? Yes No