Forum Discussion
access_denied: AADSTS65005: The application 'Microsoft Power Query for Excel' asked for scope 'user_
alex Frelis69 dverliefden,
I have reported this issue internally. Will post back once I get any updates.
Regards,
Lydia
- RedAngle8 years agoFrequent Visitor
I have been having the same issue since yesterday - can't seem to find anything useful online.
If this were something that we could control, I would expect the error to say that the action is not permitted rather than reporting that the scope is unavailable. It almost feels like a feature in Azure AD or Office 365 has been removed!
I have logged a support request with the Azure AD team so will see what they say.
- RedAngle8 years agoFrequent Visitor
Update - when I look at the Azure AD admin portal, I can see an authentication failure when I try to connect to the Office 365 mailbox from Power BI. The source application is 'Microsoft Power Query for Excel' (as expected).
The failure reason is listed as:
The application required resource access list does not contain applications discoverable by the resource or The client application has requested access to resource, which was not specified in its required resource access list or Graph service returned bad request or resource not found. If the application supports SAML, you may have configured the application with the wrong Identifier (Entity). Try out the resolution listed for SAML using the link below: https://docs.microsoft.com/azure/active-directory/application-sign-in-problem-federated-sso-gallery?/?WT.mc_id=DMC_AAD_Manage_Apps_Troubleshooting_Nav#no-resource-in-requiredresourceaccess-list.
I am not running the very latest version of Power BI (I'm one version behind) so will update and see if that resolves the issue, but I don't expect it to.
- Anonymous8 years agoNot applicable
The same problem here. I have noticed yesterday and problem still persists today. I am running the latest version of Power BI Desktop. I have tried September 2017 version of PBI Desktop and the same result. So I guess it is not a problem of the last PBI Desktop update.
Does anyone have any clue please?