Can Copilot Cowork read files from SharePoint without uploading them?

Yes. Cowork's SharePoint integration lets you point at a library on a SharePoint site and Cowork pulls the files it needs directly. You do not upload anything to Cowork; the files stay in SharePoint and Cowork reads them in place. This matters for sensitive content and for keeping the source of truth in SharePoint rather than scattered across tools.

What kind of dashboards can Copilot produce from SharePoint files?

Self-contained interactive HTML dashboards with charts, navigation, tables, hover states, and conditional formatting. The output is one HTML file that can be opened in any browser. Charts use Chart.js or similar; navigation is sticky; the page is responsive. Same pattern works for ticketing data, sales pipelines, finance exports, compliance registers, anything that produces structured exports.

Can Copilot archive the source files after building the dashboard?

Yes. Add the archive instruction to the prompt and Cowork will create a dated folder in the library, move the source files into it after the dashboard is built, and report what it moved. Each file move requires explicit tool approval; you see the action and confirm before Cowork executes it.

Does Copilot Cowork apply branding to the dashboard automatically?

Only if you point it at a Design MD file. Without one, Cowork applies a clean default style. With a Design MD in the same workflow, the dashboard colours, typography, and component patterns match your brand. The Design MD pattern is covered in detail in /articles/copilot-cowork-powerpoint-design-md.

Why does Cowork ask for tool approvals?

Safety. Any action that creates folders, moves files, sends messages, or modifies data in your tenant requires explicit confirmation. You see exactly what Cowork is about to do and approve or cancel. This prevents unintended changes; Cowork can plan all it wants, but it cannot execute against your tenant without your go-ahead.

Can I run this dashboard on a schedule?

Yes. Wrap the whole workflow into a Cowork Skill, then schedule the Skill to run on a cadence. New files land in the SharePoint library; the Skill rebuilds the dashboard with the new data and archives the inputs. Monthly or weekly scheduled reporting becomes hands-off.

How big a dataset can Cowork handle?

In the demo, 22 files including spreadsheets and call transcripts. Cowork handles dozens of files reasonably; hundreds gets unreliable. For very large datasets, summarise or aggregate in SharePoint first (using a Skill or Power Query) and have Cowork build the dashboard from the aggregated data.

Build an interactive dashboard from SharePoint files with Copilot, no uploads

A SharePoint library full of monthly exports turns into an interactive HTML dashboard in under five minutes. Cowork reads the files directly from SharePoint (no upload), builds the report with charts and navigation, and archives the source files into a dated folder when it is done.

This is the no-friction pattern for monthly reporting. The data lives where it lives. The dashboard generates on demand. The cleanup happens automatically.

The setup

A SharePoint library called "ticketing system" holds the previous month's exports: ticketing data spreadsheets, phone call transcripts, and other system exports. The library has 22 files in total.

The goal: produce an interactive HTML dashboard covering operational performance, agent and team performance, customer and commercial metrics, ticket type analysis, sentiment scoring, and transcript-driven insights. Then archive the 22 source files into a folder named for the current month.

Manually, this would be a day of work for an analyst. Copying data from each Excel sheet into a reporting template. Building charts. Designing the layout. Saving. Moving the files. Confirming the move was clean.

With Cowork pointed at SharePoint, it is one prompt.

The prompt

The user opens Cowork and types a multi-part instruction.

"Use Work IQ to point at my SharePoint skills site. There is a library called ticketing system. Create an interactive HTML report based on the files there covering [section list]. After you've created the report, create a folder in the same library called May 2026 and move all the files into that folder. Use the Design MD file in the default documents library as the brand spec."

What this prompt does:

Tells Cowork where the source files are (SharePoint site, specific library)
Specifies the dashboard structure (the section list)
Tells Cowork what to do after the dashboard is built (archive folder + file moves)
Points at the Design MD for branding

Cowork plans the work, then starts executing. It loads the files from the SharePoint library, builds the dashboard, generates the HTML, applies the Design MD styling, then asks for approval before creating the folder and moving files.

The approval moments

Three tool approvals appear during execution.

Create folder. Before Cowork creates the May 2026 folder in the SharePoint library, it surfaces the action and asks for confirmation. You see the exact folder path and library; you click approve.

Move files. Same pattern for the file moves. Cowork moves 22 files in batches; you can approve each batch or set "always approve" for the session.

Download dashboard. The finished HTML file appears in Cowork's outputs folder. You download or share it from there.

The approval pattern matters because it prevents anything destructive from happening without your explicit consent. Cowork can plan all it wants — it cannot modify your tenant without you saying go.

What the dashboard contains

The output is a self-contained HTML file you can open in any browser, share via SharePoint, or embed in a Teams tab.

Sticky navigation. A left-hand panel that stays in view as you scroll the report. Sections accessible by click; current section highlighted.

Operational performance. SLA charts, resolution time stats, first-call resolution percentages, customer effort scores. All visualised as charts (Chart.js or similar) with hover states for detail.

Team performance. Per-agent metrics: tickets handled, calls handled, average resolution time, workload distribution. Includes a heat map showing the busiest periods.

Customer and commercial. Ticket type breakdown, demand mix, sentiment distribution, customer satisfaction trends.

Transcript insights. Themes from the call transcripts, common pain points, escalation triggers. Generated by Cowork reading the transcripts during the dashboard build.

Everything in one HTML file. No external dependencies. No database connection. You open it offline if you need to.

The Design MD shapes the output

Without a Design MD reference, Cowork applies a clean default style. With one, the dashboard colours, fonts, headings, and component patterns match your brand.

In the video, the Design MD lives in the SharePoint site's default Documents library. Cowork is pointed at it explicitly in the prompt. The dashboard that comes out uses the brand's colour palette throughout, the right typography, and the brand-consistent button and card styles.

The same Design MD that produces on-brand PowerPoint presentations (covered in the Cowork PowerPoint article) produces on-brand dashboards. One file, multiple output formats, consistent brand application.

Where this fits with Copilot in SharePoint

Cowork and Copilot in SharePoint are sibling products. Both use the same open Skills format. Both can read files from your SharePoint tenant.

The dividing line for dashboards:

Copilot in SharePoint is best for dashboards that live inside SharePoint, built by team members on the site, run on demand. The output stays in the SharePoint library.

Cowork is best for dashboards that need autonomous execution, long-running file processing, scheduled regeneration, or complex multi-file synthesis. The output can land in SharePoint, but the build runs in Cowork.

For a single-team monthly report on a known dataset, either works. For a cross-team analysis pulling from 20+ files with transcript synthesis, Cowork is the better fit because of the longer-running nature of the task.

Scheduling the workflow

The final pattern worth knowing: this becomes a scheduled task.

Wrap the entire workflow (read library, build dashboard, archive files, apply Design MD) into a Cowork Skill. Schedule the Skill to run on a cadence — first of every month, every Monday morning, every quarter end.

New files land in the SharePoint library during the period. The scheduled Skill picks them up, regenerates the dashboard, archives them, and surfaces the new HTML in the outputs folder.

The team's monthly report becomes a thing that happens, not a thing somebody has to remember to produce.

What to do this week

If your team produces structured reports from SharePoint files monthly or weekly, three actions.

Identify one report that runs on a regular cadence and consumes structured files. Ticketing, finance, projects, compliance. Anything where the inputs land in a SharePoint library and the output is a report or dashboard.
Try the manual version once in Cowork. Open Cowork, point at the SharePoint library, describe the dashboard. See what comes out. Iterate on the prompt until the output is what you want.
Wrap the working prompt into a Cowork Skill. Schedule it. The report runs itself from then on.

The combination of Cowork's autonomous execution and a SharePoint library full of structured inputs is the closest most teams will get to genuinely automated reporting. The setup work is short; the payback compounds every reporting cycle.

For a specific ticketing-system worked example with 1,000 tickets and 500 call transcripts, see the Cowork ticketing dashboard article.

For organisations rolling Cowork and Copilot in SharePoint out together, the Copilot in SharePoint Immersive covers the cross-product patterns in detail.