If you’ve been paying any attention to Copilot in SharePoint this month, you’ll have seen the new live-linked dashboards. That one’s had all the attention. Rightly so. Pointing Copilot at a Microsoft List and getting a live HTML dashboard back is a really big deal for anyone who’s ever had to rebuild an Excel export with charts and graphs or similar.

But it’s not just the dashboards. There were 3 features in this drop, and they all stack.

Let me walk you through them.

1. Live dashboards connected to your Lists

You can now point Copilot at a Microsoft List, ask for an executive dashboard, and get back an interactive HTML report right there. Charts, KPIs, filters, priority breakdowns, all connected live to the source data.

Add 3 items to the List, refresh the dashboard. There they are.

Same pattern works everywhere your team keeps structured data in a List:

• Inventory tracking
• Grant applications
• Recruiting pipelines
• Customer escalations

Now pair this with a SHAREPOINT.md file (a breakdown of this in the next edition), the brains of your SharePoint site, and it stops being a one-off demo. Mine tells Copilot to save every dashboard into the Reports library. No exceptions.

Why that pairing matters:

• Dashboards land where they should, not in Shared Documents where the whole org can see them
• Everyone on the team gets the same defaults with zero training
• The rule you write once compounds every time someone uses the site

That’s every user, every prompt, every session.

2. A button on your page that runs a prompt

A question I get a lot: how does anyone on the team actually know what Skills we’ve got on our site?

Page buttons can help. This means that you can drop a button onto your homepage, wire it up to a prompt or a Skill, and give it a label that makes sense:

• “Draft this week’s status.”
• “Find the operations manual for X.”
• “Generate my overdue high-priority items.”

Anyone on the page clicks it and it runs. No syntax to remember, no hunting through /Skills. The button sits right there, exactly where people are already working.

And you don’t even need a fully-formed Skill for it. Wire a button to any good prompt someone on the team wrote last week and it’s live on the site the same day.

3. Turn a good prompt into a Skill

You can now take a good prompt, ask Copilot to turn it into a Skill from inside chat, get a nicely presented card back, and save it as a site skill. It lands in your Agent Assets library and every user on the site gets it.

I built the dashboard prompt in section 1. Then asked Copilot to save it as a Skill. One confirmation, done. Now anyone on the site can trigger that same dashboard just by asking for it.

The chat’s faster now too, and the slash-search for files, people, and meetings speeds the whole thing up. Turning prompts into Skills has stopped being a project.

Dashboards. Buttons. Skills. That’s your SharePoint site actually working for the team, without anyone having to remember which prompt to type or which library to look in.

I’ve done a full walkthrough of all three, with the SHAREPOINT.md governance rule in play, right here: This Copilot in SharePoint Update Changes Everything​

If you wire one of these up this week, hit reply and tell me which one. I read every reply.

Hope that brings you some value.

Talk soon, Daniel

PS: Small bit of housekeeping. I’ve moved my newsletter sends to daniel@danielanderson.io so my day-to-day inbox stays out of newsletter reputation. Replies still land straight with me. Thanks for sticking around while I’ve been heads-down with clients.