How Many Schedule Refreshes in Power BI?

Cody Schneider8 min read

Knowing how often your Power BI reports are updating is essential for making timely decisions. The number of automated refreshes you can schedule depends entirely on your type of license and the capacity your workspace resides on. This article breaks down the refresh limits for each Power BI plan and shows you exactly how to set up, manage, and even get around the usual restrictions when you need faster data updates.

GraphedGraphed

Still Building Reports Manually?

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

Watch Graphed demo video

Understanding Power BI Refresh Limits: Capacity is Everything

The core concept to grasp is that your refresh limit isn't just tied to your user license (like Pro or Premium Per User), it's determined by the underlying compute capacity where your data resides. Power BI has two main types of capacity: Shared and Premium.

Shared Capacity: For Power BI Pro and Free Users

If you're using a Power BI Pro or Free license, your projects are published to a shared capacity. This means you share computing resources with many other Microsoft customers. To ensure a fair experience for everyone, Microsoft places stricter limits on how often you can refresh your data.

  • Limit: Up to 8 scheduled refreshes per dataset per 24 hours.
  • Minimum Time Interval: Refreshes must be scheduled at least 30 minutes apart. Even if a refresh fails, it still counts toward your daily limit. Manual, on-demand refreshes also count against this same limit.

For many businesses, 8 refreshes - occurring roughly every three hours during working hours - is plenty. You can set a refresh before the workday starts, a few times throughout the day, and one at the end of the day to ensure stakeholders have a recent view of performance.

Note: While the Power BI Free license operates on shared capacity, it's designed for personal use. You cannot share reports with others who don't have a Pro or PPU license, which makes it less common for business reporting scenarios.

GraphedGraphed

Still Building Reports Manually?

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

Watch Graphed demo video

Premium Capacity: For Premium and PPU Users

When your organization subscribes to Power BI Premium (either Per User or a dedicated capacity), you get access to dedicated computing resources. Because you aren't sharing power with other companies, Microsoft significantly raises the refresh limit.

  • Limit: Up to 48 scheduled refreshes per dataset per 24 hours.
  • Minimum Time Interval: With a premium capacity, you can schedule refreshes as frequently as every 5 minutes if needed.

This higher frequency is ideal for more time-sensitive data analysis, like monitoring e-commerce flash sales, tracking critical operational metrics, or managing ad campaign performance throughout the day. The dedicated resources also mean your data refreshes and metric calculations generally run much faster and more reliably.

A Quick Summary of the Limits

  • Power BI Pro (Shared Capacity): 8 refreshes per day
  • Power BI Premium Per User (Premium Capacity): 48 refreshes per day
  • Power BI Premium (Dedicated Capacity): 48 refreshes per day

It's important to remember these limits apply on a per-dataset basis, not per report. If you have ten different reports all built on top of the same dataset, scheduling that single dataset to refresh will update the data for all ten reports simultaneously.

How to Set Up a Scheduled Refresh in Power BI

Configuring a scheduled refresh is a straightforward process, but you need to do it in the Power BI service (the online version), not in Power BI Desktop. The settings are tied to the published dataset.

Step 1: Publish Your Report

Once your report is built in Power BI Desktop, publish it to a workspace in the Power BI service by clicking the "Publish" button on the Home ribbon.

Step 2: Navigate to Your Workspace and Find the Dataset

In the Power BI service, go to the workspace where you published your report. Don't look for the report itself, you need to find the dataset that was published with it. It will have the same name as your report and an orange icon.

Step 3: Open the Dataset Settings

Hover over your dataset, click the ellipsis (...), and select Settings.

GraphedGraphed

Still Building Reports Manually?

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

Watch Graphed demo video

Step 4: Configure Data Source Credentials

This is the most common place people get stuck. Power BI needs to know your login credentials for each data source (like a SQL database, Salesforce account, or SharePoint file) so it can connect automatically without requiring further input. Under "Data source credentials," click "Edit credentials" for any source that has an error. Enter your credentials and sign in. You’ll have a green checkmark when everything is configured correctly.

What About On-Premises Data? The Gateway

If your data is stored on-premises (e.g., in a local SQL Server), you must install and configure an On-premises data gateway. This gateway acts as a secure bridge, allowing the Power BI service to reach into your local network and pull the data it needs for a refresh.

Step 5: Schedule Your Refresh

Scroll down to the Scheduled refresh section and toggle it on. From here, the options are simple:

  1. Refresh frequency: Choose Daily or Weekly.
  2. Time zone: Select the correct time zone for your business hours.
  3. Add another time: Click this to add specific times you want the refresh to run. You can add up to 8 slots for a Pro account or up to 48 for Premium.

Finally, you can check the box to receive refresh failure notifications by email. It's a great idea to send these to yourself or a designated IT contact so you can quickly fix any issues. Click Apply, and you're all set!

Tips for Managing Your Refresh Schedule

As you add more datasets, managing your refreshes efficiently becomes important for performance.

  • Stagger Your Refresh Times: If you have 10 datasets, don't schedule them all to refresh at 9:00 AM. This can overload your capacity (especially shared capacity) or the source systems. Space them out - run larger ones overnight and smaller, critical ones just before key meetings.
  • Monitor Refresh History: In the dataset settings, you can find the "Refresh history" tab. Check this periodically to spot any failed refreshes. Failures are often caused by expired passwords, changes in the source data schema, or gateway issues.
  • Use Incremental Refresh: For very large datasets, consider setting up an incremental refresh. This advanced technique partitions your data (usually by date) and only refreshes the most recent period, instead of re-importing the entire dataset every time. This makes refreshes massively faster and more reliable.

What If 8 (or 48) Refreshes Aren't Enough?

Sometimes you need data that's closer to real-time. If the scheduled refresh limits aren't sufficient, you have several powerful alternatives for getting more up-to-date information.

Option 1: Switch to DirectQuery or Live Connection

Instead of importing data into Power BI, you can use these connection modes. DirectQuery keeps data in the source system. Every time you interact with a Power BI visual (like clicking a filter), Power BI sends a query directly to the data source and fetches live results. This provides real-time data but can be slower than using a pre-loaded imported dataset.

Live Connection is similar but used for specific datasets like SQL Server Analysis Services (SSAS), Azure Analysis Services, or another Power BI dataset.

  • Pros: Always showing the latest data, no scheduled refreshes to manage.
  • Cons: Report performance depends entirely on the speed of the underlying data source, more limited DAX and data transformation capabilities.
GraphedGraphed

Still Building Reports Manually?

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

Watch Graphed demo video

Option 2: Use Microsoft Power Automate

For those between the 30-minute and 5-minute intervals, you can use this excellent workaround. You can build a simple flow in Microsoft Power Automate that triggers a dataset refresh. You can easily set the recurrence trigger to run, for instance, every 15 minutes. However, it’s not an unlimited hack - this method only triggers an on-demand refresh, and you must still adhere to your daily limit of refreshes, so don't be tempted to try it every minute!

Option 3: Use the Push Datasets API

For a highly customized, developer-driven approach, you can use the Power BI REST API to programmatically "push data" into a dataset in real time. This is common for real-time reporting scenarios like IoT sensor data and can support streaming rates of millions of rows every hour. Although incredibly powerful, it does take a significant amount of expertise and development operations to set up. If you need more instant analysis of your data, then this is the route to take.

Final Thoughts

Knowing your Power BI refresh limits - 8 for Shared Capacity (Pro) and 48 for Premium - is the first step to ensuring your data is timely. For most situations, setting a smart schedule and monitoring failures is enough. When you need more, transitioning to DirectQuery or leveraging tools like Power Automate can deliver the near real-time data you need.

Of course, managing data pipelines, worrying about refresh schedulers, and dealing with gateway failures across different platforms like Google Analytics, Shopify, and Salesforce is often the most time-consuming part of analysis. We built Graphed to solve this by ditching the complexity. In place of configuring datasets and refresh times, we connect directly to your data sources and create live dashboards that are automatically kept up-to-date. You're always looking at real-time data without having to think about it - just connect, ask questions in plain English, and get your insights instantly.

Related Articles