Hi @ReneWynands95 ,
An Azure AD token and an embed token are both used to authenticate and authorize access to Power BI content, but they serve different purposes.
An Azure AD token is required for all REST API operations and is used to access Power BI in both the embed for your customers and embed for your organization solutions. It expires after an hour and is used to generate the embed token in the embed for your customers solution.
On the other hand, an embed token is generated by the application in the embed for your customers solution. It grants web users access to Power BI content and specifies the content that a user can access, as well as their access level (view, create, or edit). The lifetime of the embed token is set to the remaining lifetime of the Azure AD token used to call the GenerateToken API. Therefore, if you use the same Azure AD token to generate several embed tokens, the lifetime of the generated embed tokens will be shorter with each call.
For your demands, please try embed for your custom solution.
The embed for your customers solution allows you to build an app that uses non-interactive authentication against Power BI. Your customers are likely to be external users, and they don't need to sign in using Power BI credentials to view the embedded content. Typically, this solution is used by independent software vendors (ISVs) who are developing applications for third parties. For a tutorial, see Embed Power BI content using a sample embed for your customers application.
For more details, you can read related document: Permission tokens needed for embedding a Power BI app - Power BI | Microsoft Learn
Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
