Connecting Power BI Desktop to Azure DevOps Analytics views with the OData Feed connector
You plan to use Power BI Desktop to create a bug tracking dashboard that will pull data from Analytics in Azure DevOps. From Power BI Desktop, you need to configure a data connector to authenticate to Azure DevOps. The solution must meet the following requirements: • Use Analytics views. • Filter data from the cloud. Which connector should you use?
Community Votes
51% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Analytics views expose their data as an OData endpoint, and the official walkthrough for consuming them is Get Data > OData Feed with the view's analytics URL — filtering defined in the view is applied in the cloud before data reaches the model.
A bug tracking dashboard must consume Azure DevOps Analytics views from the cloud with server-side filtering, so Power BI Desktop must be pointed at the connector that reads those views directly.
Picking the Azure DevOps (Boards only) connector because it appears in general Azure DevOps reporting docs — that connector builds queries against Boards data directly and is not the path the official Analytics views documentation prescribes; 'OData queries' is not a real Power BI connector name.
Community Discussion (41 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Analytics views expose data through OData feeds, and Microsoft's documentation for accessing Analytics data with Power BI explicitly instructs you to use the OData feed connector in Power BI Desktop, pasting the view's analytics endpoint URL. Because the view itself performs the filtering server-side, data is filtered from the cloud before it is loaded into the model, exactly as the requirement states. The OData Feed connector (D) is the only listed option that consumes those views in this prescribed way.Why the Other Options Are Wrong
OData queries (A) is not the name of any Power BI connector, so it is a distractor built to look plausible. Azure DevOps (Boards only) (B) is a real connector designed for querying Boards work item data directly; it does not consume user-defined Analytics views and is aimed at the scenario where you build the query inside Power BI rather than use a pre-filtered view. Azure DevOps Server (Boards only) (C) targets an on-premises deployment, which contradicts the requirement to filter data from the cloud.Community Comment Notes
The most-endorsed comment defends option B by quoting the Azure DevOps connector documentation for cloud services, but that page describes connecting directly to Boards data, not to Analytics views. Another highly voted comment explains that Analytics views expose data through OData feeds, which is the reasoning behind D and matches the official Analytics views walkthrough.Official Reference
Exam Strategy
When a scenario mentions Analytics views or filtering a large dataset server-side before load, immediately look for the OData Feed connector and skip any option containing "Boards only". That suffix is the trap keyword: those connectors query work items directly and never consume Analytics views. Also discard option names that are not real Power BI connectors at all, such as OData queries.
Frequently Asked Questions
Does the Azure DevOps (Boards only) connector work with Analytics views in Power BI?
No. It queries Boards work item data directly and cannot consume user-defined Analytics views, which is exactly why the OData Feed connector (D) is required here.
Why is OData queries (A) not the right choice for Azure DevOps Analytics views?
OData queries is not an actual Power BI connector name, so it is a purpose-built distractor. Analytics views are only consumed through the OData Feed connector.
Why is Azure DevOps Server (Boards only) wrong for this dashboard?
It targets an on-premises Azure DevOps Server deployment, which contradicts the requirement to filter data from the cloud.
Related Analysis
Practice All PL-300 Questions
Access 116 questions with complete answers and detailed explanations.
View Full PL-300 Practice Test →