Forum Discussion
Helper VDataset scheduled refresh fails with odata azure devops source
Well, its an answer, but if acceptable... i don't think so, hence i won't mark any as such.
Super UserUse a Power BI Dataflow instead of connecting directly in the report.
In Power BI Service, go to your workspace.
Click “New” → “Dataflow”.
Choose “Add new tables”, then select OData feed as the source.
Enter your Azure DevOps OData URL (e.g., https://analytics.dev.azure.com/{org}/_odata/v3.0-preview/).
Sign in using OAuth2 (Organizational account).
Select the tables and save the dataflow.
In Power BI Desktop, use “Power BI dataflows” as your source and connect to this data.
Publish the report. Scheduled refresh will now work from the dataflow.
decarsulI'll try create a dataflow, but honestly i do not see how authentication for a dataflow would be different from a dataset. Both are tied to my personal credentials, which seem to require an active AD user.
- BhavinVyas3003
You're right, both use your Azure AD credentials but dataflows handle authentication more reliably in the cloud. Once set up, the dataflow refreshes data independently, and your dataset connects to that refreshed data, avoiding direct login issues with Azure DevOps OData.
- decarsul
Dataflow created and auto refresh set for tonight 5am. Because i don't intend to work for atleast 8 hours prior to that, this should give AD enough time to remove my active session.
Will come back tommorow with the result.