Skip to main content
To sign up for incident.io using Microsoft Teams, please visit this link. You can read more about the permissions we ask for.

​
Signing up

​
Step 1: Sign in with Microsoft

We need these permissions to identify you, so you don’t need to tick “Consent on behalf of your organization”.

​
Step 3: Select a plan

Select a plan that would be a good fit for your organization. This will help us connect you with the right people on our team.

​
Step 4: Grant “global permissions”

You must be a Microsoft admin to proceed with this step. If you’d like to learn more about our permissions, we have an article. This is the first of two steps that both look fairly similar, beware!

​
Installing our Teams app

​
Automatically

Step 1: Grant us temporary permissions In this part, we temporarily ask for permission to create a new “Incidents” team in Teams, and install our app to it. This may take a few minutes.

​
Manually

If you don’t want to give us permission, or your Microsoft tenant doesn’t allow us to install the application automatically, then:
  1. Create a new “Incidents” team — or choose a team you wish to reuse.
  2. Right click on the team, and choose “Manage team”.
  3. Go to the “Apps” tab and click “Get more apps”.
  4. Search for “incident.io” and click through to our listing.
  5. In the “Add” dropdown, click “Add to team”.
  6. Choose the team to install us into.
  7. Click “Set up” at the bottom right.
Once that’s done, you should be able to go back to https://app.incident.io, and declare an incident.

​
Troubleshooting

If you encounter a sign-in error while setting up incident.io with Microsoft Teams:
  1. Go to portal.azure.com
  2. Go to Enterprise applications and find the incident.io app
  3. Check the Sign-in logs and Access reviews sections for details about why the sign-in failed — your admin may be able to help resolve these
If that doesn’t help, go to the Diagnose and solve problems section in the sidebar and use the correlation ID from the error to diagnose the problem.If you’re still stuck, reach out to your support contact.
For incident.io to DM a Microsoft Teams user (e.g. to notify an incident lead), the incident.io app must be installed at the user level. We request the TeamsAppInstallation.ReadWriteAndConsentSelfForUser.All permission to handle this automatically, but sometimes the installation still fails.Verify whether the app is installed for a userMicrosoft doesn’t provide a UI for this, but you can use PowerShell:
Install-Module Microsoft.Graph.Teams -Scope CurrentUser

Connect-MgGraph -Scopes "TeamsAppInstallation.ReadForUser.All"
Get-MgUserTeamworkInstalledApp -UserId "user@domain.com" -ExpandProperty "teamsAppDefinition"
If incident.io doesn’t appear in the output, we won’t be able to DM that user. Compare the output against a user who does receive DMs to identify differences.Install the app manually via PowerShell
Connect-MgGraph -Scopes "TeamsAppInstallation.ReadWriteForUser.All"

$appId = "c878d453-b147-49d6-aab9-b912dcaee5ec"

$body = @{
    "teamsApp@odata.bind" = "https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/$appId"
}

New-MgUserTeamworkInstalledApp -UserId "user@domain.com" -BodyParameter $body
Any error returned here will indicate why the automatic installation failed.Ensure the app is installed via a Teams app policyTo prevent this issue across your organization:
  1. Sign in to admin.teams.microsoft.com
  2. Navigate to Teams apps → Setup policies
  3. Edit the Global policy (for all users) or create a new policy for specific users
  4. Under Installed apps, click Add apps, search for incident.io, and add it
  5. Save and assign the policy to the relevant users or groups
If a user loses their assigned role (for example, a Responder being reverted to Viewer) or appears as deactivated in incident.io despite still being active in Microsoft, this is most likely because we can’t tell that they’re still an active user in your Microsoft tenant.This doesn’t necessarily mean the user won’t be able to log in — but it does mean that they’ll periodically appear as deactivated and/or lose any roles they’ve been granted above Viewer.To make sure incident.io accounts get deactivated when the corresponding user leaves your Microsoft tenant or is deactivated in Microsoft, we periodically check each incident.io user against your Microsoft tenant. We do this by looking at the members of the Microsoft Teams team(s) where the incident.io bot is installed. If a user doesn’t appear in any of those teams — for example, because they only sign in to the incident.io dashboard, or only DM the bot — we won’t see them, and we’ll treat them as no longer active and deactivate their incident.io account.To resolve this, make sure the affected user is a member of a Microsoft Teams team that has the incident.io bot installed. You can do this either by:
  • Adding the user to a team where the bot is already installed, or
  • Installing the bot into a team that the user is already a member of.
Once they appear as a member of a team where our bot is installed, we’ll recognize them as still active and stop deactivating their account.If you continue to see users being deactivated after applying this, reach out to your support contact.

​
You’re done!

There should be a new “Incidents” team with a “General” channel and an incident.io tab where you can declare an incident.

​
Installing our Teams app into an existing team

Once you’ve installed our app for the first time (e.g. you have followed the Installing our Teams app section and have an ‘Incidents’ team), you’re also able to install us into other teams in your Teams workspace. By installing incident.io into your other teams, you’ll be able to:
  • Declare incidents from the incident.io tab from within that team
  • Create Announcement rules to send incident updates to that team
To add our app to another team:
  1. Choose a team you wish to add us into.
  2. Right click on the team, and choose “Manage team”.
  3. Go to the “Apps” tab and click “Get more apps”.
  4. Search for “incident.io” and click through to our listing.
  5. In the “Add” dropdown, click “Add to team”.
  6. Choose the team to install us into.
  7. Click “Set up” at the bottom right.