# SharePoint Quick Steps vs Power Automate, the no-code button that replaces half your simple flows

> SharePoint Quick Steps puts one-click action buttons on every list row, no flow required. Here's the honest decision framework for when a button beats a Power Automate flow, and when it doesn't.

[Home](https://tenantcraft.ca/)  [Insights](https://tenantcraft.ca/insights)  Power Platform

Execute May 19, 2026  7 min read

Geri Crroj

Microsoft 365 consultant, Niagara, Ontario

## The problem

Open any SMB’s Power Automate environment and you’ll find the same thing: a pile of tiny, one-line flows. “Set status to Done.” “Email the manager.” “Move the file to Archive.” Each one is a manual flow somebody triggers by hand, and each one is a separate thing to own, license-check, and eventually fix when a connection breaks.

In February 2026 Microsoft started shipping a feature that does most of those jobs without a flow at all: **SharePoint Quick Steps**. It went generally available worldwide in May. The how-to coverage is everywhere. The harder question gets skipped: _when_ you should reach for a Quick Step and when you should still build a flow.

That’s the gap this post fills. It’s a decision-framework piece, not a how-to. If you’ve already decided and just want the clicks, [here’s how to add a Quick Steps button](https://tenantcraft.ca/insights/add-quick-steps-column-sharepoint-list). Quick Steps does not replace Power Automate. It replaces a specific, narrow slice of it: the one-click, single-action, person-triggered task.

The 5-minute version

If you read nothing else:

1.  **Quick Steps is a new SharePoint column type.** You add it to a list or library like you’d add a Choice or Person column. It renders clickable **action buttons** on every row.
2.  **Use it when the action is user-triggered, single-step, and you want it visible in the list.** Set a status, draft a notification email, start a Teams chat, request an approval, archive a file, or kick off an existing flow.
3.  **Keep Power Automate for anything automated, scheduled, multi-step, branching, or premium-connector.** Quick Steps has no trigger but a click, and one action per button.
4.  **Watch the governance default.** Any user with Edit permission can create a Quick Steps column, and the standard Members group _has_ Edit. There’s no admin toggle. The fix is further down.

The rest is the detail.

## What Quick Steps actually is

A Quick Step is a **column** you add to a SharePoint list or library, configured with the no-code “Rules”-style sentence builder (the same plain-English approach SharePoint already uses for formatting rules). Once it’s there, every row in the view shows one or more action buttons. You can put up to **15 buttons** in a single Quick Steps column.

There are six action types a button can be wired to:

1.  **Draft an email**, opens a pre-filled Outlook draft. It does _not_ auto-send; the user reviews and hits send.
2.  **Start a Teams chat**, opens a chat with the relevant people.
3.  **Set a value**, updates one or more columns at once, and supports tokens like _Current User_ and the current date.
4.  **Send an approval request**, needs content approval enabled on the list first.
5.  **Execute a flow**, launches an existing Power Automate flow.
6.  **Ask SharePoint (AI)**, runs a pre-configured AI prompt against the selected file. (More on this one later. It’s the exception.)

Document libraries also get **Move** and **Copy files** as button actions.

![A SharePoint list with a Quick Steps column rendering action buttons on each row](https://tenantcraft.ca/images/quick-steps-list.png)

What it looks like

A Quick Steps column adds clickable action buttons to every row, right inside the normal list view.

## The capability line, Quick Steps vs a flow

Here’s the honest comparison. Quick Steps is deliberately small. That’s the point of it, and it’s also exactly where it stops.

| Capability | Quick Steps | Power Automate cloud flow |
| --- | --- | --- |
| Trigger | User clicks a button on a row (the only trigger) | Automated, scheduled, or manual |
| Steps per action | One action per button (you can have up to 15 separate buttons) | Many steps in sequence |
| Branching / conditions inside the action | None | Full conditions, switches |
| Loops | No | Yes |
| Error handling | No | Configure run-after, scopes, retries |
| Multi-stage approval | Single approval request only | Sequential / parallel stages |
| Runs unattended | No (needs a click) | Yes |
| Display conditions | Metadata-based (hide a button when Status ≠ “Open”) | n/a (handled in flow logic) |

Two things on that table get misquoted, so be precise about them.

First, **one action per button.** You cannot build a Quick Step that “updates a column _and_ sends an email” as a chained sequence. _Set a value_ can update several columns in one go, but that’s still one action. If you need a chain, you need 15 buttons or a flow.

Second, **conditions.** Quick Steps does support **metadata-based display conditions**: a button can be hidden when a row’s Status isn’t “Open,” for example. What it does _not_ have is permission-aware visibility. A button can still appear for someone who lacks the rights to run it, and they’ll hit an error when they click. So it isn’t “no conditions.” It’s “display conditions yes, in-action branching and permission-aware visibility no.”

> Quick Steps replaces the one-click manual task. It does not replace the workflow. Know which one you’re actually building.

## The bridge pattern

The two tools aren’t rivals. They compose. A _Set a value_ Quick Step can silently change a column on a row. A Power Automate flow with an **“item modified”** trigger then fires off that change. So a single button click can kick off an arbitrarily complex flow.

That’s the pattern when you want a button in the list view _and_ the heavy lifting of a real flow: the Quick Step is the doorbell, the flow is the machinery behind the door.

## The decision framework

Use this to decide before you build anything.

**Use a Quick Step when:**

-   The action is **user-triggered**. A person decides, then clicks.
-   It’s **single-step**: set a status, draft a notification, start a chat, request an approval, archive a file, or kick off an existing flow.
-   You want the action **visible right in the list view**, next to the data.
-   You want **zero added licensing**: a native action with no flow involved at all.

**Use a Power Automate cloud flow when:**

-   It must run **automatically or on a schedule** with no click.
-   It needs **multiple steps, branching, loops, or error handling**.
-   It needs **premium connectors** or systems outside Microsoft 365.
-   It needs **multi-stage approvals**.

**Use Power Apps when:**

-   You need a real **multi-screen data-entry interface**: something beyond a row button or a list form.

## Licensing, read the framing carefully

This is the angle that saves real money, and it’s also the one most people quote slightly wrong.

Quick Steps itself carries **no extra license**. The five native actions (set a value, draft email, Teams chat, send approval, move/copy files) run on standard SharePoint, Outlook, and Teams capabilities that come with any Microsoft 365 plan. For those, **no Power Automate flow is involved at all**, so the premium-connector question simply never comes up.

The trap is the **Execute a flow** action. If a Quick Step _launches a Power Automate flow_, that flow’s own licensing applies, unchanged. Standard connectors (SharePoint, Outlook, Teams, Approvals) are fine on base Microsoft 365. But one premium connector (Dataverse, SQL, generic HTTP, a third-party service) makes the _whole flow_ premium, at about US$15 per user per month. Launching that flow from a button changes nothing about its licensing.

Frame it correctly

The win with a native Quick Step isn’t that it “avoids premium licensing.” It’s that **no flow exists in the first place**. If your Quick Step runs a flow, you still own that flow’s licensing in full. Confirm current Canadian pricing before you quote the ~US$15 figure to anyone.

## Governance, the default that will bite you

Here’s the one to flag before you roll Quick Steps out anywhere.

To **create and configure** a Quick Steps column, a user needs **Edit** permission on the list. And the default SharePoint **Members** group _has_ Edit. So out of the box, any member of a site can add action buttons, including buttons that run flows or fire AI prompts, with no admin sign-off. There is **no new tenant admin toggle** for this.

The documented fix is straightforward: downgrade the **Members** group from **Edit** to **Contribute**. Contribute lets members add and edit items but not create columns, so only **Owners** can build Quick Steps. If you care about who’s wiring up buttons on your lists, make that change before you announce the feature, not after.

Running a Quick Step is lighter than creating one, but it still varies by action. _Draft email_, _Teams chat_, and _execute flow_ need **Read**. _Set a value_ and _Send approval_ need **Edit**. Executing a flow also requires the clicking user to have permission to run that specific flow.

## The AI Quick Step is a different animal

The sixth action, **Ask SharePoint**, runs a pre-configured AI prompt against the selected file via the SharePoint Knowledge Agent (“AI in SharePoint”). It’s tempting to treat it like the other five. Don’t.

Unlike the rest of Quick Steps, **AI in SharePoint is still opt-in Public Preview** as of May 2026. It is not generally available. It’s **off by default** (an admin has to opt in) and it **requires a Microsoft 365 Copilot license** for each user who uses it. Like Copilot, it respects existing permissions and only returns what the user can already access. That also means it **amplifies any pre-existing oversharing**. If your permissions are loose, an AI prompt will find what loose permissions expose.

So treat the AI mode as preview-gated and Copilot-licensed. The other five action types are GA and free with M365; the AI one is neither yet.

Rebuilding old workflows? The playbook covers what becomes a Quick Step and what stays a flow.

SharePoint Workflow Rebuild Playbook

PDF · 7 pages · 44 checkpoints

[Email me the PDF](https://tenantcraft.ca/resources/guides/sp2013-workflow-rebuild-playbook)

## Bottom line

Quick Steps is genuinely useful, and it will quietly retire a chunk of the throwaway one-line flows cluttering your environment. But it earns its place by being small: one click, one action, one person deciding. The moment you need something to run on its own, branch, loop, or reach outside Microsoft 365, you’re back in Power Automate. That’s correct, not a limitation.

Decide first. If it’s a manual, single-step task you want sitting in the list view, build a button. If it’s a process, build a flow. And before you let the whole team loose on it, downgrade Members to Contribute so the buttons are built on purpose.

TWENTY MINUTES, NO PITCH

## Tell me what is stuck. I will tell you what it takes.

Same consultant from the first email to the last cutover. If I am not the right fit, I will refer you to someone who is.

[Book a 20-min call](https://tenantcraft.ca/contact) [See published rates](https://tenantcraft.ca/pricing)

---

_Canonical HTML: https://tenantcraft.ca/insights/sharepoint-quick-steps-vs-power-automate · Agent guide: https://tenantcraft.ca/llms.txt · Site map: https://tenantcraft.ca/sitemap-index.xml_