Chart SharePoint List Data in 2026: Power BI, Excel and Native Options

For most teams, the best way to chart SharePoint list data is:

• Quick Chart web part for a small, simple chart on a modern SharePoint page;
• Excel with Power Query and PivotCharts for analyst-owned exploration;
• Power BI Desktop using the SharePoint Online List connector for governed, reusable dashboards; or
• SharePoint Framework when you genuinely need a custom interactive experience and can own the code.

The old SharePoint command Visualize the list or library is no longer a current option. Microsoft stopped new report creation on 11 November 2025 and made previously published reports unavailable from 11 December 2025.

Fact-checked against Microsoft Learn, Microsoft Support and the official Power BI retirement notice on 7 August 2026.

The short answer

Requirement	Start here
One simple page chart with modest data and limited interaction	SharePoint Quick Chart web part
Ad-hoc analysis by an Excel-skilled owner	Excel Power Query and PivotChart
Reusable model, measures, security, refresh and interactive reports	Power BI Desktop + SharePoint Online List connector
SharePoint list to Power BI semantic model through an export flow	SharePoint Export to Power BI where available
Bespoke interaction or visual integrated into SharePoint	SPFx custom web part

Do not choose from a list of 13 tools. Choose from the decision you need to support, the people who must see it and the person who will keep it working.

Start with the question, not the chart

Write the business question in one sentence:

• How many requests are open by department and priority?
• Is the backlog rising week by week?
• Which sites have passed their review date?
• How long does an item spend in each process stage?

Then define:

• the grain of one list item;
• the fields used for grouping and filtering;
• how blanks and cancelled records are handled;
• the reporting period and time zone;
• who may see the underlying records; and
• how fresh the result must be.

A polished chart cannot repair inconsistent choice values, text dates, duplicate items or an unclear definition of “open.”

Option 1: SharePoint Quick Chart web part

The Quick Chart web part is the lightest native option for a modern SharePoint page. It can display a simple chart from entered values or, in supported page/site scenarios, data from a list on the current site.

Use it when:

• the chart is simple;
• the audience already visits the SharePoint page;
• only a small number of categories are needed;
• limited filtering and modelling are acceptable; and
• the page owner can maintain it.

Avoid it when you need a semantic model, complex measures, row-level security, drill-through, large-scale transformation or a portfolio of related reports.

The attraction is low setup. The cost is limited analytical depth. Prove the web part against your page type and tenant before designing a dashboard around it.

Option 2: Excel, Power Query and PivotCharts

Excel is often the right middle ground. Power Query can connect to a SharePoint Online list, shape the data and load it into a table or Data Model. A PivotTable/PivotChart then gives an analyst a flexible view.

Use Excel when:

• one analyst or a small team owns the workbook;
• the analysis changes frequently;
• consumers can work with a shared workbook;
• refresh expectations are modest and understood; and
• you do not need a full Power BI governance model.

A maintainable Excel approach

1. Connect with the site root URL, not a copied list-view URL.
2. Select only the required list/table.
3. Remove unused columns early.
4. give data types explicitly, especially dates and numbers.
5. normalise choice, lookup and person fields as needed.
6. document filters for deleted, test or cancelled records.
7. create the PivotTable and chart from the shaped output.
8. record who refreshes the workbook and what credentials it uses.

Do not email uncontrolled copies of the workbook. Store it in a governed library and decide whether readers may inspect the underlying rows.

Option 3: Power BI Desktop and the SharePoint Online List connector

For a durable dashboard, Power BI is usually the strongest option. Microsoft’s SharePoint Online List connector is generally available. In Power BI Desktop or Power Query, provide the root URL of the SharePoint site and select the list.

Microsoft documents connector implementation 2.0 as generally available. It improves capability over the older implementation, but you should still validate list shape, person/lookup columns and refresh behaviour in your own environment.

Recommended build flow

1. In Power BI Desktop, choose Get data > SharePoint Online List.
2. Enter the site root, such as https://contoso.sharepoint.com/sites/Operations.
3. Authenticate with the intended organisational account.
4. Select the list in Navigator and choose Transform Data.
5. keep only required columns and set data types.
6. build a clear model rather than one giant flattened table where related sources exist.
7. create explicit measures for important business definitions.
8. publish to an approved Power BI workspace.
9. configure credentials/refresh and monitor failures.
10. share through Power BI permissions, an app or an embedded SharePoint report as appropriate.

Model the business rule explicitly

If “Open requests” means items whose status is neither Completed nor Cancelled and whose created date is before the reporting cut-off, encode and document that rule. Do not depend on a visual-level filter nobody can find later.

For a broader learning sequence, use our 12-week Power BI data analyst roadmap, which covers Power Query, modelling, DAX, report design, Service, refresh and security.

Embedding Power BI in SharePoint

Microsoft provides a Power BI report web part for modern SharePoint Online pages. Embedding makes the report available in the page context; it does not grant access.

Readers still need:

• permission to the report in Power BI;
• permission to the SharePoint page; and
• the required Power BI licence, unless the content is hosted in capacity that supports the relevant free-viewer scenario.

The report’s row-level security and data permissions still apply. Test as a normal reader, not only as the report owner.

The retired “Visualize the list” integration

Microsoft retired the Power BI integration that allowed users to choose Integrate > Power BI > Visualize the list (and the corresponding library experience) directly from SharePoint.

According to the official Power BI notice:

• from 11 November 2025, users could no longer create new reports with that integration; and
• from 11 December 2025, previously published reports from it became unavailable.

Do not tell users to look for the old command or promise that an older auto-generated report remains available.

What replaced it?

Microsoft documents a newer SharePoint Export > Export to Power BI experience that creates a Power BI semantic model from list data where the feature is available. This is not the same product path as the retired Visualize integration.

Use it when a quick semantic-model starting point fits, but still review:

• the generated fields and relationships;
• refresh ownership;
• workspace location and permissions;
• licensing; and
• whether the resulting model expresses the real business rules.

For important reporting, Power BI Desktop often gives the report owner clearer control over transformation and modelling.

Option 4: SharePoint Framework custom chart

An SPFx web part can read SharePoint data through supported APIs and render a bespoke chart. A library such as Chart.js may provide the visual layer, subject to your organisation’s dependency and licensing review.

Choose custom development only when a standard web part, Excel or Power BI cannot meet a concrete requirement—for example, a specialised interaction embedded in a working page.

The organisation then owns:

• secure API access and least-privilege permissions;
• pagination and list-threshold-safe queries;
• accessibility and responsive design;
• dependency vulnerabilities and upgrades;
• error, empty and loading states;
• deployment and tenant app-catalogue governance; and
• support when the original developer leaves.

“Free library” does not mean “free dashboard.” Maintenance is part of the product.

What about third-party SharePoint charting products?

Third-party web parts can be a sensible fit when they supply a supported no-code experience between Quick Chart and a custom SPFx build. Evaluate them on current documentation and a tenant trial, not an old list of product names.

Ask:

• Does it support your SharePoint Online experience and data sources?
• How does it query large lists and handle paging?
• Can it aggregate without downloading excessive rows to the browser?
• Does it respect the current user’s permissions?
• What data leaves Microsoft 365?
• Is it accessible and usable on mobile?
• How are updates, support and AppSource permissions handled?
• What happens to saved charts if the subscription ends?

Vendor availability and pricing change too quickly for a timeless ranking. Start with requirements, then verify a current shortlist.

Data-shaping traps in SharePoint lists

Person, lookup and managed metadata fields

These can arrive as structured values rather than simple text. Choose the stable identifier and display value deliberately. Names change; email addresses and IDs have different privacy and durability implications.

Choice columns

Small spelling/case differences fragment categories. Use governed choices where possible and decide how multi-select values should be counted.

Dates and time zones

SharePoint stores and displays dates with regional/time-zone behaviour. Decide whether a daily chart uses UTC, the site time zone or a business locale, and test around midnight and daylight-saving changes.

Versioning and history

A current list row usually represents current state. It does not automatically provide the event history needed to calculate time-in-stage or yesterday’s backlog. For trend reporting, capture a proper event/snapshot history or use an authoritative audit/process data source.

Large lists

The 5,000-item list view threshold is not a rule that Power BI can report on only 5,000 rows. It is an operational boundary that affects query design and views. Use indexed/filterable patterns, minimise columns, understand connector paging and test realistic volumes.

A production checklist

• The business question and measure definitions are written down.
• The list uses consistent field types and values.
• Test records and cancellations are handled explicitly.
• Permissions are tested as a reader.
• Refresh frequency and owner are documented.
• Failed refreshes alert somebody accountable.
• Licensing is confirmed for every viewer route.
• Mobile, accessibility, blank and error states are checked.
• The chart links back to operational detail where appropriate.
• A change process exists for the data model and report.

Frequently asked questions

Can Power BI connect directly to a SharePoint Online list?

Yes. Microsoft documents the SharePoint Online List connector for Power BI Desktop and Power Query. Use the SharePoint site root URL and select the list in Navigator.

Can users still use “Visualize the list” in SharePoint?

No. Microsoft retired that Power BI integration in late 2025. A separate Export to Power BI semantic-model experience may be available, or you can build through Power BI Desktop.

Does embedding a Power BI report in SharePoint give users access?

No. The user still needs SharePoint page access, Power BI report access and the applicable Power BI licence/capacity entitlement.

Keep the boundary clear

This guide compares supported approaches from current public documentation. It does not contain Collab365 performance tests or claim that one option fits every tenant. Microsoft features, licences and third-party products change; verify the current experience and prove refresh, permission and volume behaviour with your own data.

Join the SharePoint & Teams Admins Space for practical guidance on SharePoint reporting, governance and administration.

Sources

• Microsoft: SharePoint Online List connector in Power Query
• Microsoft: Create a report from a SharePoint Online list in Power BI Desktop
• Microsoft: Embed a report in SharePoint Online
• Microsoft: Create a semantic model from a SharePoint list
• Power BI Blog: Deprecation of Power BI integration within SharePoint Lists and Libraries