Forum Discussion
New Usage Metrics Report not Refreshing
Hi itsmonique23 ,
The Error DMTS_OAuthTokenRefreshFailedError shows Power BI Service could not refresh the OAuth token for your data source.
AADSTS700003- Device object was not found means The device that Power BI is trying to use for authentication is missing from your tenant’s Azure AD directory. This usually happens if:
- The device was never registered with Azure AD.
- The device object was deleted or became stale.
- Conditional Access or Intune policies require a compliant device, but the object is missing.
You can do some workaround like-
Check Device Registration-
In the Azure portal, go to Azure Active Directory - Devices - All Devices.
Search for the machine that runs the refresh (or the gateway machine if you’re using one).
If it’s missing, re‑register the device.
On Windows- Settings - Accounts - Access work or school -Connect.
Ensure it’s joined to Azure AD or Hybrid AD.
2. Verify Gateway Authentication-
If this dataset uses an On‑Premises Data Gateway, check that the gateway service account is still valid and registered in AAD.
Re‑sign in to the gateway with the correct organizational account.
3. Re‑authenticate the Data Source-
In Power BI Service, go to Settings - Datasets - Data source credentials.
Clear and re‑enter credentials for the usage metrics dataset.
If OAuth is failing, try switching to another supported auth method (e.g., organizational account).
4. Check Conditional Access Policies
If your tenant enforces device compliance policies, the refresh will fail if the device object is missing.
Work with your IT admin to confirm whether Conditional Access is blocking the refresh.
5. Semantic Model Deletion Issue-
Usage metrics reports are system‑generated in Power BI Service. You cannot delete or recreate their semantic model like a normal dataset.
If the system dataset is corrupted, the workaround is to disable and re‑enable usage metrics for the workspace:
Go to the workspace - Settings - Usage metrics - Turn off, then turn back on.
This forces Power BI to regenerate the underlying dataset.
If this replyhelped, mark it as a solution. a kudos would mean a lot! It encourages contributors and keeps the community strong.
Thank You
Sunita
Hello Sunita,
Thanks so much for your reply,
I went into workspace settings but can't find the area to switch on/off the usage metrics report. Any ideas where this may be in workspace settings? Is this something only a higher level admin woudl have access to switch on / off?
Thanks so much appreciate your help a lot
Hi itsmonique23,
Thanks for sharing the screenshot.
From what I can see, there is no Usage Metrics setting available in your workspace settings. In many Fabric workspaces, this option is not shown, so you may not be able to turn Usage Metrics off and on from there.
The error you shared looks more related to authentication in Entra ID (Azure AD) rather than a workspace setting.
Can you please confirm if this issue is happening only with the Usage Metrics report, or are other semantic models in the workspace also having refresh issues?
Also, were there any recent changes to your Entra ID, security policies, or device management around the time the issue started?
Kindly refer to the below documentation links for better understanding:
New Usage Metrics Report not Refreshing - Microsoft Fabric Community
Hope This helps if you have any queries we are happy to assist you further.Regards,
Community Support Team.Hello,
This only seems to be happening with the usage metrics report in one of our workspaces.
Other workspaces - the new usage metrics report seems to be refreshing fine.
Hi itsmonique23,
Thank you for the update.
Since the new Usage Metrics reports in your other workspaces are refreshing correctly, the issue appears to be isolated to this specific workspace.
As a troubleshooting step, could you try opening the Usage Metrics report and selecting Save As to create a copy of the report in the workspace? In some cases, this can help regenerate the connection to the underlying Usage Metrics semantic model.
You can also check whether the affected workspace has had any recent changes to its admins, permissions, or capacity assignment around the time the issue started.
If the issue persists only for this workspace, please continue to monitor it and let us know if you notice any additional error details.
Regards,
Community Support Team.
