Edit

Share via


Summarize a report with Copilot

APPLIES TO: Power BI Desktop Power BI service

Important

The features mentioned on this page are coming soon for the Power BI service. See the Fabric Roadmap for timeline details.

Copilot lets you create insightful summaries about their reports. Copilot takes the visuals that were curated and built by report authors and generates summaries, overviews, insights and answers grounded in the report data. You can access these summaries in the Copilot report pane or in the standalone Copilot agent in Power BI.

Screenshot showing select Enter and watch Copilot generate your summary.

Screenshot of Copilot showing spending patterns as a report summary.

Note

Why summarize a report?

When working with a Power BI report filled with visuals, users often spend anywhere from 30 minutes to several hours analyzing the data to understand key questions, insights, and high-level trends, especially when preparing summaries for leadership. This might involve digging through multiple pages of visuals, identifying patterns, noting anomalies, and drafting a narrative that explains what’s happening in the data and why it matters. Whether you're summarizing for an executive briefing, preparing talking points for a stakeholder meeting, or trying to get a quick grasp of the data to inform a business decision, the process can be time-consuming.

The summary capability in Copilot lets you generate a concise summary of the report’s data in seconds, whether you’re in the report or asking about the report data in the standalone experience. Summaries highlight key trends, insights, and potential issues, helping you quickly answer core business questions and decide on next steps without needing to manually interpret every chart or rely entirely on an analyst for support.

Get started in reports with standard prompts

Let’s begin with the report experience. Here, you’re inside of a Power BI Report that has access to Copilot. To get started, select the Copilot button in the ribbon in either Power BI Desktop or the Power BI service. In the service, the button is available in both edit mode and view mode.

Tip

If you don't see Copilot, your admins might not have enabled it, or you could be in a workspace that doesn't meet the Copilot requirements.

Screenshot showing select the Copilot button in the ribbon in either Power BI Desktop or the Power BI service.

The Copilot pane opens.

Screenshot showing the Copilot pane open.

You can choose from suggested prompts of summaries from the main Copilot menu such as "What is this report page about?” or “Prep a summary for my team.”

Or you can select other prompts from the user prompt guide in the lower left-hand corner of the dialogue input box.

Screenshot showing select prompts from the user prompt guide.

After you choose a prompt, select Enter and watch Copilot generate your summary.

Screenshot showing and updated view of the report summary response.

Copilot uses Azure OpenAI to look at the visual metadata on the report and create a natural language summary. It doesn't take into account data that's not currently visualized in your current view, for example data hidden behind filters or slicers that aren't currently applied. By default, Copilot summarizes visuals across the entire report. You can adjust the scope of the summary by specifying the prompt.

Citations

In a summary response from the Copilot pane, citations are provided within the summary to indicate which visuals Copilot referenced to generate the summary. These citations help you quickly cross-check the summary output to ensure accuracy, increasing productivity. If a reference is from a page you aren't currently on, the reference takes you to that page when clicked.

Screenshot showing that footnotes are provided within the summary to indicate which data visuals Copilot referenced to generate the summary.

Custom prompts

The benefit goes beyond providing a generic summary for a consumer. You can type custom prompts to request a specific summary, such as a bulleted list or a summary specifically about sales, or about another nuanced slice of your data.

Screenshot showing type custom prompts to request a specific summary.

Copilot allows you to generate a custom summary to fit your business needs. Here are some examples of custom summaries:

  • Give me a summary of my revenue over the last fiscal year and describe any significant outliers.
  • Summarize the trends that are shown across this report.
  • Outline the insights about bike sales and Washington.
  • Summarize the data in a way that allows me to use it in an email to leadership.
  • Summarize the data specific to Seattle, WA.

Tip

For nuanced summaries about filtered data, filters and slicers must be applied in the report.

Benefits

This customization allows you to focus on nuanced aspects of the data that are relevant to your objectives or questions. Some key advantages include:

  • Relevance: Customized summaries ensure that the information provided is directly aligned with your specific inquiry or area of interest, making the insights more relevant and actionable.
  • Efficiency: You can quickly obtain targeted information without sifting through irrelevant details. This streamlines the decision-making process and enhances overall efficiency.
  • Personalization: Customized summaries cater to individual preferences and priorities, providing an experience personalized for you. This personalization fosters a sense of ownership and engagement with the data.
  • Precision: You can receive precise details on the metrics or dimensions that matter most to you, allowing for a more detailed and nuanced understanding of the data.
  • Improved decision-making: Customized summaries empower you to make informed decisions based on specific, tailored insights, contributing to more effective and strategic decision-making.
  • Flexibility: You have the flexibility to adapt the summary to changing business needs or evolving questions, ensuring that the insights remain pertinent over time.

Answer questions about your report content in the Copilot pane

The Copilot pane also allows you to ask specific questions about your report content and receive a summarized response. This allows you to not only request summaries but ask additional follow-up questions about your report or about a summary you've received. The Copilot pane generates an answer that contains visual references within the report. You can ask fact-based questions from the report.

Examples of questions you can ask

  • Which team had the highest sales?
  • What was the spend per visitor for Maui in November 2023?
  • What is the value for revenue variance?
  • Which product had the highest profit margin?
  • What is the difference in revenue by product streams, and are they statistically significant?

Get started in the standalone Power BI Copilot experience

Now, let’s take a look at the standalone Copilot experience. For more details, see Standalone Copilot experience in Power BI (preview). Although the core functionality remains the same, this version includes some enhanced features that are unique to the standalone experience.

Screenshot of the standalone Copilot experience in Power BI, showing a chat interface for interacting with data.

To get started, select the Copilot button in the left navigation menu in Power BI service. You see a landing page that offers helpful prompts to get started exploring data. This is similar to the starter prompts shown in the report pane, but using these lets you search for relevant reports you have access to. This means you don’t need to start the exploration experience in the context of the report, you can just ask Copilot to find it for you.

Tip

If you know the report you want to explore, attach it in the Add items section.

In this standalone Copilot experience, you can ask to summarize data, generate insights, or create executive overviews based on your Power BI reports. You can also ask follow-up questions, use custom prompts, continue the conversation, and jump directly into the report for deeper analysis when needed.

One key difference in this experience is the way visuals are embedded directly into the summary responses. Unlike report summaries, where visuals remain part of the main report view, the standalone experience presents them alongside the text. Visual citations are especially important here; they let you validate the data in the summary, see the original visual it references, and explore further without leaving the Copilot view. The overall layout reads more like a newspaper article, combining narrative and visuals into a single, digestible format.

Screenshot showing the full immersive summary in Copilot.

You can even hover over some of the additional visual citations that aren't rendered inline to make sure you have a good understanding of which visual the information in the summary came from.

Screenshot showing what happens when users hover over citations in the full immersive summary in Copilot.

In this immersive experience, you can also dive deeper into the visuals provided to continue your analysis - another key difference from the Copilot pane in the report view. Use the Explore buttons under the visuals to open them in a format that supports deeper exploration, allowing you to slice, dice, and interact with the data more directly.

Screenshot showing what happens when users explore in the full immersive summary in Copilot.

Best practices

To get the most accurate and useful results from Copilot summaries and responses to your report questions, it’s important to optimize your report data. The following are some best practices to make sure Copilot works effectively when delivering report summaries and answers.

How Copilot summarization works

Copilot summaries are based on the report’s visualized data and follow a two-step process:

  1. Identifying relevant visuals (up to 20) based on the user’s prompt, then
  2. Summarizing the data from those visuals

The quality of the results depends heavily on the amount of data and the clarity of labels. When Copilot resorts to sampling due to volume, accuracy may decrease.

Report composition

  • Limit the number of visuals on a report page to improve accuracy. While Copilot can rank visuals from reports with hundreds of visuals, it summarizes from only the top 20 so some insights may be missed.
  • Avoid duplicate visuals that present the same data. Exception: visuals showing data at different granularities for the same insight.
  • Prioritize distinct, simple visuals per insight rather than a single, complex visual showing everything.
  • Leverage default filters that reveal data to answer most commonly asked questions, as summaries don't currently apply filters to answer the specific prompt.
  • Use clear, descriptive titles for pages, visuals, and filters.
  • Ensure the fields have meaningful names, even if they're not displayed on the chart.

Visual composition

  • Visuals with expandable elements (like decomposition trees or matrices) are summarized in their current state. For example, if only one country is expanded in a matrix showing Country > City, Copilot only sees cities for that country. Set the default expansion thoughtfully.
  • Avoid overly complex matrices with many row levels or multiple values. Use simpler, supporting visuals to highlight key takeaways from those complex visuals.
  • The simpler the visual, the easier it is to summarize. Use cards to surface key high-level insights.

Data volume and token usage

  • Visuals might not send all data. For example, tables paginate after 100 rows, and only visible rows are summarized. If full summarization is important, reduce the data shown by using filters, trimming columns, or splitting data into multiple visuals (see limitations).
  • Avoid high-density visuals, like daily line charts spanning years. Instead, aggregate data by week or month (see limitations).
  • Hidden elements like tooltips are also included in what Copilot sees, which can increase token usage.
  • Limit the number of series in categorical charts (fewer than 10). Use an "Other" bucket for small categories. Too many series can result in wide, hard-to-parse tables.
  • Use display units where possible. For example, show "1.2K" instead of "1,234" unless high precision is necessary.
  • Avoid large text fields. Any text longer than 500 characters are truncated.

Limitations and considerations

The following are limitations and considerations across both experiences (also see the best practices section).

  • Filters and slicers aren't yet supported in summary experiences (you can't filter data with the user prompt).
  • For the Copilot button to be available, the report needs to be in:
    • An eligible workspace: the workspace needs to have a paid dedicated Fabric capacity.
    • A tenant where the admin settings are enabled.
  • Copilot summaries only consider visuals with less than 30K rows of data. If more data is included in visuals, Copilot answers using the semantic model itself, not the report visual.
  • Copilot summaries may not work accurately on table/matrix visuals with more than 500 rows. If the visual surpasses 100 rows, Copilot answers using the semantic model itself, not the report visual.
  • Answering specific report questions isn't yet supported in the standalone Copilot experience.

Send feedback

We always welcome your feedback about our products. Your feedback helps us improve the product.

Next steps