Re: "you have not approved any authentication serv...

amichalove · ‎01-14-2016

My ultimate goal is to connect Power BI to Dynamics CRM 2015 On-Premise.

This appears to be supported by Power BI Desktop as of April 2015, based upon this article, (see "Support for Custom ADFS Authentication Services"):

http://blogs.msdn.com/b/powerbi/archive/2015/04/22/16-new-updates-to-the-power-bi-designer-preview-a...

I have gotten so far as to connect to my Odata endpoint from my Dynamics CRM 2015 IFD deployment from Power BI Desktop, but I am then prompted for credentials and when I attempt to use the authentication method "Organizational Account" I recieve the message "We are unable to connect because this credential type isn't supported for this resource".

Multiple forum posts suggest this is resolved by using the Power BI Desktop app, going to File>Options & Settings>Options>Global|Security and then under "Approved ADFS Authentication Services" you will have your ADFS proxy.

For me, I just have this message: "You have not approved any authentication services on this computer". While there are two "i" icons indicating I can click for some contextual help, nothing happens.

I have searched for these messages, looked in documentation, even opened a case with Power BI support (which I do not recommend due to the lag between correspondences and their lack of knowledge on the topic -- I had to point them to the above resources to convince them it was even possible).

Does anyone know how to "approve an authentication service (on this computer)" or alternatively, add a "supported credential type for this (Odata) service" to Power BI?

Anonymous · ‎02-03-2016

@amichalove Did you get this resolved? I am about to go down the same path and would love to see someone else was able to connect CRM on prem to Power BI.

Thanks,

Scott

amichalove · ‎02-12-2016

@Anonymous sorry to say, this issue remains outstanding.

I am documenting some ADFS 2.0 settings Microsoft Support has given me and I will post that process when the issue is resolved.

One thing you can be sure of is that your ADFS must be 2.0 so if you have ADFS on a Windows Server 2008 R2 box, you will need to upgrade to Windows Server 2012. You can go ahead and do that while we continue to work this out with Microsoft.

amichalove · ‎02-18-2016

@Anonymous I have a light at the end of the tunnel to tell you about!

Microsoft support has acknowledged that the issue we are seeing is a bug with PowerBI, _AND_ it is actualy being addressed in the next release scheduled for March (2016, fingers crossed 🙂

In the meantime, they did have me run the following powershell command on my ADFS 2.0 server (Server 2012 only, will not run on 2008 R2).

Add-AdfsClient -Name "Microsoft Power BI" -ClientId "a672d62c-fc7b-4e81-a576-e60dc46e951d" -RedirectUri @("https://de-users-preview.sqlazurelabs.com/account/reply/", "https://preview.powerbi.com/views/oauthredirect.html") -Description "ADFS OAuth 2.0 client for Microsoft Power BI"

Add-AdfsClient -Name "Microsoft Power BI" -ClientId "a672d62c-fc7b-4e81-a576-e60dc46e951d" -RedirectUri @("https://de-users-preview.sqlazurelabs.com/account/reply/", "https://preview.powerbi.com/views/oauthredirect.html") -Description "ADFS OAuth 2.0 client for Microsoft Power BI"

Note that if this runs successfully, there is not feedback to the console, but if you then run the command Get-AdfsClient you should see the ADFS client listed along with atleast two others that your ADFS server sets up as part of the default installation.