An Azure service that provides an event-driven serverless compute platform.
Hello **Bill Hodgkinson,
events or webhooks directly from a Fabric SQL Database. Fabric SQL DB currently does not generate event notifications when tables are updated, which is why pipelines, notebooks, or other Fabric items cannot yet be triggered automatically from those changes.
Microsoft has been expanding event-driven capabilities within Fabric, particularly around pipeline triggers, data activator scenarios, and event streams. However, database-level change events for Fabric SQL DB have not yet been formally announced on the public roadmap. The best place to track upcoming features and announcements is the official Fabric roadmap page:
In the meantime, the architecture you described—using an external trigger such as an HTTP-triggered function in Azure Functions to call the Fabric Pipeline REST API—remains the recommended approach for near real-time execution when a Power Table update occurs.
If Fabric introduces native database change events or event subscriptions in the future, that would enable a more direct pattern where the update in Fabric SQL DB could trigger a pipeline or notebook without requiring an external component.
The functionality you're referring to — sp_invoke_external_rest_endpoint — is not currently supported in a Microsoft Fabric SQL Database.
An external trigger (Azure Function, app layer, or automation) is required to call the Fabric Pipeline API.
Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.