Forum Discussion
(PowerShell) Connect-PowerBIServiceAccount not working
Hello folks,
Since yesterday I have been unable to log on to PBI service through PowerShell with the
Request Id: 18389c28-151c-4286-aaf4-67606d172e00
Correlation Id: f79280b7-ad4f-4119-a7ad-5e6ef4b33032
Timestamp: 2021-02-19T11:53:23Z
Message: AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: 'ea0616ba-638b-4df5-95b9-636659ae5121'.
Problem found and solved!
It turned out that an update to the PowerShell extension for VS Code set this value "powershell.useX86Host": true. In other words, it started running 32 bit as default. Manually changing it back to x64 like shown in the screenshots belov solved the problem:
Cheers, Mike
19 Replies
Hi @v-shex-msft, I have this problem for a week already and it doesn't go away.
I've also checked App Registrations and there is no such app with the ID 'ea0616ba-638b-4df5-95b9-636659ae5121'. Any thoughts? ThanksOP here, now we are experiencing the same problem again, and is has persisted for several days.
OP here, problem is partially solved. The script runs fine in the PowerShell ISE editor, but it won't run in VS code. If you are having problems, try updating the MicrosoftPowerBIMgmt module with the command:
Install-Module MicrosoftPowerBIMgmt -force -AllowClobber
and then run the script in either PS command line tool or ISE. This has worked for me.
However, since VS code is a superior toll over cmd or ISE, and sinc it is a Microsoft product, I am holding my support ticket open.Problem found and solved!
It turned out that an update to the PowerShell extension for VS Code set this value "powershell.useX86Host": true. In other words, it started running 32 bit as default. Manually changing it back to x64 like shown in the screenshots belov solved the problem:
Cheers, MikeHi h4tt3n,
I test the Connect-PowerBIServiceAccount with OAuth mode and it works well.
What authorization mode you work on? Did this issue still appear on your side? Any policy or rule change that applies to your device/environment? (they may block power bi requests) Please share more detailed information to help us clarify these.
How to Get Your Question Answered Quickly
Regards,Xiaoxin Sheng
Hi Anonymous
The problem has disappeared again over the weekend. I assume it was due to overload on parts of the Microsoft servers or a small bug that was caught and fixed quickly.
Cheers, Mike
Problem disappeared by itself after 3 days.
OP here. The problem has returned again, and has persisted for about a week. No changes has been made on our side to any PS scripts. We get the exact same error message. What is the issue, and can we do anything about it?
Hi alexgor87,
If you do not change the setting on these function usage but this issue appears frequently. It means the issues may be related to some backend/remote processing of these function usages.
In my opinion, I'd like to suggest contact to the author of the packages to report this.Regards,
Xiaoxin Sheng
Exactly my thought. We use Microsofts official PowerBi management package, so I think the best thing to do is open a ticket with their support.
Maybe helpfull to note that recently I noticed that MSAL throws errors when trying to log on using interactive logon like explained on the site of Reza Rad https://radacad.com/powershell-cmdlets-for-power-bi-what-is-it-and-why-should-you-care/ . Like pasted below.
Now Powershell-ISE blocks on that, the popup does not come up. But the normal Powershell client continues after the warning. And still gives the opertunity to aquire a bearer token.
WARNING: False MSAL 4.64.0.0 MSAL.CoreCLR .NET Framework 4.8.9325.0 Microsoft Windows 10.0.26200 [2026-06-16
12:57:14Z] [MSAL:0001] WARNING SetAuthorityUri:78 Initializing authority from URI
'https://login.microsoftonline.com/organizations/' without authority type, defaulting to MsSts
