> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Installing your incident.io trial in Microsoft Teams

This guide is for a Microsoft administrator installing incident.io in Microsoft Teams for a trial. It assumes you'll run the whole install yourself, using the incident.io setup link shared with you (you may have received it from a colleague running the incident.io trial, or directly from the incident.io team).

You'll need to be a **Global Administrator** or **Privileged Role Administrator**, since installing incident.io means granting admin consent to a set of Microsoft Graph permissions that only those roles can approve.

If your security or IT team wants to review before you install, the [security overview](/getting-started/securing-teams) covers what the app does, the exact permissions and how they're scoped, and how to revoke access.

The setup link already has your plan and trial configured, so you won't be asked to choose a plan during setup. If you've seen the [public self-serve guide](/getting-started/installing-teams), you can ignore its plan selection step.

## Installation

Follow these steps to get incident.io running in your Microsoft tenant.

<Steps>
  <Step title="Sign in with Microsoft">
    Open the setup link and click **Continue with Microsoft**. You'll be asked to consent to a small set of sign-in permissions that only identify you, so you don't need to tick *Consent on behalf of your organization* at this stage.
  </Step>

  <Step title="Grant admin consent">
    incident.io first needs consent to see the teams, channels, and users in your account, granted through Microsoft's standard admin consent flow. This read access alone doesn't let incident.io create a team or install the app; that happens in the next step.

    You can grant consent during setup, or directly in Microsoft Entra ID.

    **Consent during setup (recommended):**

    1. Click **Connect your Microsoft account**.
    2. Complete the consent in Microsoft.

    **Consent in Entra ID:**

    If you'd rather grant consent directly in the Microsoft admin center:

    1. Go to **Enterprise Applications** → **incident.io** → **Permissions** → **Grant admin consent**.
    2. Return to the setup flow, which will re-check that consent is in place and let you continue.
  </Step>

  <Step title="Install incident.io">
    With consent granted, install incident.io into Microsoft Teams. You can let incident.io set this up automatically, or install it manually yourself.

    **Install automatically (recommended):**

    Click **Install to Microsoft Teams**. incident.io will:

    * Create an *Incidents* team where incidents are managed
    * Add the incident.io app to that team
    * Give the app access to the *Incidents* team only, and nothing else in your account

    To do this, Microsoft prompts you to grant two short-lived permissions, `Team.Create` and `TeamsAppInstallation.ReadWriteAndConsentForTeam`. They're granted for one hour only and expire automatically afterward. Installation can take a couple of minutes, so don't navigate away.

    **Install manually:**

    If you'd rather not grant those permissions, or your tenant blocks automated installs, add incident.io from the Microsoft Teams Store instead:

    1. Create a new *Incidents* team in Microsoft Teams, or choose an existing team to reuse.
    2. Right-click the team and click **Manage team**.
    3. Open the **Apps** tab and click **Get more apps**.
    4. Search for **incident.io** and open our listing.
    5. In the **Add** dropdown, click **Add to team**.
    6. Choose the team to install into, then click **Set up**.
  </Step>

  <Step title="You're done">
    You should now have an *Incidents* team with a *General* channel and an incident.io tab. Anyone on the team can declare an incident from there or from [app.incident.io](https://app.incident.io).

    From here you might want to:

    * **Set up single sign-on.** People already sign in with their Microsoft credentials by default. For tighter control, or to use a different identity provider, you can enable [SAML SSO](/admin/saml-sso).
    * **Automate user provisioning.** Use [SCIM](/admin/scim) so accounts and roles follow your directory automatically.
  </Step>
</Steps>