SHD / MC Checker

[serviceRestored] PB1262330 | Power BI | Some users may be unable to connect to Azure Analysis Services live connection reports from Power BI desktop



PB1262330 | Power BI | Some users may be unable to connect to Azure Analysis Services live connection reports from Power BI desktop

Status serviceRestored
Classification advisory
User Impact Users may have been unable to connect to Azure Analysis Services live connection reports from Power BI desktop.
Last Updated 03/30/2026 22:43:14
Start Time 02/20/2026 19:00:00
End Time 03/28/2026 14:01:00
Latest Message Title: Some users may be unable to connect to Azure Analysis Services live connection reports from Power BI desktop

User impact: Users may have been unable to connect to Azure Analysis Services live connection reports from Power BI desktop.

More info: As a workaround, affected users could disable the “Sign-in experience for data sources” option in the security settings of Power BI Desktop and restart the application to mitigate the issue.

Final status: We’ve confirmed that a recent service change to enable “Sign-in experience for data sources” by default contained a code misconfiguration which resulted in timeout errors when attempting to connect to Azure Analysis Services. We’ve uploaded a new build to the Microsoft Download Center and Windows Store containing a fix to address this error and have confirmed with a subset of affected users that the new build remediates impact.

Scope of impact: Some users attempting to connect to Azure Analysis Services live connection reports from Power BI desktop may have been impacted.

Start time: Friday, February 20, 2026, at 7:00 PM UTC

End time: Saturday, March 28, 2026, at 2:01 PM UTC

Root cause: A recent service change to enable “Sign-in experience for data sources” by default contained a code misconfiguration which resulted in timeout errors when attempting to connect to Azure Analysis Services.

Next steps:
– We’re analyzing the offending service change to determine why the potential for impact wasn’t caught during our internal testing and validation stages. This analysis will help us to ensure similar impact scenarios don’t occur in the future by bolstering our internal testing procedures.

This is the final update for the event.