2024-11-07

Change

Added the following application level permission: User.ReadBasic.All.

Purpose

Previously PagerDuty added the application permission User.Read.All. We are in the process of replacing this permission with User.ReadBasic.All, which decreases the scope of what user information we have access to.

User.Read.All is no longer being used, and may be revoked. We will remove this permission from the application completely in a future update.

2024-10-23

Change

Added the following application level permission: ChatMessage.Read.All.

Purpose

This is a new optional permission to support PagerDuty Advance. If you are opted-in to use PagerDuty Advance, our application will use this permission to fetch chat messages from conversations for Advance features such as generating incident status updates, or post-incident summaries.

2024-09-01

Change

Added the following application level permissions: Chat.Create, ChatMember.ReadWrite.All, OnlineMeetings.ReadWrite.All, Organization.Read.All, TeamsAppInstallation.ReadWriteSelfForChat, User.Read.All.

Purpose

These permissions support our transition away from delegated permission to an application-level permissions model.

Additional details, which are also being communicated on the main integration guide:

Previously, PagerDuty would automate incident tasks in Teams by requesting user-level (AKA delegated) permissions from individual users.

We are now transitioning to use application-level permissions, granted by your Microsoft Teams admin.

These new application permissions are all "Least Privileged Permissions" - we are only requesting the minimum permissions necessary to support the features of the PagerDuty application.

In order to ensure no interruption to service, we are currently requesting both user-level and application-level permissions, but user-level permissions will be removed when this transition is complete.