Usage Metrics Report Takeover

[AnandGNR]

Hi All,

I recently took over ownership of a Usage Metrics report and its semantic model (Early July, 25) in Power BI Service, originally created by a former employee who left at the end of June, 25.

Following Microsoft’s documentation

https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-modern-usage-metrics#update-usa...

I attempted to update the credentials. However, I’m encountering issues — I’m unable to authenticate, and it throws an error related to OAuth not being supported for this data source (see below).

As a Power BI tenant admin, and given that the report was working correctly until the employee’s exit, I’m confident that this is not due to a tenant-level config change.

My Error

What are next steps to get this to work? Has anyone had a similar experience?

[AnandGNR]

Hi All, 

Thanks a lot for the comments! Really helpful. 

@WishAskedSooner: It does appear to be a bug.I tested for a sample report  in a dev workspace and looked at the model configs and it refreshed for my creds with OAuth. So this issue seems to be related to the takeover process for existing reports as detailed by @Deku / @v-menakakota.

 @v-menakakota : Is there a way to determine which reports were selected when the original metrics report was created when using multiple reports?

The way the documentation puts it, a particular report " Retail Analysis Sample" is selected to create the report.

https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-modern-usage-metrics#create-and...

Snip below for my usecase:

1. How is the report created for multiple selections?

2. Is there a way to determine the selections in the existing model?

[v-menakakota]

Hi @AnandGNR ,

Thanks for the update,it does seem like the issue is specifically tied to the ownership change especially in cases where the usage metrics report was originally created using multiple report selections.

From what I’ve seen, Power BI doesn’t actually keep a record of which reports were selected when the metrics model was first generated. That detail isn’t exposed in the UI or stored in a way we can easily retrieve later.

At this point, the cleanest and most reliable approach would be to recreate the usage metrics report by reselecting the intended reports. This ensures the new report and dataset are fully connected to your credentials and avoids the OAuth issue going forward.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.   

Best Regards, 
Community Support Team  

[v-menakakota]

Hi @AnandGNR ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

Thank you,

[AnandGNR]

Hi @v-menakakota : I have a few updates since.

1. I was trying to detemine if I could figure out the multiple reports used on the current report by looking at the datamodel this while to proceed with a delete and rebuild report approach.

2. But suddently as of now,  it allowed me to take over the data credentials from the previous user (as per the documentation) without triggering the OAuth2 error I initially faced (screenshot shared in my earlier post) for no apparent reason.(confirming bug behavior) 

3. Since it now takes my credentials without error: how can I resume scheduled refresh:

Per the MS doc section:https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-modern-usage-metrics#usage-metr...

Thanks,

Anand

[v-menakakota]

Hi  @AnandGNR  ,

Thank you for the update  and  you were finally able to take over the data credentials without hitting the OAuth2 error That does seem to support the possibility of some intermittent behavior or a backend issue during the ownership transition.

Go to the workspace where the Usage Metrics Report dataset (semantic model) resides. Under the Datasets or Semantic Models section, locate the Usage Metrics Report. Click the Settings icon next to it. In the Data source credentials section. Make sure your credentials are showing as valid.

Scroll down to Scheduled refresh. Toggle it on. Set the preferred refresh frequency. Click Apply or Save.

Since the usage metrics semantic model is still in preview, there may be occasional schema updates that could affect custom reports built on top of it.

 

If I misunderstand your needs or you still have problems on it, please feel free to let us know.   

Best Regards, 
Community Support Team  

[v-menakakota]

Hi @AnandGNR ,

I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

Thank you.

[AnandGNR · Accepted solution]

HI @v-menakakota : This model does not have a manually configurable refresh option. I did it using APIs.

Thanks,

Anand

[v-menakakota]

Hi @AnandGNR   ,
Thanks for reaching out to the Microsoft fabric community forum. 

This kind of issue often happens when the original owner of the Usage Metrics report leaves the organization. Since the dataset is linked to their account, it stops working once that account is removed. And because OAuth isn’t supported for this type of connection, you won’t be able to just update the credentials.

As mentioned by @Deku   to fix this is to delete the existing report and create a new one. You can do that by going to the workspace and clicking View usage metrics report this will generate a fresh version that’s connected to your account.

Regards,
Community Support Team.

[Deku]

You will likely need to delete the report and model and recreate it again

[WishAskedSooner]

Oh, wow! I was looking through this forum for a similar issue as well. That is a very less than ideal solution.

Did they use a Gateway Personal mode, or Standard mode?