Get started
Logic Fabric and the Microsoft ecosystem
How Logic Fabric complements Power Apps, Power Automate, Power BI, Copilot Studio and Azure, and when to use which.
Logic Fabric is not a separate platform next to Dataverse. It is installed into Dataverse as solutions and works with the same tables, security roles, teams and business units as the rest of your Microsoft solution. That makes it a natural partner for the Power Platform and Azure: each tool keeps doing what it does best, and Logic Fabric adds a governed layer for business logic, long-running processes and APIs.
Built into Dataverse
Section titled “Built into Dataverse”- Same data. Logic reads and writes ordinary Dataverse tables and columns. Process instances, stage records and tasks are Dataverse records too.
- Same security. Logic is checked against the calling user. Preconditions use Dataverse security roles, teams, business units, queues and table permissions and, on Dataverse, Microsoft Entra ID groups.
- Same transaction when you need it. A recipe’s Before stage runs in the same transaction as the record change, so a failure cancels the change. The After stage runs once the change is saved, right away or in the background.
- Same app lifecycle. Every project is tied to a Dataverse solution, and the Logic Fabric CLI fits into the same release pipelines you use for your solutions.
Power Apps
Section titled “Power Apps”Model-driven apps are where your users meet Logic Fabric, usually without knowing it:
- Validations from recipes stop a save and show the user a clear message: the names of the rules that failed.
- Flows in recipes fill in values, create related records, assign work and send email as users save records.
- Business processes create tasks for users and teams, and each process instance shows its progress in a visual viewer.
For canvas apps, portals and external applications that should not talk to Dataverse directly, publish a Logic API: a versioned REST API with its own access control.
Power Automate
Section titled “Power Automate”Power Automate excels at connecting to hundreds of external services. Logic Fabric excels at business rules and transactional logic inside Dataverse. Use them together:
- Call Logic Fabric from Power Automate. Switch on Expose as Dataverse Action (on-premises: Expose as Action) on a logic block, logic flow or business process. It becomes a Dataverse custom action that cloud flows can call like any other action.
- Hand off to Power Automate from Logic Fabric. Let a logic flow write a record or call a custom action that a Power Automate flow is triggered by, then let Power Automate do the connector work.
- Keep one owner per rule. Put the rule itself in a logic block, and let every caller (recipes, processes, Power Automate) reuse it.
Power BI
Section titled “Power BI”Because process instances, stages and tasks are Dataverse records, Power BI can report on them with the standard Dataverse connector. Typical reports show open instances by stage, overdue and escalated stages, cycle times and workload per owner. No extra export is needed. See Instances for the records and fields available.
Copilot Studio and AI assistants
Section titled “Copilot Studio and AI assistants”Logic Fabric speaks the Model Context Protocol (MCP), the open standard that AI agents and assistants use to call tools:
- Logic Conductor turns the logic blocks, logic flows and business processes you flag with Expose as MCP Tool into tools an agent can run, for example “calculate the discount for this quote” or “start the onboarding process for this account”. Each run is checked against the user’s security and the logic’s preconditions.
- Logic Foundry lets an AI assistant work on your project: read it, explain it, and create or update artifacts with you.
Any agent platform that can connect to MCP servers can use them, including Copilot Studio agents where your tenant allows MCP connections.
- Microsoft Entra ID. On Dataverse, the In Entra group precondition rule restricts logic to members of an Entra group, through the group’s Dataverse team.
- Azure-hosted APIs. Service connections call any REST API described by an OpenAPI 3.0 or 3.1 specification, including APIs you host in Azure, with API key, basic or OAuth 2.0 client-credentials security.
- Azure DevOps and other pipelines. The Logic Fabric CLI and PowerShell module run in build and release pipelines to export, import and promote projects. See Pipelines.
When to use which
Section titled “When to use which”| You need to… | Use |
|---|---|
| Enforce a rule whenever a record is saved, in the same transaction | A Logic Composer recipe with a validation or a Before flow |
| Reuse a calculation or decision in many places | A logic block |
| Change several records, send email or call a REST API as part of business logic | A logic flow |
| Run work on a timetable | A schedule |
| Model multi-stage work with owners, parallel reviews and escalations | Process Orchestrator |
| Field-level form behaviour, such as showing or hiding a field | Dataverse business rules or form logic |
| Connect to a SaaS product through a ready-made connector | Power Automate |
| Approvals or notifications in Microsoft Teams and Outlook | Power Automate, triggered from Logic Fabric data |
| Dashboards and analytics | Power BI over Dataverse |
| A REST API for portals, mobile apps or partners | Logic API |
| Let an AI agent run your business logic safely | Logic Conductor |
| Let an AI assistant help you design logic | Logic Foundry and Logic Assist |
On-premises
Section titled “On-premises”Logic Composer, Process Orchestrator, Logic API and the CLI work the same in Dynamics 365 CE on-premises. Power Automate cloud flows, Copilot Studio and other Microsoft cloud services require Dataverse in the cloud. See Editions.