Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
We're using Power BI to visualize data from Azure Log Analytics (using the M query export feature in Log Analytics). The workspace we are using is set to keep 62 days of data. When I query the data in Log Analytics, I see data up to 62 days old.
However, in Power BI, I am only getting 31 days worth of data.
I have even updated my query to include:
| where TimeGenerated > ago(62d)
This doesn't do anything--I consistently only get 31 days of data.
Also, this is happening with a large dataset (93000 rows) and a small dataset (9500 rows), so it doesn't appear to be a row limit.
Is this a limitation in Power BI? Is there a way around it?
Solved! Go to Solution.
Found the issue--query was pointing to a development workspace. ![]()
Hi @DolEgon22
According to this article, For the Standalone or Paid tier, data collected in Log Analytics is available for the last 31 days.
Best Regards
Maggie
Here is the rowcount when using 62 days in Log Analytics:
Here is the M query for Power BI:
...and the resulting rowcount in Power BI:
Found the issue--query was pointing to a development workspace. ![]()
OK I'll clarify--we're using OMS as the data source. While this is technically Log Analytics, it can be configured for data beyond 31 days, which we have. Power BI does not see data beyond 31 days even though the query has no time limit set. In fact, even if I set it to:
"timespan"="P62D"
I still only get 31 days.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 58 | |
| 45 | |
| 42 | |
| 21 | |
| 18 |