Consider a BI workspace when the dataset, semantic model and access requirements fit.
Start with the finished task
Define the unit, time period and denominator before asking AI for a visual. A plausible explanation cannot repair an axis that exaggerates the difference.
- 1Check totals in the source
Check totals in the source before rendering.
- 2Show missing observations explicitly rather
Show missing observations explicitly rather than converting them to zero without justification.
- 3For a trend, use ordered
For a trend, use ordered time values; for category comparisons, keep units consistent.
- 4Save the data transformation alongside
Save the data transformation alongside the chart so a colleague can reproduce it.
Choose a workflow that fits
Use a simple chart for a small, fixed comparison. Avoid accepting a generated narrative without checking totals, missing values and whether the chart type fits the question.
| Tool | Source evidence | Confirm before buying |
|---|---|---|
| Microsoft Power BI ↗ | Microsoft documents Copilot in Power BI and its requirements. | Capacity, tenant settings and the supplied data model. |
| Manual or conventional route | Use a spreadsheet chart when the dataset is small and the arithmetic can be inspected directly. | Editorial workflow advice; this is not a measured comparison or vendor performance claim. |
The correction in our worked example
The initial claim confuses visual height with relative change. The corrected arithmetic is 10 divided by 100.
Fictional store records 100 orders in week A and 110 in week B. A bar chart starts its axis at 95.
Orders doubled because the second bar looks twice as tall.
Orders increased by 10, or 10%. Use a zero baseline for this bar comparison and label the same weekly period for both values.
Build and inspect the handoff
Check totals in the source before rendering. Show missing observations explicitly rather than converting them to zero without justification. For a trend, use ordered time values; for category comparisons, keep units consistent. Save the data transformation alongside the chart so a colleague can reproduce it.
Check the denominator and axis
Recalculate the percentage from the supplied values. Show whether the chart uses counts or rates, and inspect whether axis choices exaggerate a small change. Use a spreadsheet chart when the dataset is small and the arithmetic can be inspected directly.
Compare the full cost
BI licensing and AI capacity may be separate from spreadsheet access. Price the actual required workspace, not a consumer-chat subscription that lacks the necessary integration.
Workflows questions
Can a chart narrative be checked without the data?
Only partially. Verify the underlying values, units and transformations before relying on the narrative.
When is a simpler workflow a better choice?
Use a spreadsheet chart when the dataset is small and the arithmetic can be inspected directly.
THE RESEARCH DESK
Sources & methodology
Official documentation was consulted on 2026-10-07. The worked example uses fictional inputs and was edited for this guide. No vendor application benchmark or outcome test was performed. Prices and allowances should be confirmed before purchase.
learn.microsoft.com · copilot-introduction↗Put this guide to work
Your decision criteria: Capacity, tenant settings and the supplied data model.
- Fictional store records 100 orders in week A and 110 in week B. A bar chart starts its axis at 95.
- Recalculate the percentage from the supplied values. Show whether the chart uses counts or rates, and inspect whether axis choices exaggerate a small change.
- Capacity, tenant settings and the supplied data model.
AI tools for HR: build a checked onboarding handoff →
AI tools for LinkedIn: improve a profile without inventing a career →