diff --git a/integrations/popular-integrations/microsoft-teams.mdx b/integrations/popular-integrations/microsoft-teams.mdx
index e61d4ec8..486db4ae 100644
--- a/integrations/popular-integrations/microsoft-teams.mdx
+++ b/integrations/popular-integrations/microsoft-teams.mdx
@@ -103,6 +103,29 @@ You can configure your agents to automatically respond to Teams messages by sett
Set tool permissions to "approval mode" initially so your agent asks before sending messages. Switch to autopilot once you're confident.
+## Attachment support
+
+Agents connected via Microsoft Teams can receive and process attachments sent in channels and chats.
+
+### Supported attachment types
+
+
+
+ Images pasted directly into the Teams message composer are sent to the agent for processing
+
+
+ Files attached via the Teams file picker (PDFs, documents, images, and other formats) are passed to the agent
+
+
+
+### Messages with only attachments
+
+If a user sends a message that contains attachments but no text, the agent receives a `[N attachments]` indicator (e.g., `[1 attachments]`) in place of the message body. The agent can use this signal to recognize that attachments were sent and respond accordingly.
+
+
+ The agent's ability to interpret attachment content depends on which tools and capabilities are configured for that agent.
+
+
## Agent Notifications

@@ -271,7 +294,7 @@ If you see "Need admin approval" or "This app requires admin approval", follow t
- Yes, files shared in Teams channels are stored in SharePoint. You can access them through the Microsoft API Call tool step via the Microsoft Graph API.
+ Yes, in two ways. First, agents can directly receive file uploads and inline images sent in a Teams message — these are passed as attachments when the trigger fires. Second, files shared in Teams channels are also stored in SharePoint, which you can access through the Microsoft API Call tool step via the Microsoft Graph API.