> For the complete documentation index, see [llms.txt](https://docs.pushpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pushpulse.com/integrations/microsoft-teams-integration.md).
# Microsoft Teams Integration
### How It Works
When an alert is triggered in PushPulse, a message is posted to any Teams channels you've configured for delivery. As the incident evolves, status updates, notes, and all clears are automatically threaded under the original alert message — keeping communication organized and easy to follow.
Form submissions can also be configured to notify Teams channels, giving your team real-time visibility into incoming reports.
***
### Setup Overview
Getting Teams connected involves two steps:
1. **Authorize the PushPulse app** — connect your Microsoft Teams organization via OAuth
2. **Install the PushPulse bot in Teams** — an admin installs the app package and adds it to your desired teams
3. **Configure delivery** — attach channels to alert templates, individual alerts, or forms
***
### Step 1: Authorize the Teams App
In PushPulse, navigate to **Manage → Integrations → Microsoft Teams** and click **Connect**. You'll be prompted to sign in with your Microsoft account and grant PushPulse permission to connect to your organization.
You must have sufficient Microsoft 365 permissions to authorize third-party app integrations, or work with an admin who does.
***
### Step 2: Install the PushPulse Bot in Teams
This step requires a **Microsoft Teams admin**. The PushPulse bot must be uploaded to your organization's app catalog before it can be added to any team or channel.
1. Open **Microsoft Teams** and go to **Apps**
2. Click **Manage your apps**
3. Click **Upload an app**
4. Select **Upload an app to your org's app catalog**
5. Upload the PushPulse app package provided by your PushPulse administrator
6. Once uploaded, add **PushPulse** to your desired teams
> **Note:** Uploading to the org's app catalog makes the bot available across your organization. Individual team owners can then add it to their teams, or an admin can deploy it broadly.
After installation, you can send a **test message** from the integration page in PushPulse to confirm delivery is working before configuring live alerts.
***
### Step 3: Configure Delivery
#### Notification Templates
To deliver alerts to Teams at the template level — so every alert created from that template notifies the same channel(s) automatically:
1. Go to **Alert Templates** and open or create a template
2. In the **Delivery** section, select one or more Teams channels
3. Save the template
Alerts created from this template will automatically notify the selected channels when triggered.
#### Individual Notifications
You can also select Teams channels when composing a new alert:
1. Start composing an alert
2. In the **Delivery** section, select one or more Teams channels
3. Send the alert
This is useful for one-off alerts where broader or different notification is needed beyond a template's default configuration.
#### Forms
To send a Teams notification when a form is submitted:
1. Go to **Forms** and open or create a form
2. In the form settings, locate the **Send submission notification** section
3. Select one or more Teams channels to notify on submission
4. Save the form
The notification will be sent to the configured channel(s) each time the form is submitted.
***
### What Gets Sent to Teams
| Event | Behavior |
| ---------------- | ----------------------------------------------- |
| Alert triggered | New message posted to configured channel(s) |
| Status update | Threaded reply under the original alert message |
| Note added | Threaded reply under the original alert message |
| All clear issued | Threaded reply under the original alert message |
| Form submitted | New message posted to configured channel(s) |
***
### Troubleshooting
**I don't see any channels available to select.** Confirm the PushPulse bot has been installed and added to your teams by a Microsoft Teams admin. Channels only become available for delivery after the bot is present in the team.
**The app upload option isn't available.** Your Microsoft Teams organization may restrict custom app uploads. A Teams admin will need to enable this in the Teams admin center under **Teams apps → Setup policies**, or perform the upload on your behalf.
**Test message didn't arrive.** Verify that the PushPulse bot was successfully added to the target team, not just uploaded to the catalog. Open the team in Teams and confirm PushPulse appears under **Apps** for that team.
**Alerts aren't being delivered to Teams.** Verify that (1) the Teams integration is authorized in PushPulse, (2) the PushPulse bot is installed in the target team, and (3) the channel is selected in the alert template, individual alert, or form configuration.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.pushpulse.com/integrations/microsoft-teams-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.