Enable users and report developers to easily access and display the last successful refresh time and the next scheduled refresh time across all Power BI data sources, including:
Power BI Datasets (Import and DirectQuery)
Dataflows
Datamarts
Fabric Lakehouse / Warehouse
Other data model objects used in Power BI reports
Why this is needed:
Consistency Across Models: Currently, there's inconsistent visibility depending on whether you're using Import, DirectQuery, Dataflows, or newer Fabric-based models. Users and developers need a unified experience.
End-User Clarity: Report viewers often ask, “How fresh is this data?” or “When will this refresh next?”—this should be natively and easily answered from within the report.
Operational Efficiency: Reduces reliance on manual timestamp measures, third-party monitoring, or admin tools to understand refresh patterns.
Support Root-Cause Analysis: If data appears stale, users or support staff can immediately confirm if the refresh ran or is pending.
Supports Governance and Auditability: Especially important for regulated or business-critical environments.
Impact:
Improves data transparency and trust.
Reduces overhead for Power BI developers who currently work around this with manual logic.
Creates a unified governance layer for all Power BI data sources.
makromer
on:
Fabric Data Pipeline should be able to execute dbt...
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections