Skip to content

Commit 2525040

Browse files
Merge pull request #267674 from davidsmatlak/ds-ah-powerbi-tsg-20240228
Updates ARG troubleshooting guide
2 parents 1e0b62d + 6f78eef commit 2525040

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

articles/governance/resource-graph/troubleshoot/power-bi-connector.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Azure Resource Graph Power BI connector
33
description: Learn how to troubleshoot issues with Azure Resource Graph Power BI connector.
4-
ms.date: 02/22/2024
4+
ms.date: 02/28/2024
55
ms.topic: troubleshooting
66
---
77

@@ -32,18 +32,16 @@ ARG Power BI connector isn't available in the following products:
3232

3333
The ARG Power BI connector only supports [import connections](/power-bi/connect-data/desktop-directquery-about#import-connections). The ARG Power BI connector doesn't support `DirectQuery` connections. For more information about connectivity modes and their differences, go to [DirectQuery in Power BI](/power-bi/connect-data/desktop-directquery-about).
3434

35-
## Load times and throttling
35+
## Load times
3636

37-
The load time for ARG queries in Power BI is contingent on the query size. Larger query results might lead to extended load times.
38-
39-
If you're experiencing a 429 error, which is due to throttling, go to [Guidance for throttled requests in Azure Resource Graph](../concepts/guidance-for-throttled-requests.md).
37+
The load time for ARG queries in Power BI is contingent on the query response size. Larger query results might lead to extended load times.
4038

4139
## Unexpected Results
4240

4341
If your query yields unexpected or inaccurate results, consider the following scenarios:
4442

45-
- **Verify permissions**: Confirm that your [Azure role-based access control (Azure RBAC) permissions](../../../role-based-access-control/overview.md) are accurate. Ensure you have at least read access to the resources you want to query. Queries don't return results without adequate permissions to the Azure object or object group.
46-
- **Check for comments**: Review your query and remove any comments (`//`) because Power BI doesn't support Kusto comments. Comments might affect your query results.
43+
- **Verify permissions**: Confirm that your [Azure role-based access control (Azure RBAC) permissions](../../../role-based-access-control/overview.md) are accurate, as the results of the queries are subject to Azure RBAC. Ensure you have at least read access to the resources you want to query. Queries don't return results without adequate permissions to the Azure object or object group.
44+
- **Check for comments**: Review your query and remove any comments (`//`) because Power BI doesn't support Kusto comments.
4745
- **Compare results**: For parity checks, run your query in both the ARG Explorer in Azure portal and the ARG Power BI connector. Compare the results obtained from both platforms for consistency.
4846

4947
## Errors
@@ -57,6 +55,6 @@ The following table contains descriptions of common ARG Power BI connector error
5755
| Error | Description |
5856
| ---- | ---- |
5957
| Invalid query | Query that was entered isn't valid. Check the syntax of your query and refer to the ARG [Kusto Query Language (KQL)](../concepts/query-language.md#supported-kql-language-elements) for guidance. |
60-
| Scope check | If you're querying at the tenant scope, delete all inputs in the subscription ID or management group ID fields. <br> <br> If you have inputs in the subscriptions ID or management group ID fields that you want to filter for, select either subscription or management group from the drop-down scope field. |
58+
| Scope check | If you're querying at the tenant scope, ensure the subscription ID and management group ID fields are empty. <br> <br> If you have inputs in the subscriptions ID or management group ID fields that you want to filter for, select either subscription or management group from the drop-down scope field. |
6159
| Scope subscription mismatch | The subscription scope was selected from the scope drop-down field but a management group ID was entered. |
6260
| Scope management group mismatch | The management group scope was selected from the scope drop-down field but a subscription ID was entered. |

0 commit comments

Comments
 (0)