# Two Ways to Launch a Copilot Interactive Form in SharePoint

> Launch a Copilot interactive form in SharePoint from a quick step in the library's Integrate menu or a home page button, both calling the same skill.

- URL: https://www.danielanderson.io/articles/launch-copilot-interactive-forms/
- Author: Daniel Anderson, Microsoft MVP (https://www.danielanderson.io/)
- Published: 2026-11-20
- Video: https://www.youtube.com/watch?v=QyGDlGbQLog

## Key takeaways

- You can launch a Copilot interactive form in SharePoint from a quick step on the library or from a button on a page, and both can run the same skill.
- In my demo the quick step sat under the three dots, then Integrate, and sent /overdue-document-review to Copilot in SharePoint, which opened the form over the library.
- A home page button that runs a Copilot prompt opened the same form without the library being open, because the skill names the library and the process.
- Submitting the form sent my decisions to Copilot as a chat message, and nothing in the library was updated until I clicked Update on the Update items card.
- Keep the library, the rules and the form template in the skill, so each launcher only has to say the skill's name.

You can launch a Copilot interactive form in SharePoint two ways without anyone typing a prompt: a quick step on the library, or a button on a page. Both can run the same skill, so the same form opens from either one.

Quick steps are underutilised. They're kind of hidden away under the three dots, so a lot of people don't know they're there. And did you know you can run a Copilot prompt from a button? Put the two to work and your end users get a really nice experience, with no prompt to remember.

## Before you start

- **A form saved as a skill.** Both launchers call a skill, so build the form first and save it. [Building an interactive form with Copilot in SharePoint](https://www.danielanderson.io/articles/copilot-sharepoint-interactive-forms/) covers the prompt and the "make this a skill" step.
- **Copilot in SharePoint.** Everyone who launches the form needs a Microsoft 365 Copilot licence.
- **Edit permission on the library** to add a quick step, and edit rights on the page to add a button.

Everything below comes from my demo site, with sample subcontractor documents. The skill is called overdue-document-review. It finds the approved documents in a Compliance Documentation library that are past their Next Review Date and opens them in a form.

## How do you launch the form from a quick step?

A [quick step](https://www.danielanderson.io/articles/sharepoint-quick-steps/) is a saved action on a list or library, and one of the actions is **Ask Copilot**, which holds a prompt. Mine is called Overdue Documents, and its prompt is the skill's name, /overdue-document-review.

1. Open the library and select the three dots on the command bar.
2. Select **Integrate**.
3. Select the quick step. In my library it's **Overdue Documents**.

The Copilot pane opened with /overdue-document-review already sent. Copilot showed **Used site skill: overdue-document-review**, then opened the form in an HTML preview over the library, with 7 approved documents past their review date. Much better than working through them in the library view.

Each document is a card with three choices: **Mark Expired**, **Correct the date** or **Leave for now**. Beside the cards, a subcontractor insurance check updates as you click. When I marked a public liability certificate as expired, the form warned me that it would leave that subcontractor without an approved, in-date certificate. A check and balance, before anything is submitted.

The form also matched the HTML view behind it. I have a brand and theme skill on the site that runs every time an HTML page, view or form is created, so the colours and type come out the same without me asking.

## How do you launch it from a button on a page?

A [Copilot button on a SharePoint page](https://www.danielanderson.io/articles/sharepoint-copilot-button-web-part/) opens Copilot and runs the prompt you've saved in it. Mine is a Button web part on the home page, labelled **Review overdue documents**, set to the **Open Copilot in SharePoint** action with the same skill name as its prompt.

1. Add a Button web part to the page.
2. Choose **Open Copilot in SharePoint** as the action and put the skill's name in the prompt.
3. Give it a label that says what people get, then publish.

I clicked it from the home page, with the library closed. Copilot loaded the overdue-document-review skill, checked the library and opened the same form, this time with the 2 documents still overdue. I wasn't on the library at any point. The skill knows which library to look at and what process to follow.

This time I corrected the dates on both documents and knocked them off in one go.

## What happens after you submit?

The same thing from either launcher. **Submit review** opens a **Send to chat?** box showing the message that's about to go to Copilot. Mine listed the rules in plain words: set Document Status to Expired for the items I'd marked, set Next Review Date for the ones I'd corrected, leave the rest unchanged, and don't touch any other field.

Copilot then showed an **Update items** card with **Update** and **Cancel** buttons. On the first run it read "Item ID 1, Item ID 4 and 3 other items will be updated". I clicked Update, and Copilot confirmed 5 updates applied. In the library's HTML view, Approved dropped from 10 to 7 and Expired rose from 5 to 8.

On both runs, nothing in the library changed until I clicked Update. Human in the loop.

## Which launcher should you use?

| | Quick step | Page button |
| --- | --- | --- |
| Where it lives | The library, under the three dots and Integrate | Any page, such as the site home page |
| Suits | People already working in the library | People who rarely open the library |
| Who sets it up | Someone with Edit permission on the library | Someone who can edit the page |
| How it's built | A quick step with the Ask Copilot action | A Button web part set to Open Copilot in SharePoint |
| What it sends | The skill's name | The skill's name |

I use both on the same site. The quick step is for whoever looks after the library day to day. The button is for everyone else, who can do the review from the home page without knowing where the library is.

## Keep the process in the skill, so the launcher only says its name

My quick step and my button each hold one line: the name of the skill. The library to check, the definition of overdue, the form template and the rules for writing back are all in the skill. I'd set it up that way on every site.

The review rule then lives in one place. Put the process in the button's prompt and again in the quick step's prompt, and you have two copies to keep in step. [What SharePoint skills are and how to build one](https://www.danielanderson.io/articles/sharepoint-skills/) covers where the skill file lives and who can change it.

Check who can edit each piece before you roll it out. Anyone with Edit permission on the library can change a quick step for everyone who uses it, and anyone who can edit the page can change the button's prompt. On a compliance library I'd keep both to the people who own the process.

Then think about who won't see them. The Copilot action in a quick step and the Copilot button both need a Microsoft 365 Copilot licence, and people without one don't see the button at all. If half the team is unlicensed, they still need the standard library view to do the same job.

Start with one job your team does in a list or library every week. If it already has a form, save it as a skill and add one launcher where that work starts.

## Frequently asked questions

**Can a SharePoint quick step run a Copilot skill?**
Yes, in my demo. The quick step sent the skill name with a forward slash, /overdue-document-review, and Copilot in SharePoint showed "Used site skill: overdue-document-review" before it opened the form. The pane also noted that the chat experience was customised for the site by SHAREPOINT.md.

**Do I have to be in the library to open the form?**
No. The page button opened the form from the site home page with the library closed. Copilot's steps read "Loaded overdue-document-review skill" and "Found the relevant tools" before the form appeared.

**What does the form send to Copilot when I submit?**
A plain-language instruction you can read first. Mine told Copilot to apply only my selected actions, to accept a corrected date only if it was after today, to skip a missing or invalid correction and tell me, and to leave every other field alone.

**Will the form look like the rest of my site?**
Mine matched because a brand and theme skill on the site runs whenever an HTML page, view or form is created. On the second run the Copilot pane listed it as a second site skill used, alongside overdue-document-review.
