Microsoft Teams Integration Issue

Severity: MajorCategory: Change ProcessService: PagerDuty
This summary is created by Generative AI and may differ from the actual content.
Overview
During a period beginning at 21:44 UTC on Monday, January 9th, and ending at 13:16 UTC on Tuesday, January 10th, PagerDuty experienced an incident that prevented customers in the EU Service Region from authorizing new Microsoft Teams and Slack integrations. Integrations that were authorized prior to this incident were not affected, as well as new authorizations from other integrations such as Jira, Live Call Routing, Zendesk, and ServiceNow.
Impact
The incident affected customers in the EU Service Region by preventing them from authorizing new Microsoft Teams and Slack integrations. However, integrations authorized prior to the incident and other integrations like Jira, Live Call Routing, Zendesk, and ServiceNow were not affected.
Trigger
A code change to build redirect URLs intended for non-production environments inadvertently affected new authorizations for Microsoft Teams and Slack integrations in the EU production environment.
Detection
The issue was detected after receiving customer reports of not being able to authorize the Microsoft Teams and Slack integration.
Resolution
The code change was identified and reverted by 12:50 UTC on Tuesday, January 10th, and the fix was completed by 13:16 UTC the same day. Both Microsoft Teams and Slack authentications have been operating normally since the fix.
Root Cause
The root cause was a code change that inadvertently affected the production environment, specifically impacting the authorization of new Microsoft Teams and Slack integrations in the EU region.
;