Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Solved! Go to Solution.
Hi @RubenSO
It seems that the issue arises due to an organizational security policy requiring token protection, which is preventing access to the resources (Excel/CSV files on your OneDrive and SharePoint) via Power BI Desktop or Power Query in Excel. Here's how you can address the issue:
Steps to Troubleshoot and Resolve:
Confirm Organization Security Policies:
Reach out to your IT administrator or security team to confirm the specifics of the token protection policy. Policies like Conditional Access or device compliance may be restricting access via certain applications, such as Power BI Desktop or Power Query in Excel.
Use Power BI Service for Connection:
Since you mentioned that the Power BI Service works without issues, you can use the service to create a dataflow connecting to your OneDrive or SharePoint files. Afterward, you can connect to the dataflow from Power BI Desktop.
Enable Device Compliance:
Ensure your device is compliant with organizational policies. From the error details, it seems your device is marked as compliant, but recheck that all required configurations are met:
Sign in to Microsoft Endpoint Manager to review compliance.
Install or update Microsoft Authenticator if required.
Ensure Updated Applications:
Make sure your Power BI Desktop and Microsoft Office applications are updated to the latest versions. Sometimes, older versions can conflict with token policies.
Try Alternate Authentication:
Sign out and sign back in using the organizational account associated with the files. You can do this by:
In Power BI Desktop or Excel, go to File > Options and Settings > Data Source Settings, and clear the credentials for OneDrive/SharePoint.
Reconnect using your work account.
Change File Location:
If you urgently need access and cannot resolve the token issue, temporarily move the files to a location without token protection (e.g., local storage) and load them into Power BI Desktop or Excel. However, note that this is a temporary workaround and may not align with your organization's data security policies.
Contact IT Support:
Share the full error details, including the error code (53003) and correlation ID, with your IT department. They can investigate logs and verify if specific applications like Power BI Desktop or Power Query in Excel are excluded from token protection.
Enable App-Specific Access:
Request your IT team to whitelist Power Query for Excel and Power BI Desktop within Conditional Access policies to allow them to bypass token protection, if permissible.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
Hello @RubenSO ,
the error says it all, you need to check with the IT guys at your company.
Proud to be a Super User! | |
Hi @RubenSO
It seems that the issue arises due to an organizational security policy requiring token protection, which is preventing access to the resources (Excel/CSV files on your OneDrive and SharePoint) via Power BI Desktop or Power Query in Excel. Here's how you can address the issue:
Steps to Troubleshoot and Resolve:
Confirm Organization Security Policies:
Reach out to your IT administrator or security team to confirm the specifics of the token protection policy. Policies like Conditional Access or device compliance may be restricting access via certain applications, such as Power BI Desktop or Power Query in Excel.
Use Power BI Service for Connection:
Since you mentioned that the Power BI Service works without issues, you can use the service to create a dataflow connecting to your OneDrive or SharePoint files. Afterward, you can connect to the dataflow from Power BI Desktop.
Enable Device Compliance:
Ensure your device is compliant with organizational policies. From the error details, it seems your device is marked as compliant, but recheck that all required configurations are met:
Sign in to Microsoft Endpoint Manager to review compliance.
Install or update Microsoft Authenticator if required.
Ensure Updated Applications:
Make sure your Power BI Desktop and Microsoft Office applications are updated to the latest versions. Sometimes, older versions can conflict with token policies.
Try Alternate Authentication:
Sign out and sign back in using the organizational account associated with the files. You can do this by:
In Power BI Desktop or Excel, go to File > Options and Settings > Data Source Settings, and clear the credentials for OneDrive/SharePoint.
Reconnect using your work account.
Change File Location:
If you urgently need access and cannot resolve the token issue, temporarily move the files to a location without token protection (e.g., local storage) and load them into Power BI Desktop or Excel. However, note that this is a temporary workaround and may not align with your organization's data security policies.
Contact IT Support:
Share the full error details, including the error code (53003) and correlation ID, with your IT department. They can investigate logs and verify if specific applications like Power BI Desktop or Power Query in Excel are excluded from token protection.
Enable App-Specific Access:
Request your IT team to whitelist Power Query for Excel and Power BI Desktop within Conditional Access policies to allow them to bypass token protection, if permissible.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
That's a question you will need to take to your company's DLP office. They likely implemented these policies.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
63 | |
63 | |
52 | |
36 | |
36 |
User | Count |
---|---|
80 | |
71 | |
58 | |
45 | |
44 |