Where Are Power BI Comments Stored?

Ever left a comment on a Power BI report to highlight an insight, only to wonder, "Where does this comment actually go?" You’re not alone. It feels like a simple question, but the answer has important implications for how you collaborate, manage security, and back up your work. This article will explain exactly where your Power BI comments are stored and what that means for your workflow.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

The Short Answer: In the Power BI Service

Let’s get straight to the point: Power BI comments are not stored in your .pbix file. They live exclusively in the Power BI service (the cloud version you access through your web browser). More specifically, they are stored as metadata associated with your organization’s Power BI tenant.

Think of it like this: your .pbix file is the blueprint for your report - it contains the data model, queries, and visual layouts. When you publish it, the Power BI service uses that blueprint to build the interactive report online. The comments are an extra layer that gets added on top of that live report in the cloud. This separation is key to understanding how the feature works and why it’s designed for cloud-based collaboration.

How Power BI Manages Comments: A Deeper Look

When you add a comment, you’re not editing the report file itself. Instead, the Power BI service creates a record in its own internal database that links your text, your username, and a timestamp to a specific element within the service.

This linkage is very precise and can be tied to different levels:

• Dashboard Comments: Comments can be added to the dashboard as a whole. This is useful for general discussions about the overall set of KPIs.
• Report Page Comments: You can add a comment to an entire report page, providing context for all the visuals on that page. Everyone with access to the report will see this page-level comment thread.
• Visual-Level Comments: You can also attach a comment to a specific chart, table, or card. This is perfect for pointing out a specific data point, like an unusual spike in sales on a line chart.

When you use the @mention feature to tag a colleague, Power BI connects this to your organization's Microsoft 365 / Entra ID (formerly Azure Active Directory) account. This allows it to send a specific notification to that person, pulling them directly into the conversation right where it’s happening.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step-by-Step: Adding and Viewing Comments

Using the comment feature is straightforward. Here’s a quick guide to get started:

1. Add a Comment to a Report Page

• Open the report in the Power BI service.
• Look for the Comment button in the top action bar.
• Click on it to open the Comments pane.
• Type your message in the text box at the bottom. To notify a colleague, type "@" followed by their name.
• Click Post to add your comment. A speech bubble icon will now appear on the action bar to indicate there’s an active discussion.

2. Adding a Comment to a Specific Visual

• Hover your mouse over the visual you want to discuss.
• More options (...) will appear in the top-right corner of the visual. Click it.
• Select Comment from the dropdown menu.
• The same Comments pane will open, but now it’s specifically filtered to the visual you selected. Type your message and click Post.
• A speech bubble icon will also appear next to the visual’s title to show that comments exist on that specific element.

Navigating between these comment threads is just a matter of opening the main Comments pane and looking through the conversation, or clicking the speech bubble on a specific visual to jump right to that discussion.

Practical Implications: What This Means For You

Understanding that comments live in the service is more than just trivia. It has real-world consequences for security, backups, and how you manage your reports.

A Major Security "Gotcha": Comments and Row-Level Security (RLS)

This is arguably the most critical implication. Comments are not subject to a report’s Row-Level Security (RLS) rules.

Let's say you have a sales dashboard with RLS that only shows each sales rep their own performance data. If a manager, who can see all data, leaves a comment on a chart saying, "@sara, great job on driving $1.2M in sales for Region West," Sara will see that comment. However, if @dave, the rep for Region East, views the same report, he won’t see Region West's data, but he will see the manager's comment.

The comment text is visible to anyone who can view the report page, regardless of the data they see. Be extremely careful not to discuss sensitive numbers or PII in comments if your report is viewed by people with different levels of data access. Comments reveal context and information entirely outside of your RLS rules.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Collaboration Across the Team

Because comments are cloud-based, they are perfect for live collaboration. Multiple people can comment at the same time, @mentioning team members to pull them into the conversation instantly. The discussion stays right alongside the data, providing context that would be lost in long email chains or separate chat messages.

Importantly, the comment threads persist even when you refresh the dataset. The conversation remains tied to the report visual or page, not the underlying data it shows at that exact moment in time.

Backups, Versioning, and Moving Reports

Since comments are not in the .pbix file, your backup strategy needs to account for this. If you download a copy of a report from the service as a backup, that .pbix file will contain the data model and design, but zero comments.

All the discussion, context, and decisions documented in the comments are left behind in the service. For most teams, this isn’t a major issue, but for organizations with strict audit or documentation requirements, it’s something to be aware of. Microsoft does provide a Power BI REST API that technically allows you to programmatically retrieve comments, but this is an advanced solution requiring development resources.

This also affects moving or copying reports. If you publish a report to "Workspace A" and a team has a long discussion there, and then you use the "Save a copy" feature to put that same report into "Workspace B," the comments from Workspace A will not travel with it. The copy is a new artifact in the service and will have its own empty comment thread.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Why Is It Designed This Way?

Microsoft’s decision to keep comments separate from the .pbix file was intentional and provides several benefits:

• Keeps Files Lean: Imagine if hundreds of comments were embedded directly into your .pbix file. It would become bloated and unwieldy, slowing down performance in Power BI Desktop. Separating them keeps the core design file clean and fast.
• Enables Real-Time Collaboration: The core purpose of comments is collaboration. This is only possible if they are stored in a central, cloud-based location where multiple users can contribute in real-time. If comments were in a local file, you’d have constant versioning conflicts - imagine two people trying to add comments to the same file on their respective desktops.
• Foundation for Scalability: Storing comments as service-level metadata allows for better overall system management and paves the way for future administrative features like auditing, search, and moderation across an entire Power BI tenant.

Final Thoughts

Your Power BI comments are stored safely in the Power BI service, operating as a distinct metadata layer on top of your reports and dashboards. While this design is great for collaboration, it's crucial to be mindful of its security implications with RLS and to remember that comments don't travel with .pbix files for backups or moves between workspaces.

Manually building reports in tools like Power BI is often just the opening act for ongoing data conversations, but getting there takes a lot of time and technical training. We believe getting reports and insights from your business data should be as simple as having that conversation. With Graphed, you can connect sources like Google Analytics, Shopify, and Salesforce directly, and then just ask for the reporting you need in natural language. Instead of wrangling with complex tools, you just tell our AI what you want to see, and it builds interactive, real-time dashboards for you in seconds.