question MS Teams Integration impact on Integration Hub Transaction usage in MS Teams forum

MS Teams Integration impact on Integration Hub Transaction usage

WayneHadley — Thu, 08 Jan 2026 12:22:40 GMT

We are giving some consideration to doing a MS Team integration and one of the questions that has come up is the potential impact this will have on our iHub transaction volumes. We currently have the 1 million tier and are wondering if doing this integration will push us into the next tier and thus increase costs. ** in 2025 we used 500k.

I'd be interested in learning what others have experienced in terms of transaction volume impact and whether you may have used any sort of scenario-based calculator to estimate the impact.

Thank you in advance for your responses.

Re: MS Teams Integration impact on Integration Hub Transaction usage

Itallo Brandão — Thu, 08 Jan 2026 13:19:48 GMT

Hi Wayne,

Yes, the Microsoft Teams integration will definitely impact your Integration Hub transaction volume, specifically if you are using the Microsoft Teams Spoke in Flow Designer to send notifications, post adaptive cards, or manage channels.

Since you have a 500k buffer (1M limit - 500k used), you have roughly ~41,600 transactions per month available to play with. Whether this pushes you into the next tier depends entirely on "how chatty" you design your flows to be.

Here is the logic to estimate the impact:

1. The Calculation Formula Unlike email (which is "free" in terms of transactions), every outbound call to Teams counts.

Total Transactions = (Number of Tickets) x (Triggers per Ticket)

2. Scenario A: High Impact (The "Chatty" Approach) If you configure a Flow to send a Teams message every time a comment is added or state changes on an Incident:

Volume: 5,000 Incidents/month.
Updates: Avg 5 updates per ticket (Open, Assign, WIP, Comment, Resolve).
Math: 5,000 x 5 = 25,000 transactions/month.
Result: This eats up more than half your buffer.

3. Scenario B: Low Impact (High Value Approach) If you only use Teams for Actionable Notifications (e.g., Approvals and Major Incidents):

Volume: 1,000 Change Requests/month.
Updates: 1 Approval Request card.
Math: 1,000 x 1 = 1,000 transactions/month.
Result: Negligible impact.

Recommendation: Start by enabling the integration for Actionable Notifications (Approvals) first. This provides the highest ROI (faster approvals) with the lowest transaction footprint. Avoid mirroring "All Comments" to Teams unless you are sure the volume fits within your ~1,300 daily transaction buffer.

Hope this helps you calculate the risk!

If this response helps you plan your integration, please mark it as Accepted Solution.
This helps the community grow and assists others in finding valid answers faster.

Best regards,
Brandão.

Re: MS Teams Integration impact on Integration Hub Transaction usage

WayneHadley — Fri, 09 Jan 2026 12:58:25 GMT

@Itallo Brandão thank you! This is exactly what I was looking for.

Re: MS Teams Integration impact on Integration Hub Transaction usage

Itallo Brandão — Fri, 09 Jan 2026 15:09:50 GMT

You are welcome, Wayne! Glad to help.

Feel free to connect with me on LinkedIn: https://www.linkedin.com/in/itallobrandao/

Best regards, Brandão.