Failed to get OAuth resource, please make sure the OAuth is supported

[npvinhloc]

Today 2025-09-18, I cannot access to Power BI reports using live connection to AAS (hosted under australiasoutheast.asazure.com)

This is the error message

Underlying error message: Failed to get OAuth resource, please make sure the OAuth is supported
Activity ID: 3a20f7d0-e78f-4bb6-b7fa-8ad04ab051e2
Correlation ID: 51caf20b-532c-62aa-0b32-4f51de62be14
Request ID: b6fd30a6-4de6-eb26-2c26-12a7f758238f
Time: Thu Sep 18 2025 13:22:41 GMT+1000 (Australian Eastern Standard Time)
Service version: 13.0.26641.28
Client version: 2509.1.25882-train
Cluster URI: https://wabi-australia-southeast-b-primary-redirect.analysis.windows.net/

I'm still able to connect to the AAS using SSMS and Power BI Desktop, looks like this is Power BI Service problem.

I tried to update the credential by selecting different options but nothing works.

Has anyone faced and overcome this before, please help.

--

Thanks and best regards.

[npvinhloc]

Thanks @tayloramy 

Thank you for your time and support.

I checked the service health in Azure portal and saw some notification. 

Turns out it was AAS service health impact on our reagion (AustraliaSouthEast).

The only weird thing is we still can access the same AAS using Power BI Desktop and SSMS.

--

Thank you!

[tayloramy · Accepted solution]

Hi @npvinhloc, 

That error means the Power BI Service failed to acquire an Entra ID token for your Azure Analysis Services server. In practice, it often shows up during regional service issues or when the AAS firewall/allow-list path that the Service uses (different from Desktop/SSMS) is blocked or mis-resolved. 

Here's some steps to take to troubleshoot:

1. Check service health first
   Look for any current advisories on the Fabric status/known-issues page. If nothing is posted yet, also check Azure Service Health for your subscription.
   Links: Fabric service status / Known issues
2. Re-enter the dataset credentials (Service)
   In the workspace, go to … > Settings > Datasets > Data source credentials for the AAS live connection; choose Organizational account (OAuth2) and Edit. This won’t help if it’s an active incident, but it removes a stale token as a cause. Community threads show this error string when tokens can’t be acquired by the Service. 
3. Verify AAS firewall lets the Power BI Service in
   In the AAS server (Azure portal) go to Firewall and ensure “Allow access from Power BI” = On. This switch maintains Microsoft-managed allow-listing for the Service (different from Desktop/SSMS).
   Doc: Configure AAS firewall 
4. If you use network allow-lists/proxies
   Confirm your org isn’t blocking required Power BI endpoints. (Service paths differ from Desktop.)
   Doc: Power BI allow-list URLs 

If you've gone through these steps and still have a problem, open a ticket to Microsoft. 

Escalate to Microsoft Support with your IDs
Include Activity ID, Correlation ID, Request ID, Cluster URI, Client version, and exact time (yours was Sep 18, 2025 13:22:41 AEST on wabi-australia-southeast-b).
Start here: Open a ticket

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.