Forum Discussion
Permissions required for OData access projects
Hi Frede ,
If you are querying multiple projects, you should limit the query to the projects you have access to. Also, specify the project filter in the $expand clause if your expansion could include data in other, potentially inaccessible projects.
OData Analytics query guidelines - Azure DevOps | Microsoft LearnIt’s crucial to ensure that the appropriate permissions are set correctly to maintain the security and integrity of your data. Always follow your organization’s guidelines when requesting additional permissions.
About permissions and security groups - Azure DevOps | Microsoft Learn
Best Regards,
Gao
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!How to get your questions answered quickly -- How to provide sample data in the Power BI Forum -- China Power BI User Group
I forgot to mention that I do have permissions to all projects that I include in my filter statement and they do not have links to projects to which I do not have access. If there was a permission issue I would expect to have issues when including the projectname in the OData query like this, but there is not and that works OK, it's just when omitting the project name that it does not work.
= OData.Feed("https://servername/{organization}/{project}/_odata/v4.0-preview/WorkItems?" &