Azure Portal Authentication Token Issue – Microsoft_AAD_Devices Extension Failing for Graph Resource

Question

Azure Portal Authentication Token Issue – Microsoft_AAD_Devices Extension Failing for Graph Resource

kedar giri 106

I am currently facing an issue in the Azure portal while accessing the Devices blade.

Error message:

The portal is having issues getting an authentication token. The experience rendered may be degraded.Additional information from the call to get a token: Extension: Microsoft_AAD_Devices Resource: graph Details: The extension 'Microsoft_AAD_Devices' has not defined the resource access for resource 'graph' in the extension's configuration, or in the portal's configuration. CorrelationId: e325be96-0fc4-4cc1-8512-f6e4dfa6dd9c

What I have already tried:

Signed out and signed back into the Azure portal
Tried multiple browsers (Edge, Chrome)
Used Incognito/InPrivate mode
Attempted access via Microsoft Entra admin center (https://entra.microsoft.com/)
Cleared browser cache

Despite all the above steps, the issue still persists.

Is this a known issue? Any fix or workaround?

Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-04-29T04:54:19.7133333+00:00
Hey there! It looks like the Devices blade in the Azure Portal isn’t defining the Microsoft Graph resource scope for its “Microsoft_AAD_Devices” extension, so when it tries to call out for an access token it fails with that message:

“The extension ‘Microsoft_AAD_Devices’ has not defined the resource access for resource ‘graph’ in the extension’s configuration….”

Unfortunately that’s a portal‐side configuration issue (the extension’s manifest is missing the Graph resourceAccess entry), so you’ll continue to see a degraded experience until the Portal team ships a fix. In the meantime, here are a couple of workarounds:

Use the Microsoft Entra admin center’s Devices page (https://entra.microsoft.com → Devices)

Call devices via Azure CLI / PowerShell • Azure CLI:
az ad device list
• PowerShell:
Get-AzureADDevice

Run queries against Microsoft Graph directly (e.g. in Graph Explorer or your own app) • GET https://graph.microsoft.com/beta/devices

We’re tracking this as a known issue and will update the extension to include the proper Graph resource access as soon as possible.

To help us nail down any tenant-specific or network-related causes, could you share:

• The Tenant ID and exact Timestamp when the error (CorrelationId e325be96-...) occurred

• Any Conditional Access policies or IP-range restrictions in place

• A screenshot or copy of your browser’s F12 console logs when the error fires

Reference:

• Problems acquiring tokens to access a resource – common OAuth token-acquisition failures and root causes

https://docs.microsoft.com/azure/active-directory/develop/v1-protocols-oauth-code#use-the-access-token-to-access-the-resource

Hope that helps! Let me know once you have those additional details.

Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.
kedar giri 106 Reputation points

2026-04-29T06:07:02.5833333+00:00
Thanks for the update.

Here are the requested details:

Tenant ID: PII

Timestamp: (2026-04-29 11:36 GMT +5:45)

Conditional Access: No Conditional Access policies or IP restrictions are configured in this tenant

Console Logs:

Additional Info:

Issue is consistently reproducible

Occurs across multiple browsers and sessions

Also persists in Entra portal (https://entra.microsoft.com)
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-04-29T06:12:10.2366667+00:00

Hello kedar giri

Lets continue over private messages!
Michael 0 Reputation points

2026-04-29T11:39:39.0566667+00:00

We're having the same issue!
Jamie Drummond 0 Reputation points

2026-04-29T12:54:22.8866667+00:00

We are seeing same issue as well
lukasr17 0 Reputation points

2026-04-29T14:27:53.5766667+00:00

Same issue. Does anyone have news or a fix for this?
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-04-30T03:05:23.21+00:00

Hello

We will check internally and get back to you!
Rukmini 43,915 Reputation points Microsoft External Staff Moderator

2026-05-01T03:49:31.4666667+00:00

Hello kedar giri

How are trying to login to portal is it portal.azure.com or using any Tenant specific URL?
Gino Huang 0 Reputation points

2026-05-04T08:28:56.9633333+00:00

We are experiencing the same issue. We have tried all of the methods mentioned above, but none of them have resolved the problem. We are unable to continue operating or testing features such as device identity and Conditional Access.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Suleiman da Costa 0 Reputation points

2026-05-04T16:20:53.0733333+00:00

Seeing the same issue - tested on multiple devices, OS' and networks. We are in SA region.
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-05-14T15:06:24.0833333+00:00

kedar giri The issue occurred due to a backend configuration problem affecting the Microsoft_AAD_Devices extension while requesting authentication tokens for the Graph resource.

This has now been identified and fixed by the engineering team.

Next steps: Please sign out and sign back into the Azure portal, then try accessing the Devices blade again. The issue should now be resolved.

If the problem persists, kindly share an updated Correlation ID and timestamp for further investigation.