This guide provides an alternative to our manual workflow for exporting tickets from ADO. Instead, you can export your data using a a Power BI query that pulls work items across all projects in your Azure DevOps organization in a single shot, filtered to the date window Neo.Tax expects, and produces a CSV with column names that match Neo.Tax's expected format.

Once set up, the annual refresh is a one-line change (the tax year) followed by Refresh → Export to CSV.


How it works

Note on "Tree of work items": the original instructions use that query type to preserve parent → child hierarchy. In OData, every work item carries its ParentWorkItemId, which gives Neo.Tax the same hierarchy information as a column. No tree query needed.


Prerequisites

  1. Power BI Desktop installed (free download from Microsoft).
  2. Azure DevOps account with read access to all projects you want included. The query will only return data for projects the authenticated user can see.
  3. Analytics extension enabled in your ADO organization. It's enabled by default in modern ADO; if your org disabled it, an org admin needs to re-enable it under Organization Settings → Extensions.
  4. Your organization name—the slug from your ADO URL: https://dev.azure.com/{Organization}.

Step 1: Create a blank query

  1. Open Power BI Desktop.
  2. Home → Get Data → Blank Query.
  3. The Power Query Editor opens. In the left panel, right-click Query1Rename → call it WorkItems.