Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
I want to use token authenticate for the Power BI REST APIs. Now I have a service principal, then I using the az command line to login in and generate the token:
az login --service-principal -u ${app_id} -p ${password} --tenant ${tenant_id}
$token= az account get-access-token --query accessToken
And it does get the token.
However, I could not authenticate my power bi server, I got the error 403 Forbidden.
The service principal have the correct rights and add to the workspace access.
In order to verify the permission, I use the source code of a tripartite extension powerbi action.
And there is function Invoke-API:
Function Invoke-API {
Param(
[parameter(Mandatory = $true)][string]$Url,
[parameter(Mandatory = $true)][string]$Method,
[parameter(Mandatory = $false)][string]$Body,
[parameter(Mandatory = $false)][string]$ContentType
)
$apiHeaders = Get-PowerBIAccessToken
...
}
return $result
}
It is using the Get-PowerBIAccessToken to get the token.
So, I using same service principal to connect powerbi service:
$powerbiUrl = 'https://api.powerbi.com/v1.0/myorg'
$sp_secret_key = $Env:sp_secret_key | ConvertTo-SecureString -asPlainText -Force
$organizationType = 'Public'
$cred = New-Object System.Management.Automation.PSCredential($sp_client_id, $sp_secret_key)
Connect-PowerBIServiceAccount -Environment $organizationType -Tenant $sp_tenant_id -Credential $cred -ServicePrincipal
Publish-PowerBIFile -WorkspaceName $target_wrokspace_name -FilePattern "$FilePattern" -Create $Create -Overwrite $Overwrite
The function Publish-PowerBIFile will invoke the Invoke-API. Surprisingly, it worked.
This seems to indicate that my Service Principal has sufficient permissions.
But unfortunately, the execution of this function calling Connect-PowerBIServiceAccount requires the installation of the MicrosoftPowerBIMgmt function module,Our production environment is in a high security environment and does not allow me to install this module.
So I have to generate a token through Service Principal to complete the authentication.
So my question is, how is the way I generate the token using Service Principal different from the token generated by Get-PowerBIAccessToken? What should I do to be successful?
Any advice would be greatly appreciated.
update:
I grab the token through F12 and use postman to verify the token obtained by F12 and the token obtained by az account get-access-token --query accessToken, and it is concluded that the token obtained by F12 is valid. So how to generate a valid token through sp or does generating a token require additional permission settings?
Solved! Go to Solution.
Thanks for your reply. I have already check those documents. And I have resolved this issue by adding --resource https://analysis.windows.net/powerbi/api to the az account get-access-token command.
Hi @112JKJKSD ,
Please refer the following link to get the token by REST API:
https://learn.microsoft.com/en-us/rest/api/power-bi/embed-token/generate-token
And check if it hit any of following considerations and limitations:
In addition, the following link had the similar problem as yours. Hope its solution can also help you solve the problem.
Power BI embed error 403 forbidden error from server
Best Regards
Thanks for your reply. I have already check those documents. And I have resolved this issue by adding --resource https://analysis.windows.net/powerbi/api to the az account get-access-token command.
Hi @112JKJKSD ,
It's glad to hear that your problem has been resolved. And thanks for sharing your solution here. Could you please mark your post as Answered? It will help the others in the community find the solution easily if they face the same problem as yours. Thank you.
Best Regards
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |