Refresh Failure

[JKPrasannaD]

Normally my system is compliant and currently I am on MVD but receiving AADSTS53000 – DeviceNotCompliant error  and my report continuously gets refresh failure. Tried editing the data source settings and republishing but still i receive the same error. any ideas how to resolve this issue? 

Thanks in advance

[v-dineshya · Accepted solution]

Hi @JKPrasannaD ,

Thank you for reaching out to the Microsoft Community Forum. The error AADSTS53000 - DeviceNotCompliant indicates that Microsoft Entra ID (Azure AD) Conditional Access policy is blocking the token request because the device used for authentication is not meeting compliance requirements.

Please try below general troublesshooting steps to fix the issue.

1. Please Configure Service Principal authentication instead of user credentials. Assign it access to Data source and Power BI dataset.

2. Use On-Prem Gateway, Configure Enterprise Gateway and Bind dataset to gateway. use stored credentials within gateway

3. Please check with Azure admin team and ask them to exclude Power BI / Service Accounts from CA Policy.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

[Poojara_D12 · Accepted solution]

Hi @JKPrasannaD 

The AADSTS53000 error is happening because your company's Microsoft Entra Conditional Access policies are enforcing a strict device compliance check that the cloud-based Power BI Service engine simply cannot pass. While your personal machine or Virtual Desktop (MVD) is fully compliant, the scheduled data refresh runs in a background Microsoft cloud environment that lacks a physical device identity to present to your security framework, causing the policy to block the connection. To fix this, your IT or Entra administrator needs to modify the conditional access policy targeting the data source (like SharePoint or Azure SQL) and explicitly add the account running the refresh to the policy's Exclude list. If security policies forbid user exclusions, you should transition the dataset to authenticate via an On-Premises Data Gateway or use a Service Principal (App Registration), which shifts the authentication rules away from user-level device compliance checks and allows the background cloud refresh to complete successfully.

[v-dineshya · Accepted solution]

Hi @JKPrasannaD ,

Thank you for reaching out to the Microsoft Community Forum. The error AADSTS53000 - DeviceNotCompliant indicates that Microsoft Entra ID (Azure AD) Conditional Access policy is blocking the token request because the device used for authentication is not meeting compliance requirements.

Please try below general troublesshooting steps to fix the issue.

1. Please Configure Service Principal authentication instead of user credentials. Assign it access to Data source and Power BI dataset.

2. Use On-Prem Gateway, Configure Enterprise Gateway and Bind dataset to gateway. use stored credentials within gateway

3. Please check with Azure admin team and ask them to exclude Power BI / Service Accounts from CA Policy.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

[v-dineshya]

Hi @JKPrasannaD ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[v-dineshya]

Hi @JKPrasannaD ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[GilbertQ]

Hi @JKPrasannaD 

Can you mkae sure that the gateway is a registered device on your network?

[krishnakanth240]

Power BI might still be using old authentication token. Try clearing Data Source Settings and cache in Power BI Desktop, sign out from Power BI and Power BI service then sign back in and republish report. Also re-enter credentials in Power BI Service dataset settings