Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I am using Azure DevOps Analytics (OData v3) as a data source in a Power BI Import semantic model.
In Power BI Desktop, refresh works correctly and pulls the latest data.
In Power BI Service, refresh shows "Completed" (manual or scheduled), but the data does not change.
Details:
Data source: Azure DevOps Analytics OData - Boards or WorkItems
Gateway: Not used -cloud source
Authentication: Azure DevOps / Entra ID
Cloud connections are configured correctly
Dataset is Import mode
Power BI Service appears to cache Azure DevOps Analytics results. Refresh completes successfully but does not re-query DevOps.
Adding a dynamic query parameter forces fresh data, but then scheduled refresh is disabled because the source becomes dynamic.
Questions:
1. Is this expected behavior for Azure DevOps Analytics in Power BI Service?
2. Is there a supported way to force Power BI Service to re-query Azure DevOps Analytics without disabling scheduled refresh?
3. Is incremental refresh supported/recommended for Azure DevOps Analytics OData?
Solved! Go to Solution.
Hi @expertpbi ,
Thank you for reaching out to the Microsoft Fabric Community Forum.
What you are seeing is expected behavior when using Azure DevOps Analytics OData in Import mode with the Power BI Service. In the Service, a refresh can complete successfully while still returning cached or delayed results from the Analytics OData endpoint, which can differ from Power BI Desktop behavior.
Currently, there is no supported way to force the Service to fully re-query Azure DevOps Analytics OData, and using dynamic parameters disables scheduled refresh by design. Incremental refresh is also not supported or recommended for this connector. For scenarios that require reliable and timely data updates in the Service, the recommended and supported approach is to use Azure DevOps Analytics Views instead of the raw OData endpoint.
Also thank you @KevinChant for your resposne.
Thank you.
Hi @expertpbi ,
We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.
Thank you.
Hi @expertpbi ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
Hi @expertpbi ,
Thank you for reaching out to the Microsoft Fabric Community Forum.
What you are seeing is expected behavior when using Azure DevOps Analytics OData in Import mode with the Power BI Service. In the Service, a refresh can complete successfully while still returning cached or delayed results from the Analytics OData endpoint, which can differ from Power BI Desktop behavior.
Currently, there is no supported way to force the Service to fully re-query Azure DevOps Analytics OData, and using dynamic parameters disables scheduled refresh by design. Incremental refresh is also not supported or recommended for this connector. For scenarios that require reliable and timely data updates in the Service, the recommended and supported approach is to use Azure DevOps Analytics Views instead of the raw OData endpoint.
Also thank you @KevinChant for your resposne.
Thank you.
Azure DevOps data works fine for me. However, I tend to work with the Analytics Views in Azure DevOps instead of OData.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 56 | |
| 55 | |
| 37 | |
| 18 | |
| 14 |