Forum Discussion
Sharepoint authentication error "We couldn't authenticate with the credentials provided"
Hi all,
I have several reports using files from Sharepoint as a data source. I used to have Organizational account setup for authentication, which worked perfectly for a long time.
All of a sudden, this authentication stopped working when I tried to import a new Sharepoint file. I've tried removing the authentication settings as suggested in other posts. This unfortunately destroyed all Sharepoint connections I had setup which means none of them are working now.
As soon as I try to authenticate through Organizational, Basic or Microsoft Account, the prompt gives a "We couldn't authenticate with the credentials provided" error.
I've tried several things so far but nothing seems to work.
I can access the Sharepoint site without issues with the same credentials, so that doesn't seem to be the issue.
Source = Excel.Workbook(Web.Contents("https://Contoso.sharepoint.com/sites/Innovation/Shared%20documents/General/Datasets/" & #"CustomerName" & "/hours.xlsx"), null, true),
- Anonymous4 years ago
Hi,
My issue was different from the one described in the post you link.
Appartently it was an issue with the Edge authentication prompt. I fixed the issue by changing my default browser to chrome and in Power BI go to Settings > Security > User my default webbrowser.
This fixed the issue.
17 Replies
- CHayNew Member
Hey all if you are still having issues with this you can go to
Transform data > right click on your table and click advanced editor > check your url there
https://company_sharepoint.com/:x:/r/sites/ConnectedWorker/Shared%20Documents/Device/Device%20Allocation/Master%20Device%20Allocation.xlsxif it looks like this delete the /:x/r/ or whatever similar file path you have there
if this doesn't work you can clear permissions that may work good luck - TrueBlueWomanRegular Visitor
One other option that might work for this is that if your SharePoint list columms is linked to other areas of SharePoint, you can remove those columns. It's possible that those areas are restricted and even though you're not utilizing the underlying information, it may be preventing you from accessing that data. I removed those fields that could be expanded and my error went away.
- AnonymousNot applicable
Thank you for this! I never would have figured out this was my issue after trying to connect over and over again. A different error should be displayed when this happens.
- v-yanjiang-msftCommunity Support
Hi Anonymous ,
Please see if this similar thread helps.
Best Regards,
Community Support Team _ kalyjIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- AnonymousNot applicable
Hi,
My issue was different from the one described in the post you link.
Appartently it was an issue with the Edge authentication prompt. I fixed the issue by changing my default browser to chrome and in Power BI go to Settings > Security > User my default webbrowser.
This fixed the issue.
- Mery1526New Member
I had the same issue and this method solved it. Thanks a lot !
- AnonymousNot applicable
Am I missing something here? Neither this post or the one you link to seem to provide a working solution to this issue. Wondering why theye're both marked as resolved?
- AnonymousNot applicable
I am also not able to the use the function Web.Contents with SharePoint because I could not be authenticated even when using Chrome. Any other solution?
- AnonymousNot applicable
Hi, I was facing the same issue, and I found a work around. There is an option "Add shortcut to Onedrive", and this created a folder shortcut in my onedrive. I used this to select the Excel file source in Power BI. It seems to be working as expected, with around 5 mins of delay to update the data in Power BI after I changed my files in Sharepoint.
- kevin-kyAdvocate II
I encountered this error today and the resolution was very unexpected. I found if the excel file name in the sharepoint library has a pound sign # in it, it will fail to import with this error. I removed the pound and this error cleared for me.