Connect to VSTS using the Power BI OData feed


You can access the Analytics Service data through the Power BI Desktop OData feed. This method works for any account that has alternate credentials enabled. OAuth (Organizational Accounts) is currently not supported.

Accessing the VSTS OData feed

  1. Make sure you have installed the VSTS Analytics extension

  2. Make sure you have configured the permissions required to access the Analytics service

  3. To get started, Open Power BI Desktop. If you need to install it, do that now.

  4. Click Get Data from either the welcome page or the Home ribbon.

    Power BI Desktop Get Data

  5. Next, select Other > OData Feed and click Connect.

    Select OData Feed

  6. Enter the URL in the format into a supported browser:


    Select OData Feed

    If the OrganizationName is "foo" then the URL is


    Alternatively, you can enter the URL https://{OrganizationName}{project}/_odata/v1.0-preview which will trim the results by the specified team project across all entities related to that project.

  7. At this point you will be prompted to authenticate against the service. If you have not done so previously, see this topic: Client Authentication Options.

  8. Next, select the entities you want to retrieve data for by checking those entities.


    Do not select any entity with the name Snapshot in it. These entities contain the state of every work item on every day since each work item was created. For repositories of any size this will lead to tens or hundreds of millions of work items which will not load. Snapshot tables are intended only for aggregation queries

    Select the entities of data to retrieve

    At this point, if you click Load, Power BI Desktop will load all of the data in each entity. However, this may be more data than you want. To filter the data, select the entity to filter and click Edit. This brings up the Query Editor. For each column you want to filter on, select it and set your filter. When this is complete click Close & Apply in the upper left corner.

Handle relationships

Understanding the Analytics data model is critical to building good relationships between entities.

By default, when basic data is returned from the Analytics Service, the data is related as shown in the figure below:

Entity relationships

You will note that the Tags, Teams and Users are not related to any of the other data. This is due to how those entities are related. They are related by either many-to-many relationships which are not easily handled in these models or there are multiple relationships between the entities such as between users and work items (they are related by Assigned To, Created By, Changed By, and others).

Multiple relationships can be handled in fairly simply. For example, in the default model you can edit the query, select the AssignedTo column of the WorkItems table and expand the column to include all of the data from the Users table and you can repeat this process for the Created By and Changed By columns as well. This gets you around having multiple links from one table to another which is not allowed.

Another reason for expanding columns in this way is to handle circular relationships which are also not allowed. For example, take the following path: Projects > Areas > Work Items > Projects. This presents a typical circular problem. What if you wanted to see which ares were part of a given project? The model as it is build has relationships between Areas and Work Items and Projects and Work Items but Projects cannot be related to Areas because that completes the circular relationship and so it is not allowed. To handle this, you could expand the Project column in the Areas table. To do that, take the following steps:

  1. Select Edit Queries from the Home tab
  2. Select the Areas query
  3. Scroll to the Project column (the last column) and click the Expand icon at the top of the column

    Areas Query, Project Column

  4. Uncheck all of the columns except for the ProjectName and click OK

    Expand Project options

Now you can list Areas by Project and get a count of Areas in each project.

Feedback and support

We welcome your feedback.

For product related inquiries, review our User Voice page or report a problem at Developer Community. Also, you can get advice on Stack Overflow, or get support via our Support page.

Follow us on Twitter @vsts.