Microsoft gives Fabric data agents a native charting layer

Microsoft is upgrading the presentation layer of Fabric data agents, replacing their standalone chart renderer with Fabric Visuals, the same visualization foundation used by Fabric Apps and increasingly elsewhere in the platform. The change is in preview and applies to the visual responses that accompany answers to natural-language questions. Microsoft says the aim is more consistent formatting, legends, tooltips, markers and axis scaling across Fabric experiences.

What shipped

The data agent can now return line and multi-line charts, bar and multi-bar charts, stacked bars, pie charts, scatter plots, and area or stacked-area charts using the shared Fabric renderer. Microsoft says visual responses work across every source type currently supported by the agent: lakehouses, warehouses and Power BI semantic models.

No administrator switch is required. The agent decides when a visualization would help, including when a user asks for a chart, uses language such as “show me,” or poses a question the system judges clearer as a visual. Users can also name a preferred chart type in the prompt, while agent instructions can establish preferences for particular classes of questions. Microsoft says visuals are enabled by default in data-agent conversations.

Why it matters for NL2SQL teams

This is not a new text-to-SQL engine; it is a product-layer change after the query and answer are produced. But that layer matters in enterprise deployments. A conversational analytics tool that returns a correct table but makes users rebuild the result in a dashboard still leaves a workflow gap. Microsoft is trying to keep the question, result and interpretation in one surface while making the output behave more like the rest of Fabric. The company’s examples show natural-language requests producing multi-series line, clustered bar and stacked-area charts directly in the conversation.

The practical boundary remains important: a polished chart does not by itself establish that the underlying query, metric definition or selected source was correct. Teams evaluating the preview should therefore test visual rendering separately from semantic accuracy—especially axis choices, category ordering and automatic chart selection—while retaining their existing validation for generated answers. Microsoft positions the shared renderer as a foundation for richer tooltips, interactivity and accessibility improvements to come, but those additions are not part of the current announcement. The preview announcement describes rendering and supported chart types rather than changes to query generation or semantic validation.