Forum Discussion
Microsoft 365 Usage Analytics App broken
Hello all,
I am using the Microsoft 365 App Usage Analytics template/app in Power BI Service. Since a few days ago, all scheduled refreshes are failing with the following error:
DataSource.Error: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 3, Error: The remote server returned an error: (500) Internal Server Error. Microsoft.Data.Mashup.ErrorCode = 10122.
The issue also occurs in Power BI Desktop after downloading the PBIX file. All tables fail to refresh, not just a single query.
Affected source:
https://reports.office.com/pbi/v1.0/...
One example table:
ODBActive-Sites/Users/Docs
I already tried:
clearing and recreating data source credentials
re-authenticating with Organizational Account
downloading the latest template/app version
testing from different machines/accounts
Same result everywhere.
Additionally, opening https://reports.office.com directly in the browser only returns:
<Error> <Message>An error has occurred.</Message> </Error>
Is anyone else seeing this issue?
Has Microsoft deprecated or broken the old reports.office.com OData endpoint used by the Microsoft 365 App Usage Analytics app? What are customers supposed to do now?
Best regards
Pikachu-Power
Hey Pikachu-Power,
Interesting alias you got there 😁.
On the internet, multiple users have reported the same error. A very similar issue thread exists here:
https://community.fabric.microsoft.com/t5/Issues/Template-App-quot-Microsoft-365-Usage-Analytics-quot-failing/idi-p/5180513There is also a Reddit discussion where a user said that Microsoft acknowledged it as a service-side issue, and scheduled to be resolved by coming Tuesday (5/19):
https://www.reddit.com/r/PowerBI/comments/1t5xp3m/m365_usage_report_refresh_error/It seems to be widespread, affecting multiple users. I could not find an official deprecation notice yet for the reports.office.com OData endpoint, but Microsoft does appear to be gradually moving reporting scenarios toward Microsoft Graph reporting APIs.
Hope it helps a bit!
Best,
Harshit
4 Replies
Since today, it’s working again. It seems to have been a temporary issue that lasted longer. Thanks, everyone.
Sounds good. Thanks for sharing.
Best,
Harshit
Hey Pikachu-Power,
Interesting alias you got there 😁.
On the internet, multiple users have reported the same error. A very similar issue thread exists here:
https://community.fabric.microsoft.com/t5/Issues/Template-App-quot-Microsoft-365-Usage-Analytics-quot-failing/idi-p/5180513There is also a Reddit discussion where a user said that Microsoft acknowledged it as a service-side issue, and scheduled to be resolved by coming Tuesday (5/19):
https://www.reddit.com/r/PowerBI/comments/1t5xp3m/m365_usage_report_refresh_error/It seems to be widespread, affecting multiple users. I could not find an official deprecation notice yet for the reports.office.com OData endpoint, but Microsoft does appear to be gradually moving reporting scenarios toward Microsoft Graph reporting APIs.
Hope it helps a bit!
Best,
Harshit
HI Pikachu-Power ,
Thank you for reaching out to Community Forum.Microsoft Graph reporting APIs are the officially documented way to programmatically access Microsoft 365 usage data, according to Microsoft Learn documentation.
At this time, there is no publicly documented deprecation notice for the reports.office.com endpoint. However, Microsoft continues to invest in Microsoft Graph for reporting scenarios.
Since the endpoint itself is returning a (500) Internal Server Error across different environments, the issue may be service-related rather than caused by local configuration or credentials. It would be recommended to check the Microsoft 365 Service Health dashboard or contact Microsoft Support for confirmation if the issue continues.
Thank you.
