Introduction
These are the known limitations of the Microsoft Teams integration. They are inherent to the current design and to the capabilities of the Microsoft Teams (Microsoft Graph) API, and they apply to all subscribers at the time this documentation was written.
Platform Scope and Tested Versions
Remote platform: Microsoft Teams, through the Microsoft Graph API.
API host: https://graph.microsoft.com
API version: Microsoft Graph v1.0. Microsoft does not version this API with dated, subscriber-selectable namespaces; the integration was built against the documented v1.0 production endpoints as of the tested-on date below.
Last tested end-to-end: 2026-06-24.
Not built for: Microsoft products and surfaces other than Teams channel and chat messaging (for example, Outlook mail, SharePoint, or OneDrive). If Microsoft introduces a separate product line or a materially different API version in the future, this integration will not automatically support it.
1. Messages are created, not updated
This integration posts a new message each time a message record is dispatched from iPaaS.com. Re-sending does not edit a previously posted Teams message.
What this means for you: To convey revised information, dispatch a new message. There is no need to locate or modify the original Teams message.
2. An unmatched channel name posts to the first channel
When a message is delivered to a channel, the integration resolves the destination by matching the configured channel name against the channels in the team. If no channel with that name is found, the message is posted to the first channel in the team rather than failing.
What this means for you: Confirm the channel name is spelled exactly as it appears in Microsoft Teams before enabling the collection, so messages are not posted to an unintended channel, at the time this documentation was written.
3. One destination per message
A message is delivered to a single destination — either a Teams channel or a chat. If both a channel and a chat are resolved for the same message, the message is not sent and an error is recorded.
What this means for you: Map either the channel field or the chat field for a message, not both. See the Microsoft Teams Error Messages article for the related error.
4. Outbound only
This integration delivers messages from iPaaS.com to Microsoft Teams. It does not read, retrieve, or monitor messages from Microsoft Teams, and it does not perform a bulk import on first connect — messages are sent as they are dispatched.
What this means for you: Use this integration to send notifications into Teams. Reading Teams activity back into iPaaS.com is not part of this integration.
5. Placeholder Values to Replace Before Go-Live
The integration ships with sample values that each subscriber must replace before going live.
Where | Placeholder value | Replace with |
Channel name in the message mapping | TestChannel | The display name of the channel you want messages posted to. |
Teams Group ID subscription setting | sample team ID | The Group ID of the team that owns your destination channel (see the Connections and Settings article). |
Closing
This article covers five known limitations. For detailed configuration guidance, see the Microsoft Teams Channel Message From iPaaS.com Mapping Documentation and the Microsoft Teams Connections and Settings article.