Quick Answer: Yes, PagerDuty has a native integration with Microsoft Teams that routes incident alerts directly to your Teams channels, enabling your team to respond faster without switching tools.
Overview
PagerDuty and Microsoft Teams work together to bring critical incident alerts into the communication platform your team already uses daily. When an incident is triggered in PagerDuty, notifications land in a designated Teams channel in real time, complete with severity, service details, and action buttons. This eliminates the friction of checking multiple applications and keeps incident response workflows in one place.
For IT operations teams managing infrastructure, cloud services, or SaaS platforms, this integration reduces mean time to response (MTTR) by ensuring alerts reach the right people immediately, without relying on email or separate dashboards.
How the Integration Works
- Alert Routing: When a PagerDuty incident is created, the native connector automatically sends a formatted message to a specified Microsoft Teams channel. The message includes incident title, severity level, assigned responder, and service name.
- Real-Time Notifications: Alerts arrive in Teams within seconds of being triggered in PagerDuty, ensuring your team is notified immediately without delay.
- Interactive Actions: Team members can acknowledge, resolve, or escalate incidents directly from the Teams message using action buttons, without navigating back to PagerDuty.
- Channel-Based Organization: You can route different incident types or services to different Teams channels, keeping alerts organized by team responsibility or service criticality.
- Bi-Directional Context: The Teams message includes a link back to the full incident details in PagerDuty, allowing responders to jump to the incident timeline, logs, and runbooks when needed.
Key Features & Capabilities
- Automatic Alert Delivery to Teams Channels: All PagerDuty incidents are pushed to Teams without manual intervention, ensuring no alert goes unnoticed.
- Incident Acknowledgment from Teams: Responders can acknowledge incidents directly in Teams, updating PagerDuty’s incident status in real time and notifying other on-call team members.
- Severity-Based Formatting: Alerts are color-coded and formatted by severity level (critical, high, medium, low), making it easy to prioritize at a glance.
- Service and Team Routing: Configure which PagerDuty services or escalation policies route to which Teams channels, ensuring alerts reach the right team without noise.
- Incident Resolution Notifications: When an incident is resolved in PagerDuty, a notification is posted to Teams, keeping the team informed of resolution status.
- Deep Linking to Incident Details: Each Teams message includes a direct link to the full incident record in PagerDuty, enabling quick access to timeline, notes, and assigned responders.
Setup Difficulty
Easy (5–10 minutes, no code required). The integration is configured entirely through the PagerDuty web interface. You’ll need to authenticate PagerDuty with your Microsoft Teams workspace, select a channel to receive alerts, and optionally configure which services or escalation policies trigger notifications. No API calls, webhooks, or developer involvement needed.
Setup Steps
- Open PagerDuty Integration Settings: Log in to PagerDuty, navigate to Integrations, and search for Microsoft Teams.
- Authorize Teams: Click the integration and follow the OAuth flow to grant PagerDuty permission to post to your Teams workspace.
- Select Target Channel: Choose which Teams channel will receive incident alerts (or create a dedicated #incidents or #alerts channel).
- Configure Services (Optional): If desired, map specific PagerDuty services or escalation policies to different Teams channels for better organization.
- Test the Integration: Trigger a test incident in PagerDuty to verify the message appears in Teams with correct formatting.
- Enable Action Buttons (Optional): Confirm that team members can acknowledge or resolve incidents from the Teams message.
Alternatives
If the native PagerDuty–Teams integration doesn’t fully meet your needs, consider these options:
- Zapier or Make (formerly Integromat): Use workflow automation platforms to create custom logic between PagerDuty and Teams. For example, route only critical incidents to Teams, or post additional context from your CMDB or monitoring tool. Requires a paid Zapier/Make subscription but offers more flexibility.
- Microsoft Power Automate: Build custom cloud workflows that trigger on PagerDuty webhooks and post rich, templated messages to Teams. Useful if you need to enrich alerts with data from other Microsoft 365 services (SharePoint, Dynamics, etc.).
- Custom Webhook Integration: If you have development resources, configure a PagerDuty webhook to send raw incident data to a custom API or serverless function, which then formats and posts to Teams. Offers maximum control but requires ongoing maintenance.
Frequently Asked Questions
Can I acknowledge or resolve a PagerDuty incident directly from Teams?
Yes. The native integration includes action buttons in the Teams message that allow you to acknowledge, resolve, or escalate the incident without leaving Teams. These actions immediately update the incident status in PagerDuty and notify other responders.
Can I route different services to different Teams channels?
Yes. During setup, you can configure multiple integrations, each pointing to a different Teams channel. This allows you to route infrastructure alerts to #ops, application alerts to #dev, and database alerts to #dba, for example. Each service or escalation policy can have its own channel destination.
What information is included in the Teams message?
The Teams message includes the incident title, severity level, assigned responder, service name, incident number, and a timestamp. It also includes action buttons (acknowledge, resolve, escalate) and a link to the full incident details in PagerDuty.
Does the integration work with Microsoft Teams on desktop, web, and mobile?
Yes. Alerts appear in Teams across all platforms (desktop app, web browser, and mobile apps). Action buttons are available on all platforms, though the mobile experience may vary slightly depending on the Teams client version.
What happens if a responder is offline when an alert arrives in Teams?
The alert remains in the Teams channel history and will be visible when the responder returns online. Additionally, PagerDuty’s own escalation policies (phone calls, SMS, etc.) continue to work independently, ensuring critical incidents reach on-call staff even if they miss the Teams notification.