Forum Discussion
AAD Token Generation
- 1 year ago
Hi Anonymous,
Thank you for your detailed input ibarrau.
To confirm, the 403 error despite having Tenant.ReadWrite.All usually indicates a configuration issue. Please ensure that the "Embed content in apps" setting is enabled in the Fabric Admin Portal under Tenant Settings. If you're using a Master User approach, make sure Admin Consent has been granted for the Tenant.ReadWrite.All permission in Azure Active Directory. For Service Principal authentication, verify that the same permission is granted and that the "Service principals can call Fabric public APIs" setting is enabled in the Fabric Admin Portal.
Hope my suggestion gives you good idea, if you have any more questions, please feel free to ask we are here to help you.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.Thank you.
Hi Anonymous,
Thank you for your detailed input ibarrau.
To confirm, the 403 error despite having Tenant.ReadWrite.All usually indicates a configuration issue. Please ensure that the "Embed content in apps" setting is enabled in the Fabric Admin Portal under Tenant Settings. If you're using a Master User approach, make sure Admin Consent has been granted for the Tenant.ReadWrite.All permission in Azure Active Directory. For Service Principal authentication, verify that the same permission is granted and that the "Service principals can call Fabric public APIs" setting is enabled in the Fabric Admin Portal.
Hope my suggestion gives you good idea, if you have any more questions, please feel free to ask we are here to help you.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you.
Hi v-sgandrathi ,
We have not moved to Fabric mode. Can you provide a sollution without Fabric enabled.
Thank you.
- v-sgandrathi1 year agoCommunity Support
Hi Anonymous,
As you're not using Microsoft Fabric, the issue likely lies in the configuration of the app or user within the classic Power BI setup. First, confirm whether the permission is delegated or application-based, as edit mode typically requires delegated permissions tied to a signed-in user and ensure that admin consent has been granted in Azure Active Directory for the necessary scopes, such as Tenant.ReadWrite.All, Report.ReadWrite.All, and Dataset.ReadWrite.All.
Next, verify that the user or service principal has the correct Power BI workspace access with edit rights and an appropriate role (Admin or Member).
If you're using a service principal, check that it is enabled for API access in the Power BI Admin Portal. For a master user, confirm that it is licensed (Power BI Pro or Premium) and is part of the workspace. Finally, if the setup appears correct, use browser developer tools or Fiddler to inspect the API response for more details, which can indicate the exact permission or configuration that is missing.Thank you.