How to Get Data from Azure DevOps in Power BI

Visualizing your project's progress doesn't have to be a guessing game restricted to built-in dashboards. By connecting Azure DevOps directly to Power BI, you can unlock a world of customizable, in-depth reporting that goes far beyond the defaults. This article will walk you through the process of pulling your Azure DevOps data into Power BI, creating meaningful reports, and gaining a clearer view of your team's performance.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Why Bother Connecting Azure DevOps to Power BI?

You might wonder what the point is when Azure DevOps already has its own Sprints, Dashboards, and Widgets. While those tools are great for day-to-day operations within the platform, they have limitations. Connecting to Power BI elevates your reporting capabilities from simple status checks to powerful strategic analysis.

Here’s why it's worth the effort:

• Fully Customizable Dashboards: Break free from the standard widget formats. In Power BI, you have total control over every chart, graph, and table, allowing you to build reports that answer your specific questions.
• Combine Data from Other Sources: Want to see how your development sprints impact customer support tickets in Zendesk or align with sales goals in Salesforce? Power BI lets you mash up data from dozens of different sources into a single, unified view.
• Advanced Analytics and Trend Analysis: Move beyond just showing the current state of work items. With Power BI, you can easily track historical trends, calculate complex metrics like cycle time volatility, and forecast future work based on past performance.
• Share Reports with Anyone: Sharing insights with stakeholders who aren't active in Azure DevOps is often a challenge. Power BI reports can be easily and securely shared with anyone in your organization, providing a real-time, interactive look at project health without needing a DevOps license.

In short, moving your analysis to Power BI allows you to tell the story behind your data, not just present the numbers.

What You'll Need Before You Start

To ensure a smooth connection process, let's get a few things lined up first. Think of this as your pre-flight checklist.

• Power BI Desktop: You'll need the latest version installed on your computer. It's free to download and use.
• An Azure DevOps Account: You must be a member of an Azure DevOps project with Basic access or higher.
• The Right Permissions: This is a common stumbling block. To view Analytics data, your "View Analytics" permission for the project must be set to Allow. By default, all members of the Contributors group have this permission. For creating certain types of shared views, you might need more elevated permissions.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Connecting Power BI to Azure DevOps: The Main Method

Power BI offers a native connector specifically for Azure DevOps, which is the most straightforward way to get started. This connector gives you two main ways to access your data: through pre-configured Analytics Views or by writing your own OData query.

Let's focus on Analytics Views first, as they are the recommended and most user-friendly approach for most people.

Step 1: Create an Analytics View in Azure DevOps

Before jumping into Power BI, it’s best practice to define the slice of data you want to analyze within Azure DevOps itself. An Analytics View is essentially a pre-built, flattened dataset that simplifies the underlying data model, making it much easier to work with in Power BI. Creating one is easy.

1. Navigate to your Azure DevOps project. In the left-hand navigation, hover over Boards and click on Analytics views.
2. Click the green New View button in the top right.
3. Name Your View: Give it a descriptive name like "Q3 Bugs and User Stories" or "Current Sprint Work."
4. Configure the View: This is where you filter down to exactly what you need.
5. Verify and Save: Click the "Verify" tab to see a preview of your data and the number of records it will load. If it looks correct, click Save.

You'll now see your custom view listed on the Analytics views page. This is the dataset Power BI will connect to.

Step 2: Connect Power BI Desktop to Your Analytics View

With your view ready in Azure DevOps, it's time to pull it into Power BI.

1. Open Power BI Desktop.
2. On the Home tab, click Get Data and select More....
3. In the Get Data window, search for "Azure DevOps". Select Azure DevOps (Boards only) and click Connect. (Note: Use "Azure DevOps Server" if your organization hosts its own server.)
4. You’ll be prompted to enter your Organization and Team Project name. You can find these in the URL of your Azure DevOps project ("dev.azure.com/OrganizationName/ProjectName").
5. Click OK. Power BI will then ask you to sign in. Choose to sign in with your organizational account and authenticate.
6. Once connected, the Navigator window will appear. On the left side, you'll see a folder named "Shared Views." Expand it, and you should find the Analytics View you created in Step 1.
7. Select your view. A preview of the data will appear on the right.
8. From here, you have two options:

Click Transform Data. Once in Power Query, review your columns, then click "Close & Apply" on the Home tab. Your data is ready and running!

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Step 3: Build Your First Report

Now for the fun part! Your Azure DevOps data is loaded into your Power BI model. You can see all the fields from your Analytics View in the "Fields" pane on the right.

Let's create a few simple visuals:

Work Items by State:

Drag the State field onto the canvas. Power BI will automatically create a table. In the "Visualizations" pane, change it to a Pie chart. Then, drag the Work Item ID field into the "Values" box of the pie chart. Set its aggregation to Count. You now have a visual breakdown of your work by its current status.

Work Items per Assignee:

Create a new visual by clicking on an empty part of the canvas. In the Visualizations pane, select a Stacked bar chart. Drag the Assigned To field to the "Y-axis" and the Work Item ID (set to Count) to the "X-axis." This instantly shows you the current workload distribution across your team.

For Advanced Users: Connecting with OData Queries

What if Analytics Views are too limiting? If you need more granular control or want to query different entities (like build pipelines or test results), you can connect directly using an OData feed. This method is more complex and requires a bit of knowledge about the Azure DevOps data model, but it offers ultimate flexibility.

Instead of choosing the Azure DevOps connector in Power BI's Get Data dialog, you would choose OData Feed.

The URL for your feed will follow this format:

https://analytics.dev.azure.com/{YourOrganization}/{YourProject}/_odata/v3.0-preview/

You can then append queries to this URL to pull specific data tables. For example, to get all work items that aren't closed, you could modify your URL to look something like this:

https://analytics.dev.azure.com/{YourOrganization}/_odata/v3.0-preview/WorkItems?$select=WorkItemId,Title,State,AreaSK&$filter=State ne 'Closed'

This approach bypasses Analytics Views entirely, giving you raw access to the data but also putting the responsibility on you to shape it correctly into a usable model.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Practical Tips for Better Azure DevOps Reports

Connecting is just the first step. Here are a few tips to level up your reports.

• Keep Your Data Model Clean: Your Analytics Views can get bloated with fields you never use. Go back and edit your view in Azure DevOps to remove unnecessary columns. A slimmer data model is faster and easier to manage in Power BI.
• Start with a Question: Don't just build charts for the sake of it. Start with a specific business question, like "Is our sprint velocity improving?" or "Where are our biggest bottlenecks?" and build your report to answer that question.
• Publish and Schedule Refresh: Don't keep your report stuck on your desktop. Publish it to the Power BI Service (your organization's online Power BI workspace). Once there, you can set up a scheduled refresh so your data automatically updates every day without you having to lift a finger. This delivers true, real-time insights to your team.

Final Thoughts

Connecting Azure DevOps to Power BI transforms your project data from a static list of tasks into a dynamic, interactive dashboard for strategic decision-making. By leveraging Analytics Views and the intuitive Power BI interface, you can build powerful reports that highlight trends, expose risks, and provide clarity to your entire organization.

As you become more comfortable with your DevOps data, you'll start to realize that it's just one piece of the puzzle. We built Graphed because we know that true business insight comes from connecting multiple systems, not just one. Instead of manually pulling data from Shopify, Google Analytics, and Salesforce to see the full picture alongside your development work, our AI analyst does it for you. You can simply connect your sources and ask questions in plain English like, "show me a breakdown of features shipped this month vs new paying customers," and get an instant, real-time dashboard that answers your question in seconds.