Access token doesn't have claims principal object

[krzysztof]

I have a live connection to the analytics cube.
I am getting errors on the power bi web visualizations:

Error fetching data for this visual

A connection could not be made to the data source with the Name of '{"protocol":"analysis-services","address":{"server":"asazure://westeurope.asazure.windows.net/rds","database":"rds_DWH"},"authentication":null,"query":null}'.

Please try again later or contact support. If you contact support, please provide these details.

• Activity IDa6d355a6-ce2b-4601-adfa-fc07f72233af
• Request IDc92bbf32-d7f7-48ff-87d5-fc2968bc5aff
• Correlation ID30373731-4268-a420-0303-f15cc04c711b
• TimeTue Oct 15 2024 10:58:38 GMT+0200 (czas środkowoeuropejski letni)
• Service version13.0.24436.48
• Client version2410.1.21281-train
• Cluster URIhttps://wabi-north-europe-k-primary-redirect.analysis.windows.net/
  
  
  
  I'm trying to connect to the cube via ssms:
  

[zdycho]

Same problem here 

[mar_c]

In the meantime, (for me) the problem has disappeared. Suddenly it worked again, which confirms my assumption that it was a general problem.

@Anonymous Is there an incident report or official information on the matter?

[Anonymous]

Hi all,

We have seen on the internal platform that other engineers have reported this issue and submitted it.

The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

Best Regards,

Clara Gong

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.

[FrancescoPwc]

Happens for me too since today

[mar_c]

Since about saturday we are experiencing the same issues for westeurope.asazure.windows.net

Only difference is, that in our case it's a tabular model and not a cube.

The connection problems occur irregularly with different users. All errors include the phrase "Access token doesn't have claims principal object"

One side effect is that the tabular models are occasionally not visible in the Azure Portal.

As far as i know we have not made any changes to the Entra ID settings (MFA has always been activated for some users - It doesn't work with the others either)

[marcdv]

Same here, since this weekend the processing of the tabular model from Azure Data Factory using a service principle is giving this error  as well. Sometimes it work but most of the time it doesn't.

[bt_bgd]

I ran into the same problem and the problems are occuring randomly. Users report the problem and it seems to dissapear without intervention. Also in my data pipelines refreshing the models I get:

Microsoft.AnalysisServices.ConnectionException: Access token doesn't have claims principal object. 

And retrying the pipelines just works. Any idea what could cause this?

[fcannas]

Same here

[Anonymous]

Hi @krzysztof ,

You can try the following steps to resolve this issue:

1. First make sure that the user accessing the report has the necessary permissions to access the Analysis Services data.

2. If you are using a gateway, make sure it is configured and operating correctly. Sometimes, gateway issues can cause connectivity problems.

3. Verify the status of the service. Ensure that there are no network problems or firewall settings preventing connection to the server.

Best Regards,

Clara Gong

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.

[krzysztof]

Do you know what the error status is

[GilbertQ]

Hi @krzysztof 

I will talk to your azure analysis service admin to make sure that the user account or user principle that you are using still has the correct access to the analysis services database

[MichauW]

Connection problems seem to occur randomly.

We tested connections with SSMS, Dax Studio, Tabular Editor, PowerBI Desktop - each of these tools randomly displays an error similar to what Krzysztof pasted. All errors include the phrase "Access token doesn't have claims principal object". We are now tracking the thread of recently enabled MFA in Azure, because so far the problems occur mainly on the end user -> AAS line.

M.