Forum Discussion
Web Content - Access Method - WWW-Authenticate header doesn't contain a valid authorization URI
Hi timowille,
I found the same issue reported before, and the PG said:
"The Azure App part is currently unsupported due to a limitation with Azure Active Directory."
Best Regards,
Qiuyun Yu
- timowille9 years agoNew Member
Hi Qiuyun Yu,
is there any information on when this will work or is there a workaround? We would like to offer a REST API to make on-prem data available to Organizational Accounts in Power BI. Data Gateway is no option.
Thanks for your support!
Timo
- v-qiuyu-msft9 years agoCommunity Support
Hi timowille,
The workaround provided by the PG is:
To make this work with Power BI, the endpoint needs to return an URL which looks like
WWW-Authenticate: Bearer authorization_uri="https://login.windows.net/a1a2578a-8fd3-4595-bb18-7d17df8944b0/oauth2/authorize"
Where the GUID is the AAD tenant ID. This cannot be done entirely via configuration, it involves writing code on the service side.
Best Regards,
Qiuyun Yu- wolfchan8 years agoNew Member
Hi,
I had try by return below message, and Power BI do pop up and ask for O365 login, but after success login, when go to connect it still say no permission. Any suggestion?
Thank you very much.
v-qiuyu-msft wrote:Hi timowille,
The workaround provided by the PG is:
To make this work with Power BI, the endpoint needs to return an URL which looks like
WWW-Authenticate: Bearer authorization_uri="https://login.windows.net/a1a2578a-8fd3-4595-bb18-7d17df8944b0/oauth2/authorize"
Where the GUID is the AAD tenant ID. This cannot be done entirely via configuration, it involves writing code on the service side.
Best Regards,
Qiuyun Yu