Received error 500 when using the ThreatIntelligence.Read.All API

Kek Peng Tan 0 Reputation points
2026-11-17T08:34:12.3066667+00:00

I have been granted the required delegated permission, ThreatIntelligence.Read.All, for my application. However, for the past week, requests to this API endpoint have consistently returned an HTTP 500 Internal Server Error.

"error": {  
  "code": "generalException",

    "message": "Internal Server Error",

    "innerError": {}  
}
Microsoft Security | Microsoft Graph
0 comments No comments

2 answers

Sort by: Newest
  1. AI answer

    2026-11-17T08:39:49.55+00:00

    Validate the actual delegated token and signed-in user authorization before treating this as a service incident; the intelProfiles endpoint requires ThreatIntelligence.Read.All in the delegated token, admin consent, and at least the Security Reader role.

    1. Validate the access token actually sent

    For this specific endpoint, the documented request is:

    GET https://graph.microsoft.com/v1.0/security/threatIntelligence/intelProfiles
    Authorization: Bearer <access-token>
    

    Do not include a request body. The endpoint supports delegated work or school accounts and documents ThreatIntelligence.Read.All as its required delegated permission. Personal Microsoft accounts are unsupported.^1^

    Decode the exact access token used by the failing call and inspect these claims without posting the token publicly:

    • aud: must identify Microsoft Graph.
    • scp: must contain ThreatIntelligence.Read.All.
    • The token must represent the intended signed-in work or school user and tenant.
    • A delegated token carries permissions in scp; application permissions instead appear in roles.^2^

    Merely adding the permission to the app registration does not prove it is present in an already-issued token. ThreatIntelligence.Read.All requires admin consent for delegated access.^3^ After consent is granted, sign out, clear the application's token cache, sign in again, and inspect the newly issued token.

    There is a documentation inconsistency: the general Threat Intelligence overview lists delegated ThreatIntelligence.Read, while the operation-specific intelProfiles page lists delegated ThreatIntelligence.Read.All. Use the operation-specific requirement—ThreatIntelligence.Read.All—for this request.^4^

    2. Validate the signed-in user and environment

    The signed-in user must have at least the Security Reader role.^4^

    Also verify that:

    • The tenant has Microsoft Defender XDR or Microsoft Sentinel licensing.
    • The request targets the global Microsoft Graph service. This API is not supported in US Government L4, US Government L5/DOD, or the China cloud.^1^

    3. Isolate the application from the service

    Run the same GET /security/threatIntelligence/intelProfiles operation in Graph Explorer while signed in as the same user.^5^

    Interpret the result as follows:

    • Graph Explorer succeeds: compare its delegated scopes, user, tenant, and token claims with those used by the application. Microsoft specifically recommends these comparisons when Graph Explorer works but application code fails.^6^
    • Graph Explorer also returns 500 after consent and role checks: the issue is reproducible independently of the application or API Management path and should be escalated to Microsoft.
    • Direct Graph succeeds but the API Management route fails: capture the APIM trace and compare the outbound method, URL, and Authorization header. Do not expose the Bearer [Token] in logs or support posts.

    4. Escalate the persistent 500

    An HTTP 500 means Microsoft Graph encountered an internal error while processing the request; generalException alone does not establish whether authorization state or a backend defect triggered it.^7^

    Because the failure has persisted for a week, open a Microsoft support case if it remains reproducible after the checks above. Include:

    • UTC timestamp of several failures.
    • HTTP method and sanitized URL.
    • Response status and complete sanitized error body.
    • request-id, client-request-id, and date response headers.
    • Whether the identical request fails in Graph Explorer.
    • Confirmation that scp contains ThreatIntelligence.Read.All.
    • Confirmation that the user has Security Reader.
    • Tenant cloud type and relevant Defender XDR/Sentinel licensing.

    Do not include the access token itself. No endpoint-specific public documentation supplied here identifies this persistent intelProfiles 500 as an acknowledged platform-wide incident.


    References

    1. List intelProfiles - Microsoft Graph v1.0 | Microsoft Learn
    2. HTTP 403 authorization error when calling the Microsoft Graph Security API
    3. Microsoft Graph permissions reference
    4. Use the Microsoft Graph APIs for Microsoft Threat Intelligence
    5. Graph Explorer | Try Microsoft Graph APIs - Microsoft Graph
    6. Application and delegated permissions for access tokens in the Microsoft identity platform
    7. Microsoft Graph error responses and resource types
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Shaurya Bhardwaj 0 Reputation points
    2026-11-17T08:36:44.0766667+00:00

    Verify User Entra ID Roles: Delegated permissions require the signed-in user to hold an appropriate Microsoft Entra directory role (such as Security Reader, Security Administrator, or Global Reader). If the user lacks these roles, the backend service often fails with a generic 500 error instead of a clean 403 Forbidden.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.