Collaboration
Microsoft Teams
The same slash-command grammar and comment mirroring as Slack, delivered as a Teams bot: @-mention commands, mirrored channel comments, and posted notifications. A separate adapter from Slack, defaulting to EU residency.
BidirectionalData residency: EU
Request a demoWhat it does
- @bot itsm new|resolve|assign|help commands (shared grammar with Slack), actor always the verified Teams user
- Channel messages mirror as ticket comments (the bot's own messages are dropped to prevent an echo loop)
- Outbound: incident created/assigned, SLA-at-risk, and war-room notifications posted as an Adaptive Card
- Inbound activities are verified today via the platform's HMAC signed-webhook scheme; full Bot Framework JWT validation is a planned follow-on
- EU-resident by default, reflecting a typical EU tenant's Microsoft 365 region
Data residency
Teams data resides per the tenant's Microsoft 365 region. The manifest defaults to EU — typical for an EU SMB's M365 tenant — reconciled per-row against the tenant's declared region.
Event mappings
| External event | Maps to | What happens |
|---|---|---|
| bot.command.itsm | incident | @bot itsm new|resolve|assign commands act on incidents (server-derived actor) |
| bot.message.channel | ticket_comment | A channel message in a mirrored team posts as a ticket comment (bot echoes dropped) |
What you configure
- Entra tenant ID
- Bot Framework app (client) ID
- Default team ID + channel ID for notifications
- Bot Framework service URL (regional endpoint override)
- Data residency (eu default, us/hybrid)
- Bot secret configured (flag)
- War-room channel mirroring on/off
OAuth scopes requested
- https://api.botframework.com/.default
Setup overview
Register a Bot Framework app in the tenant's Entra ID, store its secret, and set the default team/channel for notifications. Declare your M365 tenant's actual data residency if it isn't EU.
Related features
See TENSOR running on your own estate.
30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.