Power BI refresh error points to device compliance checks
A Fabric Community user reported repeated Power BI report refresh failures with the Microsoft Entra error AADSTS53000. Microsoft’s Entra documentation maps that code to DeviceNotCompliant, where a Conditional Access policy requires a compliant device and the device does not meet that requirement. The user said editing data source settings and republishing the report did not resolve the issue.
Power BI refresh errors are easy to treat as Power Query, gateway, credential, or model problems. That is often the right place to start, but this report shows another possible path: identity and device-compliance rules can block the workflow before the analyst’s data logic is the real issue. For report builders who inherited dashboards from someone else, that distinction matters. Rebuilding queries or republishing the PBIX file can waste hours if the blocker lives in Entra Conditional Access, managed virtual desktop compliance, or sign-in policy. The useful move is to preserve the exact error code and route it to the person who owns device compliance, not only the person who owns Power BI.
Analysis
When a refresh fails, copy the full AADSTS error from refresh history before changing the report. If it includes AADSTS53000 or DeviceNotCompliant, ask IT to check Entra sign-in logs and Conditional Access policy results for the affected user, gateway, or service context.
Citation
This executive briefing was curated and analyzed by Collab365. To reference this analysis, please attribute: "This briefing is available on Collab365 Spaces (spaces.collab365.com)".