Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
twiek
Frequent Visitor

Feature usage and adoption not working

Hi everyone,

 

I did not find any info on my particular problem so I hope you can support me. About 2 weeks ago I found out about PowerBIs Admin Monitoring feature and its standard Dataset + Report called "Feature usage and adoption". However this never worked the whole time and I get the following two messages I can't handle:

 

1)

twiek_1-1713173109695.png

Details:

 

twiek_0-1713173084438.png

2)

twiek_2-1713173145889.png

 

Details:

twiek_3-1713173168512.png

Since this is an automatically generated Report / Dataset and there are no specific options available I have no Idea what is going on here and how I can handle this.

 

FYI: I do have a Datagateway running on a server which works perfectly fine for all custom datasets. But this shouldn't have any effect on this issue since this report does not need any access to my local files?!

 

Please help,

Thanks,

Max

1 ACCEPTED SOLUTION

Hi @twiek 

 

We finally figured it out... there's a section in the documentation that talks about reinitializing the admin workspace.

 

These were the steps we took to finally fix the app:

  • Logged into Fabric
  • Navigated to the Admin Monitoring workspace
  • Captured the Workspace Id

jeremycolson1_0-1730145319560.png

  • Opened up developer tools in the browser, navigated to the network tab, and filtered on Fetch/XHR. Then refreshed the page so we could grab the bearer token (it's a short-cut we use to get a bearer token when using something like Postman). Any fetch request should have the bearer token in the headers... so just pick one (in the image here I picked base), and then on the right, under "Headers" you can scroll down to find the bearer token under authorization.

jeremycolson1_1-1730145441552.png

  • Then we used postman to make a DELETE call to the endpoint from the Microsoft article using the Workspace Id and bearer token (just toss the bearer token under Authorization). I'm not sure how familiar you are with Postman, but if you have any questions just let me know. You should get a 200 back if the delete is successful.

jeremycolson1_3-1730146153389.png

 

jeremycolson1_4-1730146509612.png

 

  • Went back to the browser and refreshed the page... It basically reinstalls the admin workspace apps. Then it will refresh the underlying semantic models. And in about 15 minutes our usage app started working again.

 

No idea why Microsoft has made this such a convoluted process. The fact someone has to use the underlying APIs to fix their broken apps is just absurd IMO. Great job w/ the usability there Microsoft.

 

Hope this helps. If you have any questions or run into any problems just let me know.

View solution in original post

7 REPLIES 7
twiek
Frequent Visitor

Hi johnbasha33 and thanks for your answer. However I can't check any of your first 3 suggestions properly as there is no possibility to access any kind of settings of this particular dataset. Settings as known from other datasets like gateway connections / data connections in general do simply not exist for this feature.

 

1) I can only see the last refresh, I can't find a history

2) If I could see anywhere which connections are necessary I could do that

3) The gateway definitley works for all other reports

 

Maybe I just can't find the settings and you can help me there? Or anybody has had a similar problem?

Thanks

Hi @twiek  - did you find a solution for this? We have run into the same problems and like you noted, access is so restricted to this workspace we cannot do anything to diagnose or attempt to resolve.

Hi, unfortunately I did not resolve this and I couldn't find any solution on the web or AI... I am still interested in a solution.

Hi @twiek 

 

We finally figured it out... there's a section in the documentation that talks about reinitializing the admin workspace.

 

These were the steps we took to finally fix the app:

  • Logged into Fabric
  • Navigated to the Admin Monitoring workspace
  • Captured the Workspace Id

jeremycolson1_0-1730145319560.png

  • Opened up developer tools in the browser, navigated to the network tab, and filtered on Fetch/XHR. Then refreshed the page so we could grab the bearer token (it's a short-cut we use to get a bearer token when using something like Postman). Any fetch request should have the bearer token in the headers... so just pick one (in the image here I picked base), and then on the right, under "Headers" you can scroll down to find the bearer token under authorization.

jeremycolson1_1-1730145441552.png

  • Then we used postman to make a DELETE call to the endpoint from the Microsoft article using the Workspace Id and bearer token (just toss the bearer token under Authorization). I'm not sure how familiar you are with Postman, but if you have any questions just let me know. You should get a 200 back if the delete is successful.

jeremycolson1_3-1730146153389.png

 

jeremycolson1_4-1730146509612.png

 

  • Went back to the browser and refreshed the page... It basically reinstalls the admin workspace apps. Then it will refresh the underlying semantic models. And in about 15 minutes our usage app started working again.

 

No idea why Microsoft has made this such a convoluted process. The fact someone has to use the underlying APIs to fix their broken apps is just absurd IMO. Great job w/ the usability there Microsoft.

 

Hope this helps. If you have any questions or run into any problems just let me know.

@jeremycolson1Wow that looks promising. I did everything as you described it and now a new Admin Workspace has been generated and it looks like it is gonna work. Thank you very much!

Glad it worked and happy to help!

johnbasha33
Super User
Super User

@twiek 

It appears that you're encountering issues with the Power BI Admin Monitoring feature and the associated "Feature usage and adoption" dataset and report. The errors you're seeing suggest that there might be a problem with the data refresh process for this particular dataset.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

1. **Check Dataset Refresh History**: Navigate to the dataset settings in the Power BI service and review the refresh history for the "Feature usage and adoption" dataset. Look for any failed refresh attempts and examine the error messages to identify the underlying cause.

2. **Review Data Source Connections**: Although the "Feature usage and adoption" dataset is a standard Power BI dataset, it still relies on underlying data sources for its data. Ensure that any required data source connections, such as Azure Activity Logs or Office 365 usage reports, are properly configured and accessible.

3. **Check Gateway Configuration**: While the "Feature usage and adoption" dataset primarily relies on cloud-based data sources, it's possible that there may be some dependencies or configurations related to on-premises data gateways. Verify that your data gateway is running and properly configured, even though it shouldn't directly affect this particular dataset.

4. **Contact Support**: If you're unable to resolve the issue through the above steps, consider reaching out to Microsoft Support for assistance. They can provide further guidance and investigate any potential issues with the dataset refresh process.

5. **Community Forums**: You can also post your issue on the Power BI Community forums to see if other users have encountered similar problems and to seek advice from the broader Power BI community.

By following these steps and investigating the potential causes of the dataset refresh errors, you should be able to identify and address the issue with the "Feature usage and adoption" dataset and report.

Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

Jan NL Carousel

Fabric Community Update - January 2025

Find out what's new and trending in the Fabric community.