• PagerDuty
    /
  • Blog
    /
  • AI
    /
  • Announcing a forthcoming integration with PagerDuty + Azure AI SRE Agent for faster incident response

Blog

Announcing a forthcoming integration with PagerDuty + Azure AI SRE Agent for faster incident response

by Sean Noble November 24, 2025 | 4 min read

The energy at Microsoft Ignite this year was electric. AI was everywhere, and the possibilities are limitless. As developers and operations teams explore what AI can do, one thing became clear: the future isn’t about switching between tools. It’s about intelligent agents working together to help humans solve problems faster.

At PagerDuty, we’re building on that excitement. We’re thrilled to announce forthcoming Early Access for our Azure AI SRE Agent integration, coming December 2025. This collaboration will transform how teams respond to incidents in Azure environments. It will be a fundamental shift toward context-rich incident response that keeps your teams focused on resolving problems fast.

Azure AI SRE Agent integration

When paired with PagerDuty, the Azure SRE Agent will be able to ingest newly triggered PagerDuty incidents, consult with PagerDuty Advance for historical runbooks and past patterns, and correlate them with timely Azure diagnostics like App Service metrics, VM scale set health, or Storage latency, without context-switching. It will then synthesize a rapid RCA using Azure telemetry (e.g., memory saturation tied to a specific deployment), propose a safe, reversible mitigation (such as an App Service restart or targeted scale-out), and post all actions and verification back to the PagerDuty timeline.

Beyond the immediate fix, the Azure SRE Agent integration also drives durable outcomes inside the developer’s workflow. It will be able to open a GitHub issue pre-filled with RCA details, Azure metric snapshots, and incident links, assign the right service owner based on PagerDuty schedules, and kick off a Copilot-assisted PR for a permanent patch. Throughout, it will keep the incident updated in PagerDuty with status, notes, and follow-ups so responders and stakeholders have a source of truth from first alert through long-term remediation.

Here’s an example of how this could work during an incident:

  1. Detection and triage: A performance issue is detected in Azure Monitor and an event is sent to PagerDuty. This triggers an alert that starts an investigation by the PagerDuty SRE Agent.
  2. Context and collaboration: The Azure SRE Agent and the PagerDuty SRE Agent collaborate to enrich analysis with historical incident data, ownership context, correlated change events, and prior remediation patterns. 
  3. Runbook guidance: PagerDuty returns a recommended runbook synthesized from similar past incidents. For example: “Restart the affected App Service and verify performance stability.” 
  4. Coordinated mitigation: The approved mitigation runs through Azure and, together, the agents close the loop from signal to resolution in a unified, intelligent workflow.  
  5. Learning and improvement: A corresponding GitHub issue is created or updated to capture the RCA and link to the PagerDuty incident, embedding the learning directly into the development lifecycle.

And PagerDuty plans on building out more functionality over time that can be leveraged by the Azure AI SRE agent. Keep an eye on our release notes for regular MCP enhancements.

Maximizing Your Microsoft Investment

This Azure AI SRE Agent integration is part of PagerDuty’s deeper commitment to the Microsoft ecosystem. In parallel, we’re expanding our AI platform investments with the forthcoming early access of PagerDuty Advance API and MCP support. This will allow integration partners such as Microsoft Azure to activate PagerDuty Advance agents that deliver runbook intelligence, incident context, and automation to any MCP-compatible surfaces. 

Beyond this, PagerDuty is also investing in our Microsoft Teams experience with faster configuration, improved usability, and AI-first workflows in chat, so developers can work from wherever they want while resolving incidents fast.

And for development teams using GitHub, we have even more good news. We’re excited to collaborate with GitHub on a high-impact use case for custom agents: PagerDuty created an Incident Responder custom agent, now available in GitHub’s AI partner directory!

Respond to incidents directly in GitHub Copilot, no more context-switching between tools during critical moments. The agent specializes in incident response by automatically correlating incident data with recent commits and deployments to identify root causes faster, then generating fix PRs with incident linking and on-call team tagging, all within your development workflow.

For joint PagerDuty and GitHub Copilot users, the Incident Responder custom agent is now generally available. Watch this demo to learn more or visit the Awesome Copilot Repo

Together, these integrations will create a more efficient response process within your Microsoft tools: Azure AI SRE Agent handles immediate triage and mitigation, GitHub Copilot assists with permanent fixes, and Teams keeps everyone informed, all while PagerDuty Advance provides the intelligence that makes it possible.

Early Access planned for mid-December 2025 for joint PagerDuty Advance and Azure AI customers.