---
updatedAt: 2026-10-15T13:37:15.000Z
agentTools:
  siteIndex: https://support.pagerduty.com/llms.txt
  projectIndex: https://support.pagerduty.com/main/llms.txt
---

# Microsoft Teams Permission Changelog

# 2026-10-15

## Change

* Added as required, application permission for Post Incident Review: `Chat.Read.All`
* No new delegated permission is required. Post Incident Review uses the existing required delegated permission: `Chat.ReadWrite`

## Purpose

We are adding a new application permission, `Chat.Read.All`, which you need to use Post Incident Review in Microsoft Teams. If you use delegated permissions, Post Incident Review uses the existing `Chat.ReadWrite` permission instead.

Post Incident Review is not live yet and will be available soon for all Microsoft Teams customers. Approving or declining this permission does not change anything during this upgrade. You only need to approve one of these permissions after Post Incident Review is live, and only if you want to use it.

# 2026-02-05

## Change

* Updated the naming convention of this required application permission: `TeamsAppInstallation.ReadWriteSelfForChat.All`
* Updated as required, application permission for PagerDuty Advance: `ChatMessage.Read.All`
* Updated as optional application permissions: `User.Read.All`, `User.ReadBasic.All`
* Updated as required delegated permissions: `Chat.ReadWrite`,  `TeamsAppInstallation.ReadWriteForChat`
* Updated as required, delegated permission for PagerDuty Advance: `ChatMessage.Read`
* Removed this required delegated permission: `offline_access`

## Purpose

These permissions were modified to support the new **hybrid permission model** (described in the main integration guide), which allows different Teams features to share different permission types simultaneously.

# 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](https://support.pagerduty.com/main/docs/pagerduty-advance#pagerduty-advance-assistant). 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.