Forum Discussion
Helper IIPower BI + Azure DevOps OData — how to avoid 403 “Access to the resource is forbidden” when new proj
Hi syl-ade,
Based on the issue here there is no way for Analytics OData to automatically skip projects you do not have access to. When you use the organisation-level Analytics OData endpoint, azure devops first enumerates all projects and even if one project returns a 403, the entire feed fails at that point.
- Because of that, the only possible options are granting the power bi identity read access to all projects or using project scoped analytics endpoints. This is a limitation of the Azure DevOps Analytics service, not power bi.
Thanks and regards,
Anjan Kumar Chippa
- Because of that, the only possible options are granting the power bi identity read access to all projects or using project scoped analytics endpoints. This is a limitation of the Azure DevOps Analytics service, not power bi.
Super UserSome Power Query connectors (namely Web.Content) allow manual http error handling.
Handling status codes with Web.Contents for Power Query connectors - Power Query | Microsoft Learn
Helper IIHi lbendlin ,
How do you think I could use it in this case?
Whenever there is a new project, I lose access to all data in Azure DevOps. How this would handle 403 error?
- v-achippa
Community Support
Hi syl-ade,
Based on the issue here there is no way for Analytics OData to automatically skip projects you do not have access to. When you use the organisation-level Analytics OData endpoint, azure devops first enumerates all projects and even if one project returns a 403, the entire feed fails at that point.
- Because of that, the only possible options are granting the power bi identity read access to all projects or using project scoped analytics endpoints. This is a limitation of the Azure DevOps Analytics service, not power bi.
Thanks and regards,
Anjan Kumar Chippa
- Because of that, the only possible options are granting the power bi identity read access to all projects or using project scoped analytics endpoints. This is a limitation of the Azure DevOps Analytics service, not power bi.