From 717d7749a6f589f4471904f380df4af02303d6a8 Mon Sep 17 00:00:00 2001 From: Jed Laundry Date: Thu, 27 Nov 2025 15:48:58 +1300 Subject: [PATCH 1/2] Fix Selected Permissions overview --- concepts/permissions-selected-overview.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/concepts/permissions-selected-overview.md b/concepts/permissions-selected-overview.md index a75703027a9..9c346a831f7 100644 --- a/concepts/permissions-selected-overview.md +++ b/concepts/permissions-selected-overview.md @@ -34,6 +34,9 @@ When an administrator consents to Selected scopes for an application, they're de Selected scopes require a series of steps to work, which provides several means of control for administrators. The following example uses the `Lists.SelectedOperations.Selected` scope, but the steps apply to all *.Selected scopes. +> [!IMPORTANT] +> The Selected scopes APIs, such as `/sites/{siteid}/lists/{listid}/permissions` are currently only available in the `beta` Graph API. + 1. The application must be consented in Entra ID to have either the application or delegated `Lists.SelectedOperations.Selected` scope. 2. The application must be granted permissions to a list via a call to `POST /sites/{siteid}/lists/{listid}/permissions` with a specific role. 3. The application must acquire a valid token that contains the `Lists.SelectedOperations.Selected` scope for calls to the permissioned list. @@ -74,14 +77,15 @@ The following table lists the four roles that can be assigned to an application } --> ```http -POST https://graph.microsoft.com/v1.0/sites/{siteId}/permissions +POST https://graph.microsoft.com/beta/sites/{siteId}/permissions Content-Type: application/json { "roles": ["write"], "grantedTo": { "application": { - "id": "89ea5c94-7736-4e25-95ad-3fa95f62b66e" + "id": "89ea5c94-7736-4e25-95ad-3fa95f62b66e", + "displayName": "Contoso Time Manager App" } } } From 2dd3b34b00311625638aca6238c93ffc4807cfd7 Mon Sep 17 00:00:00 2001 From: Laura Graham Date: Fri, 1 May 2026 14:34:34 -0700 Subject: [PATCH 2/2] Update permissions-selected-overview.md --- concepts/permissions-selected-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/concepts/permissions-selected-overview.md b/concepts/permissions-selected-overview.md index 9c346a831f7..2a26f0e1dff 100644 --- a/concepts/permissions-selected-overview.md +++ b/concepts/permissions-selected-overview.md @@ -35,7 +35,7 @@ When an administrator consents to Selected scopes for an application, they're de Selected scopes require a series of steps to work, which provides several means of control for administrators. The following example uses the `Lists.SelectedOperations.Selected` scope, but the steps apply to all *.Selected scopes. > [!IMPORTANT] -> The Selected scopes APIs, such as `/sites/{siteid}/lists/{listid}/permissions` are currently only available in the `beta` Graph API. +> The selected scopes APIs, such as `/sites/{siteid}/lists/{listid}/permissions`, are currently only available in the beta endpoint. 1. The application must be consented in Entra ID to have either the application or delegated `Lists.SelectedOperations.Selected` scope. 2. The application must be granted permissions to a list via a call to `POST /sites/{siteid}/lists/{listid}/permissions` with a specific role.