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!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi everyone,
We have a monitoring pipeline that collects Power BI refresh history using the Activity Events API (GET /admin/activityevents). The pipeline reads RefreshDataset activity events and then calls GET /groups/{groupId}/datasets/{datasetId}/refreshes for each discovered workspace/dataset pair.
We have observed a sudden and significant change on December 19, 2025 and would like to confirm whether this is an intentional change by Microsoft.
We track RefreshDataset activity events daily. Here is what our data shows:
Date RefreshDataset Events Unique Workspaces
| Dec 15 | 25 | 7 |
| Dec 16 | 39 | 6 |
| Dec 17 | 50 | 6 |
| Dec 18 | 36 | 5 |
| Dec 19 | 143 | 20 |
| Dec 20 | 126 | 15 |
| Dec 21 | 125 | 15 |
| Dec 22 | 170 | 20 |
The number of RefreshDataset events nearly quadrupled overnight (36 -> 143), and the number of unique workspaces jumped from 5 to 20.
At the same time, our factrefresh table (populated via the refresh history API) started showing Scheduled refresh types:
Date Scheduled Refreshes Workspaces Datasets
| Dec 18 | 0 | 0 | 0 |
| Dec 19 | 28 | 3 | 8 |
| Dec 20 | 28 | 3 | 8 |
| Dec 21 | 28 | 3 | 8 |
Before December 19, we only captured ViaApi and occasional OnDemand refreshes. After December 19, Scheduled refreshes consistently appear.
Based on prior community posts, the Activity Events API was known to exclude scheduled refresh events from RefreshDataset:
It appears that Microsoft has resolved this limitation around December 19, 2025, and the Activity Events API now includes RefreshDataset events for scheduled refreshes as well.
We would appreciate any confirmation from Microsoft or the community, as this directly affects how we architect our refresh monitoring solution.
Thank you.
Hello @dundyscholt,
We suggest raising a Microsoft Support ticket. When creating the ticket, please include all relevant details such as your observations, timestamps, API endpoint used, authentication method, and the steps you have already taken. This will help the support team better understand the scenario and provide accurate confirmation.
You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Hi @dundyscholt
It appears that there could be some extra metadata that's been added to the API responses. When I have worked previously with the refresh history API, I have found that it'll always return all the events. Not specifically ones that I could select.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 46 | |
| 41 | |
| 40 | |
| 25 | |
| 23 |