Connect-PowerBIServiceAccount picks the wrong identity even when told the right one about powerbi-powershell HOT 4 OPEN

Try running powershell with "Run as a different user", this is shift + right click on the taskbar shortcut.

from powerbi-powershell.

@jsnape did running with a different user fix your issue or are you experiencing the problem still?
I'm adding a new way to authenticate which is providing your username and password directly into Connect-PowerBIServiceAccount, I'm interested in knowing if that will fix the issue too. You would call Connect-PowerBIServiceAccount and add -Credential (Get-Credential). Note this only works on Windows OS.

The Azure Active Directory Authentication Library (ADAL) is being used by the cmdlets, there is a way to seed the library with a username but it might get confusing if there is both -Credential and -Username as parameters to the cmdlet. I'm limited beyond that in controlling what the library returns after selecting the user. I could look into upgrading the component to a newer version as there may be a bug in the version being used.

from powerbi-powershell.

Released https://www.powershellgallery.com/packages/MicrosoftPowerBIMgmt/1.0.342, please verify if this can unblock you

from powerbi-powershell.

I'm sorry, I am now unable to repo the original issue so I can't guarantee the fix is really a fix. I can now pick an account with the account picker and it uses that one.

I do like the idea of passing a credential though. There is already a credential parameter but it requires ServicePrincipal to be passed as well.

from powerbi-powershell.