Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
Check it out now!Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
Hello,
I can not connect anymore to Power BI Services from the current PBIDesktop version.
When I try to connect to Power BI Services, I get a frozen Windows Security to connect to office 365 and I can not enter my credentials! The windows security is frozen and I have to end PBIDestop by task manager.
I noticed that the August 2020 version is OK. But that bug apprears from the September 2020 version to November 2020 version.
I'm on Windows Server 2016 .
Can you help me, please?
Solved! Go to Solution.
MS Support helped me and my problem is solved ! 😀
We did the following steps
- add DisableCertificateRevocationCheck = 1 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Power BI Desktop
- in IE / Options / Security / Local Intranet / Sites / Advanced : add https://office365.mycompany.com
- in IE / Options / Advanced : disable "Enable Integrated Windows Authentification"
Hi @nicolasf ,
Glad to hear the issue is gone. And thanks for your sharing.😀
In addition, please accept your reply as the solution. Your contribution is highly appreciated.
Best Regards,
Icey
MS Support helped me and my problem is solved ! 😀
We did the following steps
- add DisableCertificateRevocationCheck = 1 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Power BI Desktop
- in IE / Options / Security / Local Intranet / Sites / Advanced : add https://office365.mycompany.com
- in IE / Options / Advanced : disable "Enable Integrated Windows Authentification"
Hi @nicolasf ,
Glad to hear the issue is gone. And thanks for your sharing.😀
In addition, please accept your reply as the solution. Your contribution is highly appreciated.
Best Regards,
Icey
Hi @nicolasf ,
I am curious if this issue has been solved.
If it is solved, can you share the solution with us?
Best Regards,
Icey
Unfortunatly no Icey. I have found no solution for my problem
Hi @nicolasf ,
This may be realted to that the Product Team switched the library they used in the authentication process in the September drop.
Please try this: Using default system credentials for web proxy.
Best regards
Icey
If this post helps, then consider Accepting it as the solution to help other members find it faster.
Thank you Icey, but your recomanndation did not resolve my problem.
Any other suggestion?
Hi @nicolasf ,
If you are a pro user, it is suggested to create a support ticket to get further help.
Best regards
Icey
If this post helps, then consider Accepting it as the solution to help other members find it faster.