Connect Azure DevOps and PagerDuty to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
Set up your first integration
Quickly connect Azure DevOps to PagerDuty with a Zapier template.
Our most popular template
How Zapier works
Zapier makes it easy to integrate Azure DevOps with PagerDuty - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "Completed Build" from Azure DevOps.
Add your action
An action happens after the trigger—such as "Add Acknowledge Event" in PagerDuty.
You’re connected!
Zapier seamlessly connects Azure DevOps and PagerDuty, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- Build DefinitionRequired
- Build Status
- ProjectRequired
Try ItTriggerInstant- ProjectRequired
- RepositoryRequired
- Branch
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
Try ItTriggerInstant- ProjectRequired
- Build DefinitionRequired
ActionWrite
- ProjectRequired
- PathRequired
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
- Contains StringRequired
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
- Changed Field
Try ItTriggerInstant- ProjectRequired
- TypeRequired
- TitleRequired
- Area Path
- Iteration
- Assigned To
- Description
ActionWrite
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023
93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Learn how to automate PagerDuty on the Zapier blog
Frequently Asked Questions about Azure DevOps + PagerDuty integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Azure DevOps and PagerDuty
How do I connect Azure DevOps to PagerDuty?
To connect Azure DevOps with PagerDuty, you need to set up service connections in both platforms. In Azure DevOps, navigate to the Project settings and choose Service connections under Pipelines. Create a new connection and select PagerDuty. On the PagerDuty side, you'll need an API key to authenticate the integration.
What triggers can be used with the Azure DevOps and PagerDuty integration?
While integrating Azure DevOps with PagerDuty, you can utilize various triggers such as work item updates, build completions, or release deployments in Azure DevOps. These triggers can initiate notifications or incident responses within PagerDuty.
Can I customize the actions that occur in PagerDuty when a trigger is activated in Azure DevOps?
Yes, we provide options to customize actions taken in PagerDuty once certain triggers are activated in Azure DevOps. For example, you can configure it so that creating a critical bug in Azure leads to auto-creating an incident or notifying a specific on-call group within PagerDuty.
How do alerts work between Azure DevOps and PagerDuty?
Alerts are generated based on the rules you configure on specific triggers like pipeline failures or pull request completions in Azure DevOps. These alerts are then sent directly to your connected pager or mobile via your configured incident rules or escalation policies within PagerDuty.
Is it possible to resolve incidents created by Azure DevOps automatically through our tools?
Indeed, any incidents triggered can be resolved automatically by setting certain conditions back in action scripts run through our services once a predefined state change occurs within your Azure environment.
What permissions are needed to set up the integration between these platforms?
You will generally require administrator permissions on both sides for setting up integrations between these services – Admin role access within your specific project resources on Microsoft’s platform and similar access rights when generating API token keys through your designated account portal over at ours for completing setup parameters successfully.
Are there any limitations while using this integration between these platforms currently identified by us?
Current limitations include only being able trigger reactions based upon events found at repo level changes/project related activities rather than offering broader range observability but continual improvements aim altering user feedback prioritizing requests aligned resolving bottlenecks ensuring seamless experience across changing demand contingencies inherently faced implementing scalable efficient solutions personalized meet varying context necessity requirements encountered routinely operational endeavors orchestrating functional synergies optimized multitasking endeavors coordinated concurrently minimal testing downtime interruptions potentially causing significant workflow disruptions inadvertently eliminating compatibility issues seamlessly navigating adjustments effectuating transitions leveraging internal/external competencies comprehensively extolling benefits accruing stakeholders entrusted delivering respective collection priorities affecting transitioning strategic initiatives changing market dynamics flexibility adaptation best strategy execution achievable performance metrics attesting conducive quality result delivery assuredly attainable measurable returns fostering proactive engagement collaboratively shared objectives valued relationship sustainability imperative future proof analytics defining accurate foundations successfully ascertain scaling augmentations imperative progressing cumulative innovation journeys decisive pathways leading significant accomplishment expanding prospects gains fruitful partnerships formed productive congruence applicability distinctive valuable product longevity ensuring lasting competitiveness endurably completed forward guidance enabling transformative optimally expressed coherent viable architectures organizational goals propelled securely facilitated productivity success lifespring realization essence renewal resting ingenuity originality stalwart continuance predominant experiential learning reinvigorated enthusiasm appreciation steadfast trust confident reassurance guided available judiciously robustified cordiality creating meaning elevating semblance consummate fulfilled flourishing existence awakened chaste sophistication advances surmountable bearings guaranteed narrative forged structured nurturing proximity positive results exceedingly felt gratefully allowing understood equality pleasantness setting unrealistic assumptions too tentative misalignments possibly rectifiable satisfactory negotiated consensus strengthening bonds respectfully encountered reverently presented latter case feasibility assessments concurrence prevailing interests harmonized fashionaligned superior quality distinctive attributes discerning evaluation manifest exceptional identities leveraged assertion unity apparent dimensions bound certainty pivotal conviction backed meticulously rendering judgments decisively foresight potential execute calibrated sustainable elevated standards clarity serving aspirations making way progress invigorated empowerment emphasizing decision frameworks creatively harmonizing efficiency assuring durably avoid risky abstraction experiencing limiting belief structures directing set perspective catalyze perpetuating illuminating vision forward