PowerBi with an excel file on Sharepoint failing to auto fresh

[sdoug]

Haven't had an auto refresh issues with my dashboards until this morning. All my dashboards with data sources on SharePoint failed to refresh. <ccon>DataSource.Error: We don't support reading encrypted workbooks.. Microsoft.Data.Mashup.ErrorCode = 10830. 

ErrorMessage = Policy sync failed, NetworkError.Category=FailureResponseCode, HttpResponse.StatusCode=404, HttpRequest.SanitizedUrl=https://substrate.office.com/CompliancePolicy/ClientSyncFile/ScrubbedEmail, HttpRequest.Id={B5A35A47-34C6-4DB4-AE5C-264D3DD6AB65}, CorrelationId=a54d3b26-6e6b-48f5-998c-21bad7f486e7, CorrelationId.Description=PolicyProfile. </ccon>;<ccon>We don't support reading encrypted workbooks.</ccon>. The exception was raised by the IDbCommand interface. I am wondering if this is the consequence of some new organizational policy change and how to fix it

[v-venuppu]

Hi @sdoug ,

I hope the information provided is helpful.I wanted to check whether you were able to resolve the issue with the provided solutions.Please let us know if you need any further assistance.

Thank you.

[v-venuppu]

Hi @sdoug ,

May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.

[v-venuppu]

Hi @sdoug ,

I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.

Thank you.

[v-venuppu]

Hi @sdoug ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @Thomaslleblanc for the prompt response.

The error is happening because Power BI can’t refresh encrypted or protected Excel files stored on SharePoint. This likely started due to a new compliance or sensitivity policy rolled out in your organization (like Microsoft Purview).

To fix it, open the Excel file, go to File > Info > Protect Workbook, and remove any sensitivity labels, passwords, or encryption. Once unprotected, the Power BI refresh should work again.

You can also share the CorrelationId with your IT/security team to check if a new policy is blocking access.

Make sure you're using the SharePoint Folder connector with Organizational Account authentication for best results.

Thank you.

[Thomaslleblanc · Accepted solution]

check the authentication in the connection - here is a similar error - https://community.fabric.microsoft.com/t5/Desktop/Keep-getting-error-of-quot-don-t-support-reading-e...