Forum Discussion
Embedded - Accessing an external workspace
- 3 years ago
To connect to a customer's workspace via the Power BI REST API, your app would need to be added as a guest to the customer's tenant. Once the app has been added as a guest, you can use the OAuth 2.0 client credentials grant type for authentication. You would need to obtain the necessary client ID and secret from the customer's tenant. This information can be obtained from the Azure Active Directory in the customer's tenant, and is used to obtain an access token which is then used for making API requests. The customer would need to provide you with these credentials in order for your app to be able to access their workspace via the Power BI REST API.
To connect to a customer's workspace via the Power BI REST API, your app would need to be added as a guest to the customer's tenant. Once the app has been added as a guest, you can use the OAuth 2.0 client credentials grant type for authentication. You would need to obtain the necessary client ID and secret from the customer's tenant. This information can be obtained from the Azure Active Directory in the customer's tenant, and is used to obtain an access token which is then used for making API requests. The customer would need to provide you with these credentials in order for your app to be able to access their workspace via the Power BI REST API.
Much appreciated jaweher899
Am I right in saying that in order for the customer to provide me with the necessary client ID and secret, they would need to also create an app registration on their end?
So just to confirm, the flow would look something like this:
1) My app added as a guest on the customer's tenant/workpsaces
2) Customer sets up AOD app registration and provides me with the clients ID & secret
3) I use this to generate an access token
4) The access token can then be used to generate the embed token for the workspace artifacts that my App has access to?
Thanks