Get started
Editions
Compare Logic Fabric for Dataverse with Logic Fabric for Dynamics 365 CE on-premises and choose the one that fits your deployment.
Logic Fabric comes in two editions, one for each way you can run Microsoft’s customer-engagement platform. Both editions install the same solutions, give you the same designers and run your logic the same way. The differences are where they run, a handful of labels, and the features that depend on Microsoft cloud services.
Logic Fabric for Dataverse
Section titled “Logic Fabric for Dataverse”The edition for Microsoft Dataverse: Power Platform environments in the cloud, including environments that run Dynamics 365 Sales, Customer Service and other Dynamics 365 apps.
- Includes every Logic Fabric product: Logic Composer, Process Orchestrator, Logic API, the expression language and the Logic Fabric CLI.
- Works with the AI products: Logic Foundry, Logic Conductor and the Logic Agents.
- Uses Dataverse wording in the designers: Yes/No, Row, Choice, Table.
- Offers the In Entra group rule in preconditions, so you can restrict who runs a block, flow or process by Microsoft Entra ID group.
- Sits alongside Power Automate, Power BI, Copilot Studio and the rest of the Microsoft cloud. See Logic Fabric and the Microsoft ecosystem.
Logic Fabric for Dynamics 365 CE on-premises
Section titled “Logic Fabric for Dynamics 365 CE on-premises”The edition for Dynamics 365 Customer Engagement (on-premises), for organizations that run the platform in their own data center.
- Includes Logic Composer, Process Orchestrator, Logic API, the expression language and the Logic Fabric CLI, with the same artifacts and run-time behaviour as the Dataverse edition.
- Is built for Dynamics 365 Customer Engagement (on-premises) version 9.1.
- Uses the classic Dynamics 365 wording in the designers: Two Options, Entity, Option Set.
- Does not offer the In Entra group precondition rule.
- Relies on your on-premises servers for background work: for example, built-in process escalations need the Dynamics 365 asynchronous processing service to be running.
Compare capabilities
Section titled “Compare capabilities”| Capability | Dataverse | On-premises |
|---|---|---|
| Logic Composer (logic blocks, logic flows, recipes, events, schedules, service connections) | Yes | Yes |
| Process Orchestrator (stages, gateways, parallel branches, escalations) | Yes | Yes |
| Logic API and API Studio | Yes | Yes |
| Expression language | Yes | Yes |
| Logic Fabric CLI and PowerShell module | Yes | Yes |
| Expose as Dataverse Action on blocks, flows and processes | Yes | Yes, labelled Expose as Action |
| Expose as MCP Tool (AI tools through Logic Conductor) | Yes | No |
| In Entra group precondition rule | Yes | No |
| Logic Foundry, Logic Conductor and Logic Agents | Yes | No |
| Power Automate cloud flows, Copilot Studio and other Microsoft cloud services | Yes | No. These Microsoft services require Dataverse in the cloud |
Projects use the same artifacts in both editions, so logic you build on-premises keeps its meaning if you later move to Dataverse.
Label differences
Section titled “Label differences”The designers use each platform’s own vocabulary. The meaning is identical; only the words change.
| Concept | Dataverse label | On-premises label |
|---|---|---|
| True/false type | Yes/No | Two Options |
| A whole record as a type | Row | Entity |
| A choice from a list | Choice | Option Set |
| Target of the Has permission precondition rule | Table | Entity |
| Words in step descriptions and help | “row” | “record” |
| Flag that registers a block, flow or process as a custom action | Expose as Dataverse Action | Expose as Action |
| Description of the Run Process Action flow step | “Run a Dataverse Action…” | “Run an Action…” |
| Precondition rule In Entra group | Offered | Not offered |
Lookup, Currency, Text, Whole Number, Decimal Number, Floating Point Number and Date and Time read the same in both editions.
Supported platform versions
Section titled “Supported platform versions”| Edition | Platform |
|---|---|
| Logic Fabric for Dataverse | Microsoft Dataverse (Power Platform environments in the cloud) |
| Logic Fabric for Dynamics 365 CE on-premises | Dynamics 365 Customer Engagement (on-premises) 9.1 |
Each edition has its own installation packages. Always install the package built for your edition. See Installation.
How to choose
Section titled “How to choose”Your edition follows your platform, so in most cases the choice is already made:
- You run Dynamics 365 or Power Apps in the cloud: choose Logic Fabric for Dataverse. You get every product, including the AI products, and you can combine Logic Fabric with Power Automate, Power BI and Copilot Studio.
- You run Dynamics 365 Customer Engagement in your own data center: choose Logic Fabric for Dynamics 365 CE on-premises. You get the full design and run-time experience for logic, processes and APIs.
- You plan to move from on-premises to the cloud: start with the on-premises edition. Your projects carry the same artifacts, so you can import them into a Dataverse environment that runs the Dataverse edition when you migrate. Review any precondition rules and integrations that should change with the move, for example to use In Entra group.
For licensing and commercial questions, contact Flowon.