What’s an AI-infused button?
For fifteen years, the SharePoint button was a styled hyperlink: click it, go somewhere else. In 2026 it has become one of the most strategic surfaces in Microsoft 365. Under the MC1419800 rollout (GA completing mid-August 2026), the Button web part can now launch a predefined Copilot in SharePoint prompt or start a Power Automate flow by Flow ID. A parallel change adds a Quick Steps column that drops a real button into every list or library row.
This matters because AI has an interface problem, not a capability problem. Copilot and Skills can already reason over your content — but only if a user knows the feature exists and how to phrase the prompt. A button collapses that into one click, turning an intimidating chat box into a named, governed, repeatable action that sits exactly where the work happens. In effect, the button becomes the front-end of your AI and automation estate. As with any early capability, it ships with sharp edges.
Two surfaces to keep separate
The Button web part lives on a page and runs in one of three modes — classic link, Copilot prompt, or Power Automate flow.
- The Copilot mode needs the clicking user to hold an M365 Copilot license.
- The flow mode works for any authorized user.
- The Quick Steps column lives in a list or library: add the column, and a button renders in every row that can move/copy the item, trigger a flow-by-Flow ID, or run an “Ask SharePoint” prompt against the item or whole library. Buttons can even be conditional — shown only when another column equals a value — turning the library into a context-aware app.
Two practical notes on access. Licensing splits by mode: the Copilot-prompt button requires the clicking user to hold a Microsoft 365 Copilot license, while the flow button works for any authorized user regardless of Copilot licensing. And rollout is staggered — GA completes worldwide by mid-August 2026, but later for sovereign clouds (GCC by late August, GCC High into early September) — so what a tenant sees depends on its ring.
Five things I’ve found
- 1 – Page buttons run flows from the default environment only
The Button web part’s Flow ID picker only resolves flows in your tenant’s default Power Platform environment — not personal/developer, dedicated dev/test, or managed production environments (confirmed in the Microsoft Community Hub thread on this behavior). Mature orgs deliberately move automation out of the default environment into ALM-managed, Dataverse-backed environments — exactly the flows the button can’t see. So, the feature nudges makers back toward the least-governed environment in the tenant.

Two workarounds if you need a non-default flow today: configure the button as Open Link pointing at the flow’s direct “run” URL instead of using the Run Flow action; or switch the flow to a “When an item is created or modified” trigger gated on a column value, since automatically started flows run fine from any environment. Neither is as clean as native support, but both ship today.
- 2 – A prompt button can solve skills discoverability
Because a page button fires a predefined prompt, the prompt can be about your AI estate. Configure one that reads “List every Copilot in SharePoint Skill on this site with its owner,” and you’ve turned an invisible, scattered set of skills into a discoverable, self-documenting catalog rendered on click. Skills have always suffered a discoverability gap; a single well-written prompt behind a button becomes a living index.

One caveat to set expectations: skills are stored as SKILL.md files in the site’s Agent Assets library, so an “owner” maps to the file’s Created/Modified By. A last-run-time column, however, is not something SharePoint currently exposes for skills — there is no documented skill run-history surface — so treat that field as aspirational until Microsoft adds it (or just read my Super Skill blogpost: https://gokan.studio/2026/06/28/from-skills-to-super-skills-in-sharepoint/)
Because those skill files live in a real SharePoint library, they inherit real governance. The product-managed Agent Assets library can’t be deleted, but you can apply standard file controls to it — permissions, retention, sensitivity labels, and auditing. By default, anyone with Edit on the site can create a skill, and anyone with View can run one; break inheritance on the library if you need a tighter create-versus-run model.
- 3 — Quick Steps could run a skill — or let the user choose
A Quick Steps button set as an Ask SharePoint action runs a prompt against the item, and because that prompt is free text, you can direct it toward a specific skill — the makings of a one-click “run this skill on this document.” Even better would be a prompt that proposes the available skills and lets the user pick which one to run on the selected item, turning a single button into a menu that collapses discovery and execution into one gesture.

- 4 — Quick Steps hit the same environment ceiling
A Quick Steps button that triggers a flow is also restricted to the default environment. You paste a Flow ID from the flow’s URL, but if that flow lives in a dev, test, or production environment outside the default, the Quick Step can’t run it. Same root cause as Point 1, and the same two workarounds apply — now multiplied across every list and library.

- 5 – This flow cannot be run directly from Power Apps. Only flows with a “Power Apps” or “Power Apps (v2) trigger can be used.
Basically, running a flow requires in SharePoint specific triggers. It can be only either run manually or Power Apps. The PG told me that this was a limitation of the Power Platform, and they’re going to see if they could resolve this.

My ask to Microsoft: a native “list skills → run a skill” action
Feature request for Microsoft: Add a first-class Quick Step (and Button web part) action type that lists the skills available on the site and runs a selected one directly — a real, registry-backed picker, not a hand-written prompt hoping the model enumerates them correctly.
Everything in Points 2 and 3 works today only by describing what you want in prose. Promoting that to a supported action would give admins a governed, click-to-run skills surface with none of the prompt-engineering fragility — and it would turn the current clever workaround into a dependable capability. If Microsoft ships one thing from this article, this is it.
What a button can really do — and where it’s heading
Set the limitations aside, and the capability is striking. One button can ask SharePoint anything (grounded on your content and trimmed to the user’s permissions — “summarize this contract’s termination clauses,” “which of these 400 files mention the vendor”), generate structured output like a live dashboard or skills catalog, or run a skill or a flow that actually changes the world. One control spans “answer a question” to “create records and route approvals.”
The bigger prize is treating the button as a composable action surface. Chain it — a prompt classifies a document, writes a column, a conditional Quick Step appears, its flow routes the item downstream — and you have an agentic pipeline whose entry point is a single click. Conditional, permission-trimmed buttons make the same library render different actions per user, so it behaves like a line-of-business app with no SPFx. As Copilot Studio and custom agents mature, the button is the natural governed launch point for them. And because a button encodes a prompt or skill, it makes AI usage consistent and auditable — the difference between AI as a novelty and AI as a repeatable business process. Defined once, it can travel onto a Viva Connections dashboard or a Teams tab, carrying its action with it.
The concept is right; the gaps are in the wiring. Free the flow picker from the default environment and replace prompt-based skill enumeration with a real “list skills → run skill” action — do those two things and the button stops being a clever workaround and becomes the dependable front door to everything intelligent in SharePoint.
Hope that helps!
Renewed Revolution






Leave a Reply