Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago

Power BI API via PowerShell fails in Azure DevOps

Hi all,   I'm trying to automate the deployment of Power BI (and other modern DWH components) via Azure DevOps releases. I've created a PowerShell script that looks at the contents of a setup file ...
Need Help
Anonymous's avatar
Anonymous
Not applicable
7 years ago

The reason I can't use Power BI Actions (I tried!) is that it needs a username and password. This is not acceptible for our clients. Best practice is to use a client id. 

Via PowerShell this is 100% possible. In fact the scripts work when I run them locally on my laptop. They seem to get stuck on the authentication part when I run them as part of a DevOps pipeline. 

 

I'm interested in your blog article! 

Jayendran's avatar
Jayendran
Icon for Solution Sage rankSolution Sage
7 years ago

Hi Anonymous 

Ok could you please try my script below

 

$applicationId = "xxxxxxxx";
$securePassword = "xxxxxx" | ConvertTo-SecureString -AsPlainText -Force
$credential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $applicationId, $securePassword
Connect-PowerBIServiceAccount -ServicePrincipal -Credential $credential -TenantId "xxxx"

Which is using the Client ID autentication part.

 

I've also provided this answer in SO

 

By this way it will work in both your local and azure devops

  • Anonymous's avatar
    Anonymous
    Not applicable
    7 years ago

    This doesn't work because the Power BI cmdlets don't accept service principals for most operations. For example:

     

    Therefore I'm trying to login using a native app (instead of web app) using the code I posted in the OP. That works perfectly fine in Windows, just not in DevOps.