| title | titleSuffix | description | ms.assetid | ms.subservice | ms.author | author | ms.topic | monikerRange | ms date |
|---|---|---|---|---|---|---|---|---|---|
Connect to Power BI Data Connector |
Azure DevOps |
Learn how to connect to Power BI Data Connector and Analytics to access Azure DevOps data. |
509ECCF2-E18E-4F14-B7EE-8802AB8938A2 |
azure-devops-analytics |
chcomley |
chcomley |
how-to |
>= azure-devops-2019 |
10/04/2021 |
[!INCLUDE version-gt-eq-2019]
In this article, you learn how to establish a seamless connection between Power BI and Azure DevOps by using Data Connector. This integration allows you to extract valuable insights from your Azure DevOps data and create compelling reports within Power BI. Power BI Data Connector uses Analytics views.
[!INCLUDE temp]
::: moniker range="azure-devops"
- Get familiar with What is Analytics and the knowledge base of Power BI articles.
- Install the Power BI Desktop October 2018 Update or a newer version.
- Ensure that you're added as a project member. If you aren't, get added now. Anyone with access to the project, except stakeholders, can view Analytics views.
- Ensure that Boards is enabled. If not, Analytics views doesn't appear. To reenable Boards, see Turn an Azure DevOps service on or off.
- Ensure that you have permissions required to access Analytics. If you're a member of the project Contributors group, you have permission.
- Create an Analytics view that you want to create a Power BI report.
::: moniker-end
::: moniker range="< azure-devops"
- Get familiar with What is Analytics and the knowledge base of Power BI articles.
- Install the Power BI Desktop October 2018 Update or a newer version.
- Ensure that you're a member of a project with Basic access or higher. If you don't have a project yet, create one.
- Ensure that you're added as a project member. If you aren't, get added now. Anyone with access to the project, except stakeholders, can view Analytics views.
- Verify that Analytics is installed, and if not, then enable it. You must be an account owner or a member of the Project Collection Administrators group to add extensions or enable the service.
- Ensure that Boards is enabled. If not, Analytics views doesn't appear. To reenable Boards, see Turn an Azure DevOps service on or off.
- Ensure that you have permissions required to access Analytics. If you're a member of the project Contributors group, you have permission.
- Create an Analytics view for which you want to create a Power BI report.
::: moniker-end
[!INCLUDE alt-creds-deprecation-notice]
[!INCLUDE temp]
Create reports based on the loaded data. After the load operation finishes, you can explore the data by creating custom reports. For examples of common reports, see Data Connector - Example reports.
:::image type="content" source="media/data-connector-visual.png" alt-text="Screenshot that shows the Power BI Desktop report view.":::
Find answers to common questions about Power BI Data Connector and Analytics error messages.
A: You might feel challenged reading error messages coming from the connector because they typically contain extra contextual information. If the load operation fails, then the message starts with "Failed to save modifications to the server...". When you see it, search for [DataSource.Error] Azure DevOps...:. The following example shows the error message returned from the connector. The most important part of the error message is "Query result exceeds maximum size. Reduce the number of records by applying additional filters."
:::image type="content" source="media/QueryExceedsPreferredMaxSizeException.png" alt-text="Screenshot that shows the Query result exceeds maximum size error message.":::
Q: How do I resolve the "Query result exceeds maximum size. Reduce the number of records by applying additional filters" error?
A: You get the following error if the number of records retrieved from Analytics exceeds 250,000:
"Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: [DataSource.Error] VSTS: Request failed: The remote server returned an error: (400) Bad Request. (Query result exceeds maximum size. Please reduce the number of records by applying additional filters).'"
This error typically occurs when your project has a large number of work items. Reduce the size of the dataset by customizing the view. Do this step before you use it in Power BI.
:::image type="content" source="media/QueryExceedsPreferredMaxSizeException.png" alt-text="Screenshot that shows the Query result exceeds maximum size error.":::
A: You might get this error if you try to access a project that you don't have permissions to. You might also see it if Power BI doesn't recognize your credentials. To check your permissions, see Set permissions to access Analytics and Analytics views. If it's a credential issue, work with your administrator to see if they can help resolve the problem. For more information, see Power BI security, user authentication and Troubleshooting sign-in issues for Power BI.
:::image type="content" source="media/AccessDeniedError.png" alt-text="Screenshot that shows the access-denied error.":::
Note
Power BI uses Microsoft Entra ID to authenticate users who sign in to the Power BI service, and in turn, uses the Power BI sign-in credentials whenever a user attempts to access resources that require authentication. Users sign in to the Power BI service by using the email address used to establish their Power BI account. Power BI uses that sign-in email as the effective username, which is passed to resources whenever a user attempts to connect to data. The effective username is then mapped to a user principal name and resolved to the associated Windows domain account, against which authentication is applied.
A: You might get this error if you have access to a specific project but you don't have the View analytics permissions. Work with your project administrator to get these permissions. For more information about the security model, see Analytics security.
:::image type="content" source="media/AnalyticsAccessCheckException.png" alt-text="Screenshot that shows the error message Access to the resource is forbidden.":::
Q: How do I resolve the "Project 'X' does not exist or you do not have permissions to access it" error?
A: This error indicates that the value you entered for Project name doesn't correspond to any project. A common mistake that users make is to confuse the project name with a team name.
For example, if the URL you use is https://dev.azure.com/fabrikam-fiber-inc/Fabrikam-Fiber-Git/Device, then Fabrikam-Fiber-Git is the project name and it should be used in the parameter. Device is the team name.
