Hello Microsoft Fabric Product Team,
In Microsoft Fabric, the SQL Analytics Endpoint is a critical consumption layer for Lakehouse data, especially for downstream systems, reporting tools, and automated jobs that rely on T‑SQL access.
Today, there is no official or exposed metadata indicating when the SQL Analytics Endpoint was last synchronized with the underlying Lakehouse data. The refresh process is asynchronous, and while activities such as “Refresh SQL Analytics Endpoint” exist, they do not provide:
- a reliable last refresh timestamp,
- a refresh completion status that can be queried programmatically,
- or a way to correlate Lakehouse data availability with SQL endpoint readiness.
Problem
In production environments, this lack of visibility makes it difficult to:
- Validate data freshness after Lakehouse pipelines complete
- Diagnose data latency issues between Spark (Lakehouse) and SQL consumers
- Coordinate downstream jobs that depend on up-to-date SQL data
- Implement governance or SLAs around data availability
Teams are often forced to rely on empirical testing (data comparisons, polling, manual verifications), which is fragile and operationally costly.
Proposed Enhancement
Expose a system-level indicator for the SQL Analytics Endpoint such as:
- LastSuccessfulRefreshTimestamp
- Optional RefreshStartTime / RefreshEndTime
- Refresh status (e.g., InProgress, Succeeded, Failed)
This information could be made available through one or more of the following:
- A system DMV or system table in the SQL Analytics Endpoint
- Lakehouse or workspace metadata (Fabric UI / APIs)
- Pipeline activity outputs or logs
- Fabric monitoring or governance endpoints
Benefits
Providing this visibility would:
- Enable deterministic orchestration between Lakehouse pipelines and SQL consumers
- Improve troubleshooting and reduce false data-quality incidents
- Support enterprise-grade governance, observability, and SLA definitions
- Increase trust in SQL-based consumption of Fabric Lakehouse data
This feature would significantly improve operational clarity for customers running production workloads on Microsoft Fabric.
Thank you for considering this suggestion.
Best regards,
Rafael Tiago Alves Ribeiro
Data Architect SQ / Microsoft Fabric User
