Note: This article was originally published on https://d-bi.gitee.io and medium, and will be migrated to CSDN in June 2023
mentioned above
There are many blog posts on this site about implementing Power BI REST API, including:
- How powerful is the Power BI REST API? A must-read for PBI developers
- Power BI REST API practical tutorial: PowerQuery as an example
- Using Python to call Power BI REST API
- Power BI Report Server REST API in action
These blog posts cover as much as possible all specific uses of the PBI API. However, nearly a year has passed, and the content should be updated and supplemented. For example, if the previous article does not cover the Service Principle methods commonly used by enterprise users and the practice of using Power Automate to integrate Key Vault, this article will make necessary supplements in this regard.
Note: This article assumes that the reader has read the previous article or related MS documents, so some specific steps may be omitted depending on the situation.
Actual combat
1. When registering the App and granting permissions, the effects will not be applied immediately after the permissions are granted.
Likewise, effects will not be applied immediately after permissions are removed
2. For security and compliance reasons, sensitive data should use Key Vault and enable Secure Outputs.
3. v2.0 URI should be used when obtaining Access Token
4. The verification method when calling the REST API should be consistent with that when obtaining the Acess Token.
If the OAuth method is not used when obtaining the Access Token, this method cannot be used when calling the API, otherwise an error will be reported.
test
Follow the author: Zhihu Power BI official community