Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hello,
I have an on-premise Power BI Report Server set up and I've also setup Kerberos authentication. I've created the SPNs and the constrained delegation in Active Directory. I've also updated the rsreportserver.config file to include <RSWindowsNegotiate /> under AuthenticationTypes. In the web portal, my report runs. However, when I test the windows authentication connection by going to my report>manage>Data sources, I get an error, "Authentication type Integrated is not supported.". This does not make any sense to me because if the authentication connection doesn't work, wouldn't the report not run? I've recently upgraded my report server and Power BI Desktop from Oct 2017 version to March 2018 version. Is there a bug in this latest version?
Any solution from Microsoft on this?
I keep putting in FIREWALL requests with our Internal General Motors Networking team, thinking some firewall is causing this.
Seems to me it is a BUG in Power BI Server March 2018.
It gave me so many sleepless nights.
Hi,
I've experienced issues with the Test Connection button:
The test reported the connection was not configured correctly, when infact it was. Your issue sounds very similar.
You have included "<RSWindowsNegotiate /> " - but which order did you use? It could be important.
Did you use this documentation? : https://docs.microsoft.com/en-us/power-bi/report-server/configure-kerberos-powerbi-reports#authentic...
I've used that document. It's written like this:
<AuthenticationTypes> <RSWindowsNegotiate/> <RSWindowsNTLM/> </AuthenticationTypes>
User | Count |
---|---|
4 | |
3 | |
2 | |
2 | |
2 |
User | Count |
---|---|
6 | |
4 | |
3 | |
3 | |
2 |