Copilot builds the first draft of a dashboard in minutes. This guide covers the steps, the prompts, and the checks that make it safe to share.
A Copilot dashboard looks finished within minutes, and that is the reason to slow down on two things: whether the numbers are right, and who can open the file. The building part is easy. Describe the charts, headline figures and filters you want, and Copilot produces something that looks like a reporting tool.
There are three different ways to get there, and they behave differently. Copilot in Excel builds charts, PivotTables and dashboard sheets inside your workbook. Copilot in SharePoint can build an interactive HTML dashboard from an Excel file, and, according to practitioners who have used it, from a Microsoft List that stays connected to its data. A video from Scott Brant (Your 365 Coach), published October 12, 2026, walks through the HTML route using invoice data and then a List, and it is a useful outline for the steps below.[4] I could not access its transcript, so this guide follows its chapter structure and checks every claim against Microsoft’s documentation or says plainly where only practitioners report it.
The sections below take you through choosing a route, preparing the data, building and refining the dashboard, deciding between a snapshot and a live connection, and checking the result before it goes to anyone else.
Start by deciding who needs to see the dashboard and how fresh the data has to be. Those two answers pick the route.
| Route | What you get | Data freshness | Best for |
|---|---|---|---|
| Copilot in Excel | Charts, PivotTables and a dashboard sheet inside the workbook, linked to the source data and editable.[1] | Updates as the workbook does | Analysts and managers who already work in the file |
| HTML dashboard from an Excel file | An interactive HTML file with charts, headline figures and filters, saved in SharePoint. | A snapshot, unless you ask for and test a live link | A one-off readout for a meeting or a deadline |
| HTML dashboard from a Microsoft List | An interactive HTML file reported to stay connected to the List. | Refreshes when opened, per the practitioner reports | A shared tracker, such as a pipeline or a request log |
A Future Factors comparison. The HTML routes depend on Copilot in SharePoint, a Microsoft 365 Copilot license to create or edit, and rollout status in your organization.
If you are unsure, begin in Excel. The workbook route keeps the data where it already is, and nothing leaves the file until you decide to share it.
Copilot reads your data the way a new colleague would, so ambiguity in the data becomes ambiguity in the dashboard. The video places data preparation first, before any prompt, and that order is right. Five minutes of cleanup prevents most of the wrong totals people blame on the AI.
Take out anything the audience should not see. A column you leave in the data may end up in the dashboard file, which matters a great deal in the HTML route, covered below.
In Excel, open the workbook, open Copilot and use edit mode, which Microsoft describes as the default. In that mode Copilot can create and edit charts, PivotTables and shapes with editable links to the source data, and Microsoft says it can make dashboards and planning tools from scratch.[1] Chat mode only analyzes your data and does not change the workbook, so check which mode you are in before you ask for a build. Edit mode works on Windows, Mac and the web, while iPhone and Android support chat mode only.
Ask for the dashboard in parts instead of one long request. First ask for the headline figures, such as total invoiced, total paid and total overdue. Then ask for two or three charts that answer named questions: how revenue moves by month, which customers carry the most overdue balance, and how invoice status splits. Then ask for a filter or slicer on the field people will use most. Each step is easy to check, and a wrong total is easy to trace to the step that produced it.
Microsoft does not state a table-format requirement on its Excel page, but a clean table range is still the safest input. Use the Stop button if Copilot heads somewhere you did not intend; Microsoft notes you can stop or pause it at any time.[1]
The HTML route produces a single interactive file with charts, headline figures and filters. Microsoft’s documentation for HTML pages in SharePoint says Copilot can create a page from a prompt, that the draft opens in edit mode, and that you should confirm it saved to the Site Pages library.[2] Creating or editing with Copilot needs a Microsoft 365 Copilot license. Uploading, viewing and sharing do not. HTML pages are on by default, but a site owner can turn them off, and some features roll out gradually to organizations in the Frontier program.
The Build Loop below is the sequence I would follow. It mirrors the chapters of the video: prepare the Excel data, prompt for the dashboard, explore it, then edit it with follow-up instructions.
A Future Factors framework, not a Microsoft process. Steps 4 and 5 are where most dashboards go wrong, so they get their own sections.
The prompt matters more than anything else you do. A practitioner who walked through the SharePoint version found that a prompt without a save location produced an HTML file that downloaded to the desktop, so name the document library in the request.[6] The same author notes that your wording decides whether you get static values or a live feed, so say which you want.
| Build an interactive HTML dashboard from [file or List name] and save it in [named document library]. The audience is [role] and the decision it supports is [decision]. Use these columns: [list]. Definitions: [what overdue, revenue and so on mean]. Show headline figures for [three measures]. Add [two or three charts, each phrased as a question]. Add filters for [fields]. Keep the layout simple with readable contrast and a title that states the date range. Tell me which parts of the data are embedded in the file and which are read from the source. |
Copy and fill in the brackets. The last sentence makes Copilot state what it embedded, which is the fact you need for the sharing decision.
Refine with single changes. Ask for a different chart type, then a colour change, then a filter, and test after each one. If a follow-up breaks something that worked, you know which instruction did it.
The video spends several chapters on the difference between a dashboard built from Excel data and one connected live to a Microsoft List, and on what each means for security when the file is downloaded or shared.[4] It is the most important decision in the build.
A snapshot dashboard carries a copy of the data inside the file. A practitioner describes this as baking the rows into the file, so that anyone who can open it can read every row, whatever the List permissions say.[5] A live dashboard reads from the source when it is opened, so changes show up without rebuilding anything, and access follows the permissions on the source, as reported in the video summary I could access.
Treat a static dashboard as a copy of its data, and share it only with people who could see every row.
| Question | Snapshot (static) | Live (connected) |
|---|---|---|
| How fresh is the data? | As of the day you built it | As of the last refresh when opened |
| Who can read the underlying rows? | Anyone who can open the file | Depends on permissions on the source |
| What do you prompt for? | Embedded values; works offline | A connection to the List or file, stated in the prompt |
| What can go wrong? | Stale numbers; copied data leaving the team | Broken refresh; permission gaps; changes needing a re-prompt |
| Use it for | A dated readout with non-sensitive data | A tracker people check repeatedly |
Based on the video’s chapters and two practitioner write-ups. Test the behavior in your own tenant before relying on it.
One caution on live connections. Microsoft’s HTML page documentation says SharePoint blocks arbitrary fetch requests and outbound API calls from HTML pages, and that pages run in a sandboxed frame.[2] My reading is that a live link therefore depends on Copilot’s own List and file connection, and not on code you add to the page yourself. Microsoft’s August 2026 SharePoint update describes live dashboards connected to lists and files, but the body of that post would not load for me, so confirm availability and behavior in your organization. Then run the test the video recommends: change a record in the source and see whether the dashboard updates.
An AI-generated dashboard can be wrong in ways that look right. Copilot can misread an ambiguous prompt or produce a misleading total from inconsistent data, and the video’s own advice is to test every dashboard Copilot generates before it is shared. The check below is short enough to do every time.
Before sharing, recompute three numbers by hand from the source and match them to the dashboard.
| Check | How | Pass when |
|---|---|---|
| Totals | Recompute three headline figures from the source with a filter or formula | All three match exactly |
| Filters | Apply each filter and count the rows it should leave | Counts match the source |
| Date range | Read the title, axes and the first and last data points | They match the data you meant |
| Labels and definitions | Check each chart title and the definition of overdue, revenue or similar | A reader would not misread them |
| Hidden data | Open the file as a viewer would and look for columns you did not intend to show | Nothing sensitive appears |
| Refresh | Change a source record and reopen (live dashboards only) | The change appears |
| Accessibility | Check text contrast, keyboard use and chart labels | Readable without a mouse or color alone |
A Future Factors checklist. Accessibility, contrast and alt text depend on what the model generated, so the owner has to test them.
Who runs the check depends on the dashboard. A finance analyst should recompute against the ledger, a project manager against the tracker, an HR partner against the HRIS export, and a sales operations lead against the CRM report. The person who owns the number is the person who signs off the dashboard.
Sharing is where the earlier choices come due. Microsoft states that publishing a page makes the current version visible to people who already have permission to view it, and does not grant new permissions.[2] Viewing and sharing an HTML page do not require a Copilot license, which fits the video’s note that colleagues can view a shared dashboard without a paid Copilot license. So the dashboard can travel further than the license, and the data travels with it if you chose a snapshot.
Before sharing, work through the same questions each time. Where is the file saved, and who can reach that location? Does the person you are sending it to have a right to every row in the data? Can the file be downloaded, and would a downloaded copy be a problem? Is anything in the data, such as salaries, personal details or client names, that the dashboard does not need? If the answer to any of these is unclear, build a live version or a smaller extract and share that instead.
Branding and maintenance are worth knowing about as well. A practitioner notes that an HTML file does not inherit the tenant theme, and that changing it later means re-prompting Copilot or editing raw markup instead of editing a web part.[5] For a quick readout that is acceptable. For a dashboard that must persist, many teams will prefer a governed reporting tool, which is covered next.
A Copilot-built HTML dashboard suits quick, disposable readouts: a monthly review, a deadline tracker, a one-off board slide. It is a poor fit when the numbers drive decisions that need an audit trail, when the data is regulated or highly sensitive, when many people depend on it every day, or when the definitions must be identical across teams. In those cases use your organization’s governed reporting setup, and use Copilot to draft the questions and the layout instead of owning the numbers.
Microsoft’s HTML page documentation also lists limits worth knowing before you promise anything: an upload limit of 10 MB for the HTML, no co-authoring, no comments and reactions, and only Microsoft-managed versions of libraries such as Chart.js, Mermaid, React, Fluent UI and Babylon.[2] A decision rule helps: if the dashboard will be opened once or twice and then retired, build it with Copilot. If it will be opened every week, plan for an owner, a refresh schedule and a place for questions about the numbers.
Here is a 30-minute first build on a small, non-sensitive dataset. It gives you the whole loop without risking real data.
| Minutes | Step | Output |
|---|---|---|
| 0 to 5 | Pick a small dataset of 50 to 200 rows with no personal data and fix names, categories and dates | A clean table |
| 5 to 12 | Use the prompt blueprint to build the dashboard, and ask Copilot to state what is embedded | A first version |
| 12 to 20 | Refine with one change at a time and test each filter | A version you understand |
| 20 to 26 | Run the pre-share check, recomputing three numbers by hand | A checked dashboard |
| 26 to 30 | Decide snapshot or live, who can see it, and who owns the numbers | A sharing decision in writing |
A Future Factors exercise. Dates and numbers in your own data will differ, so keep notes on what you changed.
Keep three things from the exercise in a note next to the file:
By the end of the half hour you will know whether the route fits your work, and you will have the habit that matters: no Copilot dashboard goes out until three numbers match the source and someone has decided who can open it.
Yes. Microsoft says Copilot in Excel can create and edit charts, PivotTables and shapes with editable links to the source data, and can make dashboards and planning tools from scratch. Use edit mode, which lets Copilot change the workbook. Chat mode only analyzes and does not edit.
Microsoft says creating or editing an HTML page with Copilot needs a Microsoft 365 Copilot license, while viewing, sharing and publishing do not. Viewers still need permission to reach the file. Check who can open it before you share, because the data inside a static file can be read by anyone with access.
A static dashboard embeds a copy of the data at build time, so it does not update and anyone who opens the file can read the rows. A live dashboard reads from the source when opened, so it refreshes and follows the source’s permissions, according to practitioner reports. Test refresh and access in your own tenant.
Recompute three headline numbers from the source by hand, apply each filter and count the rows, and read the date range and chart labels. Wrong totals usually come from inconsistent data, such as mixed statuses or blank dates, so clean the data before you prompt.
Use a governed reporting tool when numbers drive decisions that need an audit trail, when the data is sensitive or regulated, or when many people depend on the dashboard daily. A Copilot-built HTML dashboard suits quick, disposable readouts with an owner who checks the numbers.
This guide was written by Sana Mian, Co-Founder of Future Factors AI, using the Future Factors approach of treating AI output as a draft that a named person checks. It was prompted by a video from Scott Brant (Your 365 Coach), published October 12, 2026. YouTube blocked access to the transcript, so I used only the video’s title, description and chapter list, quoted nothing from it, and wrote all prompts myself. Claims about Copilot in Excel and HTML pages in SharePoint come from Microsoft Support pages read on October 16, 2026. Microsoft’s August 2026 SharePoint update, which describes live dashboards connected to lists and files, could be read only in summary, so the live List behavior here rests on that summary and two practitioner write-ups. I have not tested these features, features roll out gradually and can differ by organization, and Microsoft updates the pages often, so confirm current behavior before building on it. The Dashboard Build Loop and the pre-share check are Future Factors working tools, not Microsoft processes.
Weekly tips. Real examples. Practical help for busy professionals.
We care about your data, check out our privacy policy.