Problem:
When using Dataverse → Microsoft Fabric Link, there is currently no native monitoring, logging, or alerting capability in Dataverse to detect link failures or synchronization issues. Failures (such as shortcut creation errors, missing metadata tables, or incomplete refreshes) are only observable from the Microsoft Fabric side, making proactive detection difficult.
This results in delayed issue identification, increased reliance on manual checks or custom monitoring solutions, and reduced reliability for enterprise data integration scenarios.
Suggested improvement:
- Provide native diagnostic logs and telemetry in Dataverse for Fabric link operations.
- Enable real-time alerts or health status indicators when the link fails or encounters errors.
- Surface clear, actionable error details (e.g., failed tables, sync status, metadata issues).
- Offer centralized monitoring visibility within Dataverse or Power Platform admin tools.
This would improve observability, reduce operational overhead, and help customers proactively manage data integration reliability without relying on custom solutions.
Comments
definitely need that one! must have. it was unreliable and we finding out about failures from customers!
Category: Long Term Retention CE
Our organisation is dependent on this system integration, to ensure up to date data is available in Fabric via the Dataverse to Fabric Link - no native monitoring or logging being available to detect failures and alert administrators to action, seems like a significant product design flaw.A native solution would be greatly appreciated.
Category: Long Term Retention CE
