Skip to content

Commit 4b243d5

Browse files
authored
update
1 parent 5ed4890 commit 4b243d5

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

support/entra/entra-id/users-groups-entra-apis/403-error-when-calling-microsoft-graph-security-api.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,18 @@
11
---
2-
title: HTTP 403 authorization error when calling Microsoft Graph Security API
3-
description: Provides a soltion to an HTTP 403 error that occurs when you call Microsoft Graph Security API.
2+
title: HTTP 403 authorization error when calling the Microsoft Graph Security API
3+
description: Provides soltions to an HTTP 403 error that occurs when you call the Microsoft Graph Security API.
44
ms.date: 05/06/2025
55
ms.service: entra-id
66
ms.custom: sap:Getting access denied errors (Authorization)
77
ms.reviewer: bachoang, v-weizhu
88
---
9-
# HTTP 403 authorization error when calling Microsoft Graph Security API
9+
# HTTP 403 authorization error when calling the Microsoft Graph Security API
10+
11+
This article provides soltions to an HTTP 403 error that occurs when you call the Microsoft Graph Security API.
1012

1113
## Symptoms
1214

13-
When using Microsoft Graph Security API to call endpoints such as `https://graph.microsoft.com/v1.0/security/alert` and `https://graph.microsoft.com/beta/security/secoreScores`, you might get an 403 error with the following message:
15+
When using the Microsoft Graph Security API to call endpoints such as `https://graph.microsoft.com/v1.0/security/alert` and `https://graph.microsoft.com/beta/security/secoreScores`, you might get an 403 error with the following message:
1416

1517
> Auth token does not contain valid permissions or user does not have valid roles
1618
@@ -21,9 +23,7 @@ The error occurs due to one of the following reasons:
2123
- The access token lacks the necessary Microsoft Graph permission for the security endpoints.
2224
- The authenticating user that obtains the access token isn't in a required Azure AD admin role for delegated permission type token.
2325

24-
## Solution
25-
26-
### Microsoft Graph permission
26+
## Solution 1: Use valid Microsoft Graph permission
2727

2828
There are two types of tokens: application and delegated permission token. For more information, see [Application and delegated permissions for access tokens in the Microsoft identity platform](../app-integration/application-delegated-permission-access-tokens-identity-platform.md).
2929

@@ -39,7 +39,7 @@ For delegated permission token, Microsoft Graph permission is in the `scp` claim
3939

4040
For more information, see [Use the Microsoft Graph security API](/graph/api/resources/security-api-overview) and [Microsoft Graph permissions reference](/graph/permissions-reference).
4141

42-
### Microsoft Entra admin roles
42+
## Solution 2: Use valid Microsoft Entra admin roles
4343

4444
For delegated permission token, the authenticating user needs to be in one of the following admin roles:
4545

0 commit comments

Comments
 (0)