Skip to main content
incident.io runs the whole incident lifecycle on Microsoft Teams. You declare incidents, get a channel for each one, assign roles, post updates, page on-call responders, run Investigations, and write postmortems, without leaving Teams. Some capabilities work differently there. Most of them depend on Slack platform features that the Microsoft Teams platform doesn’t support, so we’ve built the closest equivalent instead. This page lists every difference we know about, so you can weigh them before you choose. None of them stop you running incidents on Teams.
An organization has one primary communications platform. Choose Slack or Microsoft Teams when you sign up. You can’t run both at once, so talk to your support contact before you move between them. See why incident.io requires a communications platform.

​
What works the same

Most of incident.io doesn’t touch your comms platform, so it behaves identically on either one: postmortems, status pages, Insights, custom fields, incident types, severities, incident roles, and follow-ups. These do post to your platform, and work on both:

​
How you drive incident.io

In Slack, you drive incident.io by talking to it: /inc and its subcommands, tagging @incident, and reacting to messages with emoji. In Microsoft Teams, our bot posts notifications and doesn’t take messages back. You drive incident.io from the buttons and forms on the messages it posts, from the incident.io tab in the incident channel, and from the dashboard and mobile app.

​
Incident channels

See choosing where incident channels are created for how the team expression works.

​
Private incidents

Private incidents work on both platforms. In Slack, a private incident gets a private channel; in Teams they use a group chat. While Microsoft Teams has private channels, they are severely limited, so private incidents live in chats instead. Teams also needs one extra tenant-wide permission for this. See the permission Teams needs.

​
Messages in the channel

​
AI and suggestions

​
Streams

Streams work on Teams, but you create and manage them from the dashboard. They don’t get a channel of their own.

​
On-call and reporting

On-call reaches people the same way on both platforms. Only the last two rows differ. Syncing a schedule to a user group keeps a group such as @platform-on-call in step with whoever is currently on-call, so anyone in the company can reach the right person by mentioning it. Teams has no equivalent, so people reach on-call through an escalation instead.

​
The permission Teams needs

Private incidents on Teams need Chat.Create, which is one of only two permissions incident.io asks for across your whole tenant. Your Microsoft admin consents to it once, during installation. Chat.Create lets us create new group chats, and nothing else. It carries no read access, so it can’t read or access the chats that already exist in your tenant. Everything else we ask for is scoped to the single team we’re installed in, or to the incident chats we create. For the full list, with a purpose for each permission, see permissions in Microsoft Teams. If a security or IT team is reviewing the install, send them securing incident.io in Microsoft Teams.

​
FAQs

Yes. It drafts updates, creates follow-ups, changes severity, answers questions about the incident, and queries your telemetry.A few of its abilities are Slack only, so check what @incident can do for the current list.