Copilot in SharePoint: Live Dashboards, Prompt Buttons and Site Skills

When we covered Copilot in SharePoint in July, the honest caveat was that its dashboards were snapshots. Impressive to generate, stale the moment the list changed. The August update removes that caveat and adds two quieter features that matter more than they first look.

As before, this is included with the Microsoft 365 Copilot licence and still carries a preview label. Here is what shipped, where it earns time and the checks to make before your firm leans on it.

What shipped in August

• Live dashboards. A dashboard built from a list is now linked to that list. Open the report and it refreshes from the source, with a refresh control and a last refreshed time on the page. Add three items to the list and the numbers move. Dashboards can also be built from Excel and CSV files, and you can open Copilot alongside a generated report and question the data behind it, asking who is assigned to the in-progress items rather than exporting anything.
• Prompt buttons on pages. The button web part gains an action that opens Copilot in SharePoint with a prompt you write once. A “Draft status update” button on a project hub means any team member generates the same summary in one click, without knowing what to type. The same web part can run a Power Automate flow or open a link instead.
• A tidier chat. Type / in the prompt box to insert files, people and meetings as context. Thinking steps are more compact, citations get a hover card and the cards shown when skills run are cleaner. It is also noticeably quicker than the early preview.

The quieter half: skills and the site’s standing rules

Two pieces underneath these features deserve more attention than the dashboards will get.

The first is the SHAREPOINT.md file, a plain Markdown file in the site’s Agent Assets library that Copilot reads as context in every conversation on that site. It is where standing rules live: what the site is for, how things are named and instructions such as every generated report saving into one reports library, no exceptions. Every user’s chat follows the same rules, which is the difference between a tidy site and forty dashboards scattered across whichever library each person prompted from.

The second is skills. Describe a workflow in chat, for example the executive dashboard prompt you have refined over a fortnight, and Copilot drafts it as a skill for you to review and save. It stores as a Markdown file in the Agent Assets library as a site skill or in your OneDrive as a personal one. From then on anyone on the site can run it by name, or Copilot loads it when a request matches. Skills chain the things Copilot in SharePoint can already do. They cannot execute code, reach outside SharePoint or give anyone access their own permissions would not allow.

Where this earns time

• The Tuesday readout that stays current. The tracking list dashboard no longer gets rebuilt the day before the meeting. It refreshes when opened, and the filters still work.
• The consistent status update. A button on the project hub means the weekly summary is generated the same way by whoever is in that day, not just the person who knows the prompt.
• The month-end pack as a skill. The pack that took a well-honed prompt becomes a skill with a name, run by anyone, producing the same structure every month.
• Questions without exports. Standing in front of the dashboard, ask it to group the in-progress items by owner. No export to Excel, no pivot table.

The checks the demos skip

1. A live report is a standing window onto its data. Last month the exposure question was a one-off: a generated file’s permissions follow where it saves, not the list it came from. Live linking makes that question permanent. A dashboard over a tightly permissioned list, saved into a broadly shared library, now republishes that data continuously, not once. The client data governance discipline is unchanged: check where outputs land and who can open them, and use the SHAREPOINT.md file to make the landing place a rule rather than a habit.

2. Live is still not Power BI. Refresh on open is not scheduled refresh, and an HTML report has no row-level security or audit trail. Our July rule of thumb loses its first half and keeps its second: the staleness caveat has gone, but Copilot dashboards remain right for communication and Power BI for operations. A number the business runs on still belongs in a governed report.

3. The site’s brains are ordinary files. SHAREPOINT.md and every skill are Markdown files in the Agent Assets library, and by default anyone with Edit permissions on the site can change them. They steer what Copilot does for every user, so treat them like policy rather than scratch notes: agree an owner, review changes and tighten permissions on the library if the default is too open.

4. Copilot can now write to your lists. Ask it to add items and it will, filling every column. That is useful capture at the end of a meeting and exactly where a checking habit matters, because a generated row looks as confident as a typed one. Agree the review point before the habit spreads, the same honest register that applies to agents everywhere: assistance with a person checking, not entries nobody looks at.

From a prompt one person knows to a habit the site owns

There is a progression hiding in this update. A prompt starts in one person’s head. The button puts it on the page for the team. The skill makes it a named, reviewable asset the site owns. The MD file sets the rules every conversation follows. That is adoption in miniature, from first Copilot habits towards Copilot agents, with a person reviewing at each step.

It is still not a workflow strategy. A process with multiple steps, exceptions or systems beyond SharePoint belongs in Power Automate or a custom build, and choosing the right route is the same question it was last month.

What to do with this

Pick one well-managed site. Write the SHAREPOINT.md rules first, starting with where reports save. Then one list, one live dashboard, one button and, if the pack repeats monthly, one skill. Agree who checks generated numbers and list entries before either starts to circulate. If your sites are not somewhere you would want AI reading and writing, that is the readiness work to do first.

We cover this as part of Copilot training built around your own sites, and the tidy-up beforehand through SharePoint consultancy. If you want a view on which site to start with, book a consultation and we will look at it with you.

Sources checked

Last checked: 8 August 2026.

• What’s New in Copilot in SharePoint: August 2026
• Extend Copilot in SharePoint with skills
• Use the Button web part
• The SharePoint.md file, your site’s context for Copilot in SharePoint