Skip to main content
Setup time: 3 Min
Seamlessly integrate your MS Teams channels with All Quiet to streamline incident management directly within MS Teams.
The first part of this documentation focuses on creating the integration. The second explains how to send All Quiet incidents to your Microsoft Teams channels (Outbound). Want to create new incidents from your Microsoft Teams channels (Inbound)? Follow the third part of this guideline.
Unlike most of our integrations, this setup begins in your MS Teams channels instead of the All Quiet web app.

​
Add All Quiet to your MS Teams Channels

If you are a Team Member in MS Teams, ensure you have the necessary permissions to add an app. If not, contact your MS Teams Team Owner or IT Administrator for assistance.
  1. In the Microsoft Teams Application, click Apps.
  2. In the Search Bar, enter All Quiet.
  3. Select the All Quiet app (or, if you are a allquiet.eu user, the All Quiet EU app) from the search results and click Add or Open .
Next, click Add or Open in the Pop up. By using All Quiet, you grant the necessary permissions for the All Quiet MS Teams app. We only request permissions essential for the app to function effectively.
  1. Select the first MS Teams channel to integrate with All Quiet. Later, you can extend All Quiet to all channels within the same MS Team. If you’d like to use All Quiet with another MS Team, simply repeat this process and add it to a channel in that team.
  2. Click Go.
You will be redirected to the selected MS Teams channel, where you’ll receive a message from the All Quiet app. Click Connect All Quiet to link All Quiet with MS Teams. After that, you will be taken to your All Quiet Web App.
To establish the connection with All Quiet, you must log into your All Quiet account and be a member of at least one team in All Quiet.

​
Set up MS Teams Integration in All Quiet

You will be redirected to a draft page for your MS Teams integration in All Quiet.
  1. In the Display Name field, enter a name for your integration. For example, you can name it “MS Teams”.
  2. As All Quiet Team, select the All Quiet Team you want to connect with MS Teams. This will enable you to send incidents from this All Quiet Team to MS Teams and to create incidents in MS Teams to be sent back to this All Quiet team.
    Standard plan users: Later, you can connect additional All Quiet Teams using the “Connect” command in MS Teams. This will create an extra MS Teams integration for each All Quiet team.
    For Organizations with Pro and Enterprise plan: You will be able to add additional teams in the next step, allowing you to use the same MS Teams integration across several teams of your organization. This way, you can manage one incident across multiple teams, all from your MS Teams channels.
  3. Click Create & Connect to connect All Quiet and MS Teams.

​
Send Incidents From All Quiet to MS Teams

To send All Quiet incidents to your MS Teams channels, you must complete the following additional configuration steps.
  1. Open the Edit tab of your Microsoft Teams integration on All Quiet
  2. Select your preferred Forwarding settings:
    1. Default: Always will automatically forward all incidents to your Microsoft Teams Channels, unless excluded by advanced routing rules.
    2. Alternative: Always After Forwarding - Messages will only be sent if users manually forward specific incidents or if you set up advanced routing rules for your Microsoft Teams integration that automatically forward incidents in specific scenarios. After the initial Forwarding, all updates will automatically be sent.
      You can change your selection anytime.
  3. Optionally enable Anonymize Outbound Logs (disabled by default). When enabled, activity log entries for this integration are stored without descriptions, external identifiers, error details, and payload data. Only operational metadata such as operation, outcome, and HTTP status is kept.
Confirm by clicking Save. Next, open the Microsoft Teams Settings tab. Here, you can configure additional information.
  1. In the Settings subsection, you can see the connected MS Team.
    • Read Only: You can change your integration settings to “Read Only”. In this mode, we will not send any action buttons to your Microsoft Teams Channels, meaning users cannot interact with the messages. This is ideal if you want to use the integration for internal stakeholder management.
    • Tag On-Call Members: You can tag the on-call members in the related Microsoft Teams channels when an an incident is assigned to them.
  2. Configure where All Quiet sends incident updates in the Fixed Channels and
  3. Dynamic Channels sections.
Only for Pro and Enterprise plan - Manage your Team Connections: The root team is pre-selected, and you can add the integration to further teams within the root team’s organization. Team Administrators can add / remove those teams they are an Administrator in, Organization Administrators & Organization Owners can manage the connections to all teams of the organization.

​
Fixed Channels

Select the MS Teams channels where you want to send All Quiet incidents to. You can choose from every channel in the connected MS Team(s).
Regardless of its name in MS Teams, your first connected MS Teams channel will always be referred to as General in All Quiet. Unfortunately, this is beyond our control.

​
Dynamic Channels

Instead of—or in addition to—Fixed Channels, you can create a dedicated MS Teams channel per incident. When an incident matches your configured severities, All Quiet creates a new channel, posts all incident updates there, and manages the channel lifecycle for you.
  1. Enable Dedicated channels per incident.
  2. Set a channel name prefix. Channel names are generated from the prefix, date, title slug, and short incident ID, then sanitized to fit Microsoft Teams’ naming limits.
  3. Select the severities that should trigger a dedicated channel.
  4. Disable on-call invite: You can disable the automatic invitation of the on-call members to the dedicated channel when an incident is assigned to them.
    Microsoft Teams cannot automatically add the dedicated channel to the overview channels. We heavily recommend activating the tag on-call members option and / or leave the on-call invite enabled to increase the visibility of the dedicated channel for the on-call members.
  5. Configure archiving:
    • Auto-Archive on resolve or archive — archive the channel when the incident is resolved or archived in All Quiet.
    • Optionally set an archive delay to wait before archiving (useful if you want a short grace period after resolution).
Save your settings.
If an incident is reopened, All Quiet unarchives the dedicated channel so updates continue there.
Here’s an example of how an All Quiet incident will appear in MS Teams. You can manage your entire incident from within MS Teams, including your status pages, and forward the incident to other integrations for ticketing or post-mortems.
If incident grouping is enabled, All Quiet will only include the grouping attributes in the Microsoft Teams messages we send (the same fields used to group events into an incident). Learn more in our Inbound Integrations docs.
For compliance reasons, only Users with rights in the All Quiet team(s) connected to the incident can interact with the Message.
You can now use MS Teams as an outbound integration to send All Quiet incidents to your team channels. Below, you’ll find instructions on how to use MS Teams to create new incidents as well.

​
Create New All Quiet Incidents Directly From MS Teams

To create a new incident in All Quiet from your MS Teams channel, start a new post in a channel you have added to your Fixed Microsoft Teams channels and type @All Quiet. You can use the Tab key for autocomplete. Next, you will receive command suggestions.
  1. Select the command incident by either clicking on it or typing it.
  2. Click Post to create the incident form.
Fill out the form in order to create an incident.
  1. You will see the command that triggered the form.
  2. Enter a Title for the incident.
  3. Enter a Description.
  4. Select the Severity.
  5. Select the All Quiet Team where you want to create the incident. If the right team is not listed, you will need to add it first. See below for more.
    For compliance reasons, Users will only be able to select from the All Quiet teams they have rights in & that are connected to Microsoft Teams via the integration.
  6. Click Create Incident to submit.
This is how the new incident will appear in MS Teams… …and this is how it will look in the incident overview on the All Quiet web app.

​
Connect Additional All Quiet Teams With MS Teams

With the following command, you will eventually create an additional MS Teams integration for each team in All Quiet. We recommend Pro and Enterprise users to add the integration to further All Quiet teams via the integration’s setup page in All Quiet in case they want to share incidents across several teams.
To connect another All Quiet team with MS Teams, simply go to your teams channel and enter @All Quiet followed the command connect. This will trigger another Connect message. By clicking Connect more All Quiet teams, you will be redirected to your All Quiet web app with a drafted MS Teams integration. Simply follow the steps from above and select the additional All Quiet team wish to connect.

​
Disconnect All Quiet and MS Teams

To disconnect your Microsoft Team from All Quiet, enter the command @All Quiet disconnect and confirm by clicking on Disconnect Now in the interactive message the bot is sending you afterwards.

​
Troubleshooting

Team Administrators, Organization Administrators, and Organization Owners can troubleshoot this integration using the History tab (Outbound History) on the integration details page. See Outbound History for what is logged, who can access it, and how to read outcomes. For broader checks when outbound tools do not fire, see Outbound integrations — Troubleshooting and advanced routing.

​
On-call tagging or dedicated channels not working

If you connected Microsoft Teams before August 10, 2026, Tag On-Call Members and Dedicated channels per incident may not work—the All Quiet app is likely missing updated Microsoft Graph permissions in your tenant. These features (on-call tagging, notifying on-call members about dedicated channels, and auto-archiving dedicated channels) were added on that date. Integrations connected on or after that date receive the permissions during setup. These permissions apply only to those optional features—not to basic incident forwarding. Ask a Microsoft 365 admin to grant admin consent for these application permissions on the All Quiet app: How to grant them: Have a Microsoft 365 admin open the All Quiet app in Microsoft Teams admin or Entra ID (Azure AD) → Enterprise applications and approve the permissions above, or remove and re-add the All Quiet bot/app to your team so the updated consent prompt appears—then admin-consent the permissions.