SharePoint Just leveled up: Copilot creates HTML Views!

What if opening a SharePoint list gave your team an interactive overview of what matters most? With the new capability demonstrated in this video, Copilot can generate HTML-based views directly inside SharePoint lists and document libraries. Describe what you want to see, and Copilot turns your data into a dashboard with summaries, visuals, search, and filters.

You do not need to write the HTML yourself. You explain the result you need in everyday language, review what Copilot creates, and ask for adjustments.

What makes this new capability special?

The important step forward is where the dashboard lives: it becomes a view within your list or document library. Users can select it alongside the existing views and return to it whenever they need an overview.

In my earlier examples, I created HTML dashboard apps connected to SharePoint list data. This new approach brings that experience directly into the list itself. The dashboard becomes part of the place where people already work with their information.

Think of an HTML view as a custom dashboard for your existing data. It can bring together headline figures, status summaries, charts, and searchable details in one screen. Your team gets a clearer starting point for understanding the information and finding what needs attention.

Example 1: Turn a SharePoint List into an interactive overview

The first example in the video uses a SharePoint list containing sample tenant data. The goal is to create a useful overview of those records, including their status and information worth investigating.

I open Copilot from the list and describe the view I want. A prompt for this scenario could be:

Build an interactive HTML view for this list. Summarize the records and their statuses, highlight anything that needs attention, and include useful charts, search, and filters. Save the result as a view in this list.

That last instruction matters: it tells Copilot to create the dashboard as a list view.

Copilot then asks a few follow-up questions to understand the purpose of the data and what the overview should prioritize. In the demonstration, I explain that the records are for training and demonstration purposes and choose a balanced focus for the recommendations.

The generated dashboard appears among the list's views. It provides an overview of the data and a searchable list of records. Searching for a particular tenant narrows the results, making it easy to move from the overall picture to an individual entry.

The View stays connected to your data

The dashboard remains connected to the underlying SharePoint list. You can update the source information and see those changes reflected when the view reloads.

To demonstrate this, I open the list in another browser window and change an item's status. Back in the dashboard, I switch to another view and then return to the HTML view. The updated value is now reflected in the overview.

This means you can keep using the dashboard as the list changes, without asking Copilot to rebuild it for every update. The video demonstrates the data updating when the view is reopened.

Example 2: Create a Dashboard for a Document Library

The same opportunity is available for document libraries. In the second example, I use a library containing flight accident reports and create a dashboard to help users explore the reports and identify those needing attention.

This example also shows another way to get started:

1. Open the document library and select Add view.
2. Choose the new Dashboard option.
3. Enter a name for the view, such as Overview, and select Create.
4. Copilot opens with a prepared dashboard request. Answer any follow-up questions to guide the result.

In this demonstration, Copilot asks which reports should be flagged for attention. I select both reports involving injuries and reports with processing exceptions.

The resulting view combines report statistics, visual summaries, and a searchable table. Users can apply filters to focus on specific categories, making it easier to find relevant reports and understand the collection at a glance.

Improve the result through conversation

The first version is a starting point. You can continue talking to Copilot to make the view more useful.

In the document library example, I notice that the dashboard needs direct links to the reports. When users find a relevant document, they should be able to open it immediately. A follow-up request could be:

Add a direct link to each document in the overview table so users can open the report from this view.

Copilot updates the view and turns the report numbers into clickable links. I test a link, and the document opens successfully.

This is a practical way to refine the experience: create a first version, try it as a user, and describe what would make it better. You can guide the result without editing the underlying HTML.

Make the Dashboard your default view

Once the dashboard works well, you can set it as the default view. In the list example, I choose Set current view as default, leave the list, and open it again. The HTML dashboard is now the first view displayed.

That can make a real difference for colleagues who are unfamiliar with the data. They start with a summary and clear ways to explore the information. Existing views remain available when they need another perspective.

Where could your Team use this?

The two examples suggest plenty of everyday possibilities:

• Project tracking: Show project statuses, upcoming deadlines, and items requiring attention.
• Request management: Help a team explore incoming requests by status, category, or priority.
• Customer overviews: Make account records easier to search and understand.
• Document reviews: Highlight review statuses and provide direct links to relevant files.

The best starting point is a simple question: What should someone understand when they first open this list or library? Use that answer to guide your prompt, then check that the generated figures, filters, and links work as expected.

Copilot-generated HTML views offer a new way to make SharePoint information easier to explore. Watch the video to see both examples, from the initial request to an interactive view that users can open directly from their list or document library.