Forum Discussion
Connect to your data with Usage Analytics
That error basically means Power BI expected an OData/JSON response, but the URL it’s calling is returning an HTML page instead. In this Microsoft 365 Usage Analytics flow, that almost always happens when the request gets redirected to a sign-in page, blocked/denied, or you’re not actually subscribed/ready for the Usage Analytics dataset yet, so the service returns an HTML message page rather than the OData payload.
If your org uses Conditional Access or MFA, that can also lead to HTML being returned to the connector. This is why the account you are using needs to have the Usage Summary Reports Reader role. Also because of the least privileged roles by task principle you should apply.
Hi pt3thanh285, it could be that your usage analytics is still not ready. Check the page Enable Microsoft 365 usage analytics where you can read that it can take up to 48 hours depending on the size of your tenant. The Go to Power BI button is enabled (no longer gray) when data collection is complete.
And, you need to make sure your account has the required admin/reader roles for Usage Analytics. This would the Usage Summary Reports Reader role. The role should permantly assigned to your account to be able to schedule the semantic model refresh.
Hope this helps. If so, please give kudos 👍 and mark as Accepted Solution ✔️ to help others.
it is def not the case. I activated the report feature a week ago. Also the account has admin role. Doesn't affect anything. Also its not what the error was about
That error basically means Power BI expected an OData/JSON response, but the URL it’s calling is returning an HTML page instead. In this Microsoft 365 Usage Analytics flow, that almost always happens when the request gets redirected to a sign-in page, blocked/denied, or you’re not actually subscribed/ready for the Usage Analytics dataset yet, so the service returns an HTML message page rather than the OData payload.
If your org uses Conditional Access or MFA, that can also lead to HTML being returned to the connector. This is why the account you are using needs to have the Usage Summary Reports Reader role. Also because of the least privileged roles by task principle you should apply.
