PagerDuty announced a new integration with Microsoft Teams, a workspace collaboration application that is part of Microsoft Office 365.
PagerDuty with Microsoft Teams helps teams find out about incidents faster, and gives them background on the incident, directly in Teams so they don’t lose time switching between services. Cutting the time to respond to and resolve the incident reduces the risk of it impacting customers, with the associated risks of lost revenue and brand damage. For management-level users, the Teams integration provides a full view of the incidents their team is working on. This level of communication and visibility is important for ensuring teams across an organization, including Developer, IT, Customer Services, Sales and more can collaborate effectively and stay up to date.
“As organizations work to meet increased digital demand, clear communication and strong collaboration are more important than ever,” said Jonathan Rende, SVP of Product at PagerDuty. “PagerDuty’s new Microsoft Teams integration helps reduce the time it takes to resolve incidents and continuously improve.”
PagerDuty surfaces critical incidents in Teams, which in turn allows workers to communicate and work together during the incident resolution process. By allowing a user to view critical incident details from within Teams, the integration creates a third user interface to PagerDuty, in addition to mobile and desktop. PagerDuty users can perform key incident actions within Teams. This includes acknowledging and resolving incidents, adding notes, and even triggering new incidents directly within Teams. Users can also connect services directly to Teams channels, keeping everyone in sync and connected.
“Microsoft Teams empowers the DevOps community with secure collaboration and meeting experiences,” said Farhaz Karmali, Lead Product Manager, Teams at Microsoft. “With PagerDuty’s integration for Microsoft Teams, DevOps practitioners can drive real-time operations all within the Teams platform.”
Key benefits of the PagerDuty and Teams integration include:
- Work where you are—View critical incident details without having to leave Teams. Responders can now acknowledge, resolve and add notes to PagerDuty incidents all from within Microsoft Teams. Users can now also trigger a new PagerDuty incident from within Teams.
- Drive modern ChatOps—Break down silos by driving real-time ChatOps with PagerDuty for Teams. Connect disparate teams across NOC, DevOps, Customer Service, Engineering and more to a common incident management framework.
- Align services and permissions—Now users can synchronize their Teams and PagerDuty user and account permissions to ensure secure communication and safe information sharing. Connect PagerDuty services to Teams channels via Add-Ons Page and ‘connect’ App command.
- Automated activity capture for post mortems from Teams – All incident response activities in Teams are automatically captured for post-mortems to help team members continuously improve and learn.
- Connect to Microsoft—In Teams, users can access both PagerDuty incident data and technical documentation from Microsoft tools. Users can access every incident response documentation available in real-time.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.