During the continued development of CCO Insights, we have been able to identify and fix several bugs or product limitations and we would like to encourage you to read this document before starting to leverage the solution.
-
Which Power BI Desktop version I should use? (Microsoft Store or Web Download)
-
Power BI Regional Settings (Maps Visualizations incorrectly locate resources or VNET peerings)
-
Management Groups - Access to the resource is forbidden error
-
Log Analytics REST API timeout (CCO AKS dashboard add-on only)
We will keep updating this list of known issues as soon as we get more feedback from the community.
Based on our experience we highly recommend to use the Power BI Desktop version from the Microsoft Store to get automatic updates. The following article explains the main difference between both options. https://docs.microsoft.com/en-us/power-bi/desktop-get-the-desktop
Make sure that you don't have both versions installed on the computer where you plan to use CCO Insights.
It might happen then when you run the Dashboard using different regional settings some coordinates are not calculated properly. CCO Insights' development has been based on English US regional settings. Make sure that you set the Regional Settings to use English (United States) on the application language on both Global and Current File options. If the current file has a different configuration you will need to change to English US, export the file as template again, and then open it from your computer
During the first use of the CCO Insights templates you should be prompted to enter the credentials for both the Azure Management REST API and the GRAPH REST API. You might get the error message from below if you incorrectly enter your credentials. Also, in some cases, during the first run, Power BI will not ask for credentials because they are already cached by a previous use of another Power BI Dashboard accessing the same APIs.
If that happens you will need to manually set the proper credentials for the GRAPH REST API Data Source. To do this you must follow this steps:
- Go to File.
- Click on Options and settings.
- Click on Data source settings.
- In in Current file/Global permissions select https://graph.windows.net and click on Edit permissions.
- Click on Edit and enter your credentials.
Another credentials issue we identified during our pilots is that in some cases the end user didn't setup the Privacy levels correctly getting the following error
This is an example of a wrong Privacy Levels configuration across Data Sources. Makes sure that you set both Data Sources to Organizational
Every time you run the Dashboard from the .pbit template you will be asked to enter the Tenant parameter. This parameter is critical to properly get your RBAC information. If this parameter is entered incorrectly but the tenant exists it will load the Dashboard information with blank information on the RBAC page or the Subscriptions Owners visualization on the Overview page
Management Groups in Azure is a relatively new capability and some users reported the following error when loading the Dashboard for the first time. The reason behind that error can be the lack of permissions but also because there is no Management Groups definition.
If that is the case and you are still not using Management Groups in your environment you can simply open the Query Editor, browse to the Management Groups query on the left side panel and disable the query. You will need to refresh all the data once this change is applied.
Depending on the number of records we have in log analytics, we can obtain a timeout during the refresh.
The solution is to wait a few minutes and launch a new refresh.
In some occasions when having both Power BI Desktop versions installed on the computer we have seen the Data Relationship model to disappear. If that happens you can use the following reference to manually reconfigure the relationship between tables. It should also help you to understand how we defined the Data Model in case you want to expand the default content
Governance:
Infrastructure:
Try using a native user account to the AAD tenant you are connecting to instead of a guest user account.