After completing the initial configuration, you can manage PagerDuty incidents in Microsoft Teams.
The PagerDuty application offers users a variety of app commands. In any of your team channels, you may enter
@PagerDuty [COMMAND], replacing
[COMMAND] with any of the following:
help: View the list of available commands.
open: Open PagerDuty in a new browser window.
linkUser: Link your PagerDuty and Teams user accounts.
unlinkUser: Unlink your PagerDuty and Teams user accounts.
trigger: In a channel, complete the form to create a new incident.
PagerDuty Admins or Manager Role Required
connect [SERVICE-URL]: In a channel, use the PagerDuty service page URL to connect a PagerDuty service to a channel.
PagerDuty Admin Role Required
authorize [KEY]: In a private PagerDuty bot message, use the unique key provided to authorize PagerDuty to connect to a team.
configure: Open PagerDuty’s app configuration page in your browser.
To perform an incident action in Microsoft Teams, a user’s PagerDuty and Microsoft Teams account must be linked. If accounts are not linked, they will receive a private bot message with a personal link to complete the process.
When an incident notification posts in a Microsoft Teams channel, channel members can perform the following actions:
- Add Note
- Create Meeting
- New Status Update
- Select More Actions to access:
All incident actions performed in Microsoft Teams will update the incident in PagerDuty.
Users can create Microsoft Teams Meetings that will be assigned as an incident-specific Conference Bridge in PagerDuty incidents. Users may also add notes from the Microsoft Teams Meeting chat, which will sync with the PagerDuty incident.
To create a Microsoft Teams Meeting Conference Bridge:
- After an incident notification posts in a Microsoft Teams channel, click Create Meeting from the incident actions:
- You will see the confirmation message
All current responders with linked PagerDuty accounts will be added automatically, click Confirm.
- Note: If prompted, click the link to authorize the connection with Microsoft Graph.
- You will now see the meeting link populated in the incident notification, and on the PagerDuty incident as the Conference Bridge and as a Note:
- To join a Microsoft Teams Meeting Conference Bridge, click Join Meeting on the incident notification:
- All comments made in the meeting chat (found by clicking the Show Conversation at the top of the screen) will sync with the Chat in the Microsoft Teams console, so you can request help from team members not currently in the Meeting.
Users can create Microsoft Teams meetings that will be assigned directly from a PagerDuty incident’s details page when the following conditions are met:
- The incident does not already have a conference bridge
- The account has not configured the Zoom integration
After connecting Microsoft Teams and PagerDuty, to create a Microsoft Teams Meeting on an incident’s details page:
- In the PagerDuty web app, navigate to an incident’s details page.
- Click Create MS Teams Meeting.
After clicking Create MS Teams Meeting, the Conference URL will update with a link to join Microsoft Teams meeting. All incident responders will be automatically added to the meeting, if they have configured the Microsoft Teams add-on. Otherwise, the responders that don’t have the add-on enabled will receive an email alerting them of the meeting creation.
The incident timeline will also show an entry indicating that the meeting was successfully created.
View customer service application impact during an incident in Microsoft Teams. Services with Salesforce or Zendesk integrations will list the number of cases related to the current incident, with links to individual cases.
To view individual cases:
- To the right of the application you would like to view, click
- You will see a list of related cases in the modal that appears. Click a case number to navigate to the integrated application and view the case.
Our Incident Workflows feature allows users to run a workflow to create a Microsoft Teams dedicated chat or conference bridge. Please read our Incident Workflows article for more information.
Updated 4 days ago