Microsoft Teams



You're viewing documentation for beta features. These features may change functionality or be removed before the final release.

This article describes setting up and managing your integration with Microsoft Teams. The FireHydrant MS Teams bot v2 allows driving incidents from end-to-end from Microsoft Teams.


  • You will need to reach out to our team to schedule a demo and get access to the beta
  • You will need Owner permissions in FireHydrant
  • You need to be logged in to a Service Account in your Microsoft ecosystem with elevated permissions, specifically:
    • Installing bots in your MS Teams instance
    • Access to all Teams you would like the bot to be able to post messages into



As with other FireHydrant integrations, we recommend authorizing Microsoft Teams with a Service Account in your Office ecosystem. This prevents problems if named users leave your organization and can help differentiate automated messages from messages posted by a real user.

Authorize the Integration on FireHydrant

  1. Go to FireHydrant's integrations page. Search for and click "Microsoft Teams (beta)".
  2. To initiate the integration, click "Authorize Application." This action will redirect you to your Microsoft login page for authentication. Ensure you're logged into a Service Account with proper permissions, and follow the on-screen prompts to complete the process.

This connects FireHydrant to your Microsoft Teams instance and allows us to post messages into channels across any teams the authorizing user can access, as well as create incident channels in specific Teams.

Installing the FireHydrant bot in Teams

Uploading a custom app

Uploading a custom app

  1. After authorizing the integration on FireHydrant, switch to Microsoft Teams. On the left-hand side, go to "+ Apps" > "Manage your apps" > "Upload an app".
  2. On this screen, click "Upload a custom app." Here, you will upload the application Zip file our team will provide.



Do not install the FireHydrant bot from the App directory. That is the existing legacy bot, which will be decommissioned upon GA of this v2 bot. At that point, this new bot will be installed via the App directory in Teams.

  1. On this page, click on the dropdown to the right of "Add" and click "Add to a team." Select a Team and primary channel (we recommend General) to install the bot and the FireHydrant tab. Click "Set Up."
    1. Note: You must install the bot for each Team that needs to access a FireHydrant tab and execute FireHydrant commands, like creating new incidents and participating in incidents.
  2. Once you click "Set Up", the modal should confirm the app has been configured and then direct you to press "Save" to mount the app. You can optionally post to the channel about the new FireHydrant tab installed.

User Logins

Finally, once the bot has been installed, users must log in to FireHydrant twice: once when executing commands, and the other when clicking into the Tab view.

Command Login

Logging in to execute bot commands

Logging in to execute bot commands

A user can initiate command login by executing @FireHydrant login. Alternatively, if they attempt to run any other commands, FireHydrant will automatically prompt for a login if they are not already.

Clicking the "Log in" button will open a browser window for the user to log into FireHydrant. Once they do so, their user account will be linked, and any @FireHydrant commands should start working.

Bot logins persist across all instances of MS Teams. So you only need to log in once via Command and you will be able to execute FireHydrant commands from e.g., MS Teams on your phone, MS Teams on desktop, web, etc.

Tab Login

FireHydrant Tab view

FireHydrant Tab view

The Tab view is each user's personal view of FireHydrant. It can be thought of as an additional portal into their FireHydrant account. So even though the Tab is installed on a shared channel, each user's view of it differs, and subsequently, they must log in to FireHydrant.

Like the above command flow, users can click the "Log in" button and follow the on-screen prompts to link to their user in the chosen FireHydrant organization.

They will see the list of all incidents they have access to, and if the tab exists in an incident channel, will be able to see and interact with the incident in that Tab as themselves.

Unlike Bot logins, Tab logins are local sessions and remain local to the device you log in with. To view FireHydrant incidents on the Tab on a different device, you must log in again on that device.

Multiple Organization Support

FireHydrant offers multiple Organizations to logically separate different business units, sandboxes from prod, etc. Users can log out of existing connections and log back in, authorizing the different organization they would like to switch to.

To remove your Teams integration

  1. Go to FireHydrant's integrations page and click Microsoft Teams (beta).
  2. Edit the MS Teams integration
  3. Select Uninstall
  4. Remove the bot from your Team/Workspace in Microsoft Teams

Next Steps