Copilot in SharePoint: Documents, Dashboards and Tidier Libraries from a Prompt

For most firms SharePoint has spent twenty years as the place files sit. The June and July 2026 updates to Copilot in SharePoint change what the site itself can do: a chat panel inside your sites, libraries and lists that produces things rather than just finding them.

The demo videos doing the rounds are genuinely representative for once. But they are demos, so they stop at “look what it built”. This post covers what shipped, where it earns real time back, and the four things to check before your firm leans on it.

What it can now do

From a prompt inside a SharePoint site, Copilot can now:

• Create Office files from your content. Select a report in a library and ask for an Excel workbook that analyses it, a Word summary drafted from it, or a PowerPoint deck for a management review, without opening any of those apps first.
• Build interactive dashboard reports. Point it at a list, a set of files or a whole folder and it produces an HTML dashboard with charts, summary tiles and working filters. Follow-up prompts refine it: add a measure, change the look, make it filterable by team. It can even combine two lists that share a common field, which previously meant lookup columns or an export to Excel.
• Tidy a library by conversation. Ask it to review a messy document library and it proposes a folder structure with a mapping of what moves where, then applies the reorganisation after you approve it.
• Add columns, views and rules. It can set up an approval-status view, group and highlight items, and create reminder rules, for example an email to the document owner a few days before a review date falls due.

It also still does the earlier work of creating sites, pages, lists and libraries. Rollout began in mid-June 2026 as an opt-out preview, included with the Microsoft 365 Copilot licence, on by default for licensed users, with daily and weekly per-user usage limits while Microsoft tunes capacity. It joins a licence that has quietly accumulated a whole roster of included agents this year.

Where it genuinely earns time

The pattern across all of these is the same: the content already exists, and the labour was always in assembling it.

• The month-end pack. A library of reports becomes a management summary, a deck and a dashboard without anyone copy-pasting between apps.
• The project or matter readout. A tracking list becomes a filterable dashboard for the Tuesday meeting, at risk items flagged, refined by prompt when someone wants a different cut.
• The legacy library. The tidy-up nobody has owned for three years becomes an afternoon of reviewing Copilot’s proposed structure and approving the moves, which also improves every other Copilot answer drawing on that content.
• The review cycle. Policy and document review dates get a view and a reminder rule in minutes, the kind of light process that previously never justified building a workflow.

For document drafting specifically, the same habits apply here as in Word: the better the source material, the better the draft, and the draft is not the document.

The four checks the demos skip

1. Where did the output land, and who can open it? Everything Copilot in SharePoint produces is a new file, saved somewhere in the site, sometimes the library you prompted from, sometimes the site’s default documents area or assets. That matters because the file’s permissions follow its location, not its source. A dashboard summarising a tightly permissioned list, saved into a broadly shared library, has just republished that data to a wider audience. Before sharing anything generated, check where it saved and who has access. This is the same discipline as our client data governance guide: the AI respects permissions when reading, so the exposure risk moves to what gets created and where it lives.

2. Dashboards are snapshots. Update, 8 August 2026: this is the check that has since changed. Dashboards built from lists are now live linked, refreshing from the source when opened. We cover the change in what shipped in August. The rule of thumb at the end of this check still stands. As first published: the HTML report is not wired to the list the way a Power BI report is wired to its dataset. When the data changes, the dashboard does not, until you ask Copilot to refresh it. For a readout prepared the day before a meeting, that is fine and fast. For a number people check daily, with scheduled refresh, row-level security and an audit trail, Power BI remains the right tool. The honest rule of thumb: Copilot dashboards for communication, Power BI for operations.

3. Check the figures before they travel. Generated reports read as finished, and that is exactly when checking stops. A summary built across several files can smooth over gaps, and a chart can present an extrapolated figure as confidently as a real one, for instance where the current year only has part-year data. Before a generated pack goes to management or a client, someone who knows the numbers should compare the headline figures against the source. Two minutes of checking preserves all of the time saved.

4. It arrives switched on. Because this is an opt-out preview, licensed users get it without anyone deciding they should. Admins can scope it with PowerShell, tenant-wide, allow-list or block-list by site, and sites using Restricted Content Discovery are excluded automatically. For most firms the sensible position is deliberate rather than default: enable it where the content is well managed, hold back the sites where permissions need attention first.

Rules by prompt are not a workflow strategy

The rules Copilot creates, reminders, approvals on a library, are real SharePoint rules you can inspect and edit afterwards, and for single-step nudges they are the fastest route there has ever been.

They are not a replacement for proper automation. A process with multiple steps, exceptions, escalations or systems outside SharePoint still belongs in Power Automate or a custom build, and the choosing the right route question is the same as ever: prompt-created rules for light touches, engineered workflows for processes the business depends on.

What to do with this

If your firm has Copilot licences, this is worth an hour of deliberate exploration rather than organic discovery: pick one well-managed site, try the month-end pack and one dashboard, and agree the checking habit before generated files start circulating. If your SharePoint is not in a state you would want AI assembling reports from, that is the readiness work to do first, and it pays back across every Copilot feature, not just this one.

We cover Copilot in SharePoint as part of Copilot training built around your own sites and documents. If you want a view on whether your tenant is ready for it, and which sites to enable first, book a consultation and we will look at it with you.

Sources checked

Last checked: 30 July 2026.

• Get started with Copilot in SharePoint (preview)
• What’s New in Copilot in SharePoint: July 2026