Microsoft has expanded Fabric Actions and Business Actions in Microsoft Fabric Data Factory pipelines, both in preview, so pipeline authors can call supported Fabric operations and business application actions from the same orchestration flow. The update adds broader Fabric REST operation coverage and 25 additional third-party connectors for Business Actions.
The change is aimed at workflows that continue after data movement or transformation. A pipeline can now include follow-up steps such as refreshing a semantic model, running a notebook, updating a business application, generating a document or sending a notification.
Fabric operations inside pipelines
The Fabric Actions activity lets a pipeline invoke supported Fabric REST API operations. Pipeline authors select the Fabric operation, configure its inputs and add it to the pipeline, rather than manually constructing REST API requests and handling the authentication and request details themselves.
Microsoft says it is expanding supported actions across Lakehouse, Warehouse, Notebook, Copy Job, Dataflow, Eventhouse, Eventstream, semantic models, OneLake shortcuts, Workspaces, Capacity and other Fabric areas. That gives teams a way to include platform operations in the same pipeline that handles data processing.
The practical examples are straightforward. A pipeline could run a Notebook during processing, manage a OneLake shortcut, perform a Lakehouse operation or refresh a semantic model after new data is ready.
Business Actions adds more connectors
Business Actions is the related activity for calling business systems and workflows from a Fabric pipeline. Microsoft Learn describes the Business action activity as running an enterprise application action through a Logic Apps connector.
The preview update adds 25 third-party connectors for Business Actions. Microsoft groups them across areas including CRM, communications, document generation and signing, security, financial planning, project management and marketing.
Named examples include D7SMS for SMS notifications, Formstack Documents for contracts and invoices, Pipeliner CRM and Commercient for CRM and sales processes, Nitro Sign Enterprise Verified for electronic signatures, RiskIQ for security and threat intelligence operations, and WP Connectr for WordPress publishing. Microsoft also refers to connectors for project and portfolio management systems, without naming them in the announcement.
Discovery and configuration
The updated Fabric Actions experience lets authors browse or search for supported Fabric operations. They no longer need to know the REST API endpoint before adding the activity.
After an operation is selected, the activity shows the relevant configuration and required parameters. Authors can select an existing Fabric connection or create one, enter the required inputs and use dynamic content where supported.
When the activity runs, the selected Fabric operation executes as part of the pipeline. Its response is available through the activity output, which matters for downstream branching and control flow.
Business Actions follows the same model of structured configuration for supported business application operations. The point is to reduce the amount of custom API integration needed for common follow-up actions in business systems.
Pipeline limits still apply
These are still Fabric Data Factory pipeline activities, so existing pipeline design limits and settings remain relevant. Microsoft Learn states that, by default, a pipeline can have up to 120 activities, including inner activities for containers.
General activity settings include timeout, retries and secure input or output options. The documented default timeout is 12 hours, with a maximum of seven days.
Fabric Actions activity and Business Actions activity are listed as preview features. Microsoft’s preview terms apply, and general availability timing is not stated in the material.
Pipelines that now call Fabric REST operations, refresh semantic models and hand work to business applications raise orchestration, ownership and monitoring questions that ECS's Data topic covers, alongside Microsoft Fabric, Power BI, SQL Server and Dataverse. Sessions give attendees practitioner context on where Fabric pipeline design, semantic models and downstream business processes meet in real projects. Attend with concrete pipeline patterns and the operational questions that are difficult to settle from documentation alone.
This article was written by the ECS editorial team with the assistance of Amal Agent, run.events' AI assistant, which supported the research, drafting and proofreading.