Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi everyone,
I have followed the tutorials for embeding a Power BI report into a website and I have got the code working fine on my local machine/development environment, however, when the code is released onto production machines, I am unable to connect to the Azure AD service.
the line of code:
authenticationResult = await authenticationContext.AcquireTokenAsync(ResourceUrl, ClientId, credential);
-- using the Microsoft.IdentityModel.Clients.ActiveDirectory library
Is throwing the exception message:
Unable to connect to the remote server
I assume this is because the production environment is locked down, but I am not sure what I need to allow to be able for it to see the remote server. Ports 80 and 443 are open, from reading around I thought these were the only ones needed.
Any help much appreicated,
Thanks.
Did you get to fix the problem?
Help me, please!
Thanks.
@pconnor wrote:
Hi everyone,
I have followed the tutorials for embeding a Power BI report into a website and I have got the code working fine on my local machine/development environment, however, when the code is released onto production machines, I am unable to connect to the Azure AD service.
the line of code:
authenticationResult = await authenticationContext.AcquireTokenAsync(ResourceUrl, ClientId, credential);
-- using the Microsoft.IdentityModel.Clients.ActiveDirectory library
Is throwing the exception message:
Unable to connect to the remote server
I assume this is because the production environment is locked down, but I am not sure what I need to allow to be able for it to see the remote server. Ports 80 and 443 are open, from reading around I thought these were the only ones needed.
Any help much appreicated,
Thanks.
You can try to shut down the firewall of the production with approval the of the server admin. If then it works well, it is some port that maybe blocked. Another approach would be using fiddler to trace the network traffic to see what http requests are blocked/returning response status code other than 200.
User | Count |
---|---|
5 | |
5 | |
3 | |
2 | |
2 |
User | Count |
---|---|
9 | |
7 | |
4 | |
4 | |
4 |