How to Check Power BI Logs

When a Power BI report is taking ages to load or throwing unexpected errors, your first instinct might be frustration. But your next move should be investigation, and that's where logs come in. Digging into Power BI logs is the key to understanding exactly what’s happening behind the scenes. This guide will walk you through the different types of logs available, where to find them, and how to use them to troubleshoot issues, monitor security, and optimize performance.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Why Should You Check Power BI Logs?

Monitoring logs isn't just for when things go wrong, it's a proactive habit that helps you manage your entire Power BI environment. Think of it as a health checkup for your data analytics.

• Troubleshooting Failures: When a dataset fails to refresh or a report won’t render, logs provide detailed error messages that pinpoint the exact cause, saving you from hours of guesswork.
• Boosting Performance: Slow reports are a common complaint. Logs can help you identify which visuals are taking the longest to load or which DAX queries are inefficient, allowing you to optimize for a better user experience.
• Enhancing Security and Compliance: Audit logs show you who is accessing what, who is sharing reports, and who is changing settings. This is essential for maintaining data governance and meeting compliance standards.
• Understanding User Adoption: By analyzing activity logs, you can see which reports are most popular and which ones are being ignored. This insight helps you focus your development efforts where they matter most and provide targeted training to users.

The Different Types of Power BI Logs

Power BI offers several distinct logs, each serving a different purpose. Understanding the distinction is the first step to using them effectively.

• The Activity Log: The go-to resource for admins. It tracks user and admin activities within your Power BI tenant, such as viewing reports, creating workspaces, and refreshing datasets. It’s ideal for understanding usage patterns and general administrative oversight.
• Audit Logs: Housed within the Microsoft Purview compliance portal (formerly Microsoft 365), these are focused on security and compliance. They contain a detailed record of actions that can be used for formal audits, allowing you to see a comprehensive history of activities across your Microsoft 365 subscriptions, including Power BI.
• Performance Analyzer logs: This log is specific to a single report within Power BI Desktop. It records the performance of each individual visual, breaking down the time spent on DAX queries, visual rendering, and other processes. It’s your best tool for speeding up slow reports.
• Gateway Logs: For organizations using an on-premises data gateway, these logs are crucial for troubleshooting connection issues between your local data sources and the Power BI service.

Let's break down how to access and use each one.

How to Access and Use the Power BI Activity Log

The Activity Log provides a comprehensive view of activities happening across your tenant. You need to be a Power BI service administrator or have a Global Administrator role in Microsoft 365 to access it.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Using the Power BI Admin Portal

This is the most straightforward method for viewing recent activity.

1. Log in to the Power BI service (app.powerbi.com).
2. Click the Settings gear icon in the top-right corner and select Admin portal.
3. In the Admin portal, navigate to Activity logs.
4. You can filter activities by date (up to 30 days), user, or activity type. This interactive dashboard is great for quick spot-checks.
5. For more detailed analysis or for data older than 30 days, you can export the data to a CSV file.

For example, if you want to know who has been publishing new reports, you could filter by the activity "PublishReport" and see a full list of users and timestamps for the selected period.

Using PowerShell for Advanced Analysis

For more systematic or long-term monitoring, using PowerShell is a much more powerful option. It allows you to programmatically fetch activity data and store it for historical analysis beyond the 30-day portal limit.

First, ensure you have the Power BI Management module installed:

Install-Module -Name MicrosoftPowerBIMgmt

Next, you can connect to your Power BI account and run a script to pull the activity events. Here’s a basic script to get the last day's activities:

# Connect to your Power BI Service Account
Connect-PowerBIServiceAccount

# Set start and end dates for the data pull
$startDate = (Get-Date).AddDays(-1).ToUniversalTime().ToString("yyyy-MM-ddTHH:mm:ssZ")
$endDate = (Get-Date).ToUniversalTime().ToString("yyyy-MM-ddTHH:mm:ssZ")

# Retrieve the activity events
$activities = Get-PowerBIActivityEvent -StartDateTime $startDate -EndDateTime $endDate

# You can now export this to a CSV or analyze it directly in PowerShell
$activities | Export-Csv -Path "C:\Temp\PBI_Activity_Log.csv" -NoTypeInformation

This approach is perfect for building a historical archive of user activity, allowing you to track trends in adoption or investigate security incidents long after the fact.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Tracking Security with Audit Logs in Microsoft Purview

While the Activity Log is great for operational management, the official audit trail resides in the Microsoft Purview compliance portal. This is where you go for formal security audits and deep forensic investigation.

1. Navigate to the Microsoft Purview compliance portal. You will need appropriate permissions to access this.
2. In the left-hand navigation pane, select Audit.
3. On the Search tab, configure your search criteria:
4. Click the Search button to run the audit. The results will populate in the table below, showing the user, the activity performed, the timestamp, and other relevant details.

For instance, if a sensitive report was unexpectedly made public, you could search for "ShareReport" and "Create [public] link to report" activities to identify who took the action and when.

Speeding Up Reports with the Performance Analyzer

When users complain that a report is slow, the Performance Analyzer is your best diagnostic tool. It runs inside Power BI Desktop and breaks down how long each element of your report takes to load.

1. Open your Power BI file (.pbix) in Power BI Desktop.
2. Go to the View tab in the ribbon and check the box for Performance analyzer. This will open the Performance analyzer pane.
3. Click the Start recording button within the pane.
4. Now, interact with your report as a user would. Click on slicers, buttons, or navigate to different pages. Each action you take will be logged and timed.
5. You'll see a breakdown of the load times for each visual, split into three key categories:
6. You can click "Copy query" for any visual to see the exact DAX code being generated. You can then analyze this code in a tool like DAX Studio to further diagnose performance bottlenecks.

Checking On-Premises Data Gateway Logs

If your Power BI reports rely on an on-premises data gateway to connect to sources like a local SQL Server, troubleshooting connection failures requires looking at the gateway logs. These logs are stored directly on the machine where the gateway is installed.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

How to find gateway logs:

1. Open the On-premises data gateway application on the server where it's installed.
2. Go to the Diagnostics tab.
3. Click the Export logs button. This will package all the relevant gateway logs into a single .zip file on your desktop.

Within this package, you'll find different log files covering gateway configuration, query execution, and information requests. When a scheduled refresh fails, these machine-level logs are often the only place you'll find the detailed errors needed to resolve the problem.

Final Thoughts

Checking Power BI logs is a vital skill for anyone responsible for a Power BI environment. From using the Performance Analyzer to optimize a slow report to searching the Purview audit log to confirm data security, these tools give you the visibility you need to move from reactive troubleshooting to proactive management.

We believe that getting insights from your data shouldn't be a constant exercise in technical troubleshooting. While digging through logs can be necessary for complex tools, we built Graphed to remove this friction entirely for marketing and sales analytics. Instead of learning complex software, you can connect your data sources in one click and ask a question like, "Show me my campaign ROI from Facebook and Google for last month." We instantly build a live, shareable dashboard for you, freeing you up to focus on strategy, not server settings.