Business Rules react instantly on a form. Business Process Flows guide a user through stages, screen by screen. A classic Workflow is different again: it's server-side automation that runs in the background, with no form and no user watching, triggered by something happening to a record.
- Workflows are the older, still-supported background automation mechanism
- Triggered by create, update, status change, or a schedule
- Run as real-time (immediate) or background (asynchronous) processes
- Can update records, send emails, and wait on conditions
- Built with a classic no-code, point-and-click designer
- Power Automate is Microsoft's current recommended direction for new automation
Automation that predates Power Automate
Before Power Automate existed, Workflows were the main way to automate Dynamics 365 CE without writing code. They're older technology, but Microsoft still supports them, and plenty of environments still use them for simple, reliable background jobs. A Workflow watches a table for an event — a record being created, a field changing, a status moving — and then runs a predefined set of actions.
Those actions can update fields, send an email, create a related record, or wait for a condition before continuing. All of it is configured through a classic, form-based designer — no code, but a different, older interface than Business Rules or BPFs use.
Real-time vs. background
A Workflow runs in one of two modes:
- Real-time — runs immediately, in line with the triggering action, before the user's save completes.
- Background (asynchronous) — runs shortly after the trigger, off to the side, without holding up the user at all.
Most Workflows run in the background, which is exactly why they're well suited to things a user doesn't need to wait on — a confirmation email, a follow-up record, a status cleanup a few minutes later.
How it compares to what you've already learned
Three tools can look similar to a Workflow at first glance. They aren't the same:
| Where it runs | Trigger style | Typical use | |
|---|---|---|---|
| Business Rule | On the form, client-side only | Instant reaction to a field on screen | Show/require/default a field as someone types |
| Workflow | Server-side, background or real-time | Record events (create, update, schedule) | Send an email, update a record, no user watching |
| Power Automate | Cloud, connector-based | Record events, schedules, external triggers | Modern automation, connects to hundreds of outside services |
Business Rules don't run on the server at all — they're form-only and stop existing the moment nobody has that form open. Business Process Flows aren't really automation; they guide a person through steps rather than doing work for them. Workflows and Power Automate are the two tools that actually do things in the background without a user present.
An old conveyor belt next to a new robotic arm
Think of a factory floor with an old conveyor belt still doing its one simple job reliably, even after a newer, more flexible robotic arm (Power Automate) gets installed alongside it. The belt isn't replaced overnight — it keeps running the simple task it was built for, while the new equipment handles the more complex work.
Power Automate is Microsoft's current recommended direction: it connects to hundreds of outside services, handles more complex branching, and gets new features Workflows don't. But Workflows haven't been removed, and for a simple, self-contained background job entirely inside Dataverse, they're still a perfectly reasonable, dependable choice. For the cloud-based, connector-rich alternative, see the dedicated Power Automate tutorial.