Course: Microsoft Power BI Training
Topic: Configuring Scheduled Data Refresh
Course Link: Microsoft Power BI Training at JustAcademy
Demo Link: Register for a Free Course Demo
JustAcademy Website: Visit JustAcademy
Scheduled data refresh is an important feature in Microsoft Power BI that automatically updates the data stored in a semantic model at predefined times. It helps ensure that reports and dashboards display recent information without requiring users to open Power BI Desktop and refresh the data manually every day.
Organizations frequently receive updated data from sales systems, databases, Excel files, customer relationship management systems, inventory platforms, and cloud applications. If a Power BI report continues using old data, its insights may no longer represent the current business situation. Scheduled refresh helps automate the process of retrieving updated source data and processing it into a semantic model.
For example, a retail company may receive new sales transactions throughout the day. A Power BI sales report can be configured to refresh every morning before employees begin their workday. When users open the report after a successful refresh, they can analyze the latest data included in that refresh.
Scheduled refresh is primarily relevant to semantic models using Import storage mode. DirectQuery and live connection models generally access data differently and do not use the same scheduled import-data refresh process.
Scheduled data refresh is a configuration that tells the Power BI service when to refresh a semantic model using data from its connected sources.
A refresh operation typically involves connecting to the source, executing queries, retrieving updated records, applying the necessary transformations, and updating the imported data in the semantic model.
After completing this topic, learners should be able to:
When a refresh runs for an Import-mode semantic model, Power BI connects to the configured data sources and retrieves the data required by the model. Power Query transformations may be executed as part of the refresh process, and the semantic model is updated with the refreshed results.
For example, suppose a company stores its sales transactions in a SQL Server database. The database receives 500 new transactions during the day. When the scheduled refresh runs, Power BI queries the source, processes the required records, and updates the semantic model so reports can use the newly imported data.
A semantic model contains the data and analytical structures used by Power BI reports. These may include tables, relationships, measures, calculated columns, hierarchies, and security definitions.
A report contains pages, charts, tables, filters, slicers, and other visual elements that display information from a semantic model.
Scheduled data refresh is generally configured for the semantic model, not for an individual report. Multiple reports may depend on the same semantic model, so refreshing that model can update the data available to all connected reports.
| Component | Purpose | Refresh Relevance |
|---|---|---|
| Data source | Stores original business data. | Provides the latest available records. |
| Power Query | Connects to sources and transforms data. | Queries and transformations are executed as required during refresh. |
| Semantic model | Stores and organizes analytical data and calculations. | Usually the primary object refreshed in Import mode. |
| Report | Displays data through visuals and filters. | Uses the data available from its semantic model. |
| Dashboard | Displays pinned tiles and summaries. | Tile and cache behavior depends on the underlying connection and model configuration. |
Understanding refresh types helps determine which process is suitable for a particular reporting requirement.
A manual refresh is initiated by a user rather than waiting for a predefined schedule.
In Power BI Desktop, users can select the refresh option on the Home ribbon to retrieve updated source data into the local model. In the Power BI service, authorized users can select Refresh now for a semantic model to initiate an on-demand refresh.
Example: An analyst updates an Excel sales file and wants to verify the updated results immediately instead of waiting until the next morning.
Scheduled refresh automatically starts a refresh at configured times. It is useful when reports need regular updates, such as every morning, several times per day, or at other supported intervals.
Example: An operations dashboard is refreshed at 6:00 AM and 12:00 PM each business day.
Power BI can synchronize certain connected files stored in OneDrive or SharePoint Online so that changes to the underlying file can be reflected in the service. This synchronization is distinct from a scheduled data refresh that queries and processes source data.
If a report uses a file stored in OneDrive or SharePoint Online, understand both the file synchronization process and the semantic model refresh schedule. Allow enough time for the source file changes to become available before the data refresh begins.
Automatic page refresh is a report-page feature mainly associated with DirectQuery scenarios and supported configurations. It periodically updates report visuals rather than performing the same type of full Import-mode semantic model refresh.
| Refresh Type | Initiation | Common Use |
|---|---|---|
| Manual refresh | User action | Testing and immediate updates. |
| Scheduled refresh | Configured schedule | Daily or periodic reporting. |
| OneDrive/SharePoint synchronization | Service-managed synchronization | Updating connected files. |
| Automatic page refresh | Configured page interval | Frequently updating supported DirectQuery reports. |
| API-triggered refresh | External application or automation | Custom workflows and orchestrated refresh operations. |
Before configuring a schedule, confirm that the semantic model and its data sources are suitable for refresh in the Power BI service.
Create and validate the report in Power BI Desktop. Save the PBIX file and publish it to the appropriate Power BI workspace. Publishing makes the report and its associated semantic model available in the service, subject to the user's permissions and licensing.
Power BI must be able to connect to each required source. Cloud sources may support direct connections from the service, while sources on a private network or local computer may require an on-premises data gateway.
Refresh requires valid authentication for the source. Depending on the connector, this may involve an organizational account, database credentials, OAuth authentication, Windows authentication, or another supported method.
The semantic model owner needs appropriate access to configure the model and its refresh settings. Enterprise gateway usage may also require the administrator to grant the user permission to use the relevant gateway data source.
Import-mode models are the primary use case for scheduled data refresh. DirectQuery, live connection, Direct Lake, composite models, and certain connectors have different refresh behavior or configuration requirements. Always verify the supported behavior for the chosen source and storage mode.
The Power BI service provides settings for refresh frequency, refresh times, gateway connections, source credentials, and notifications. The exact controls visible to a user depend on the model type, data sources, capacity, and permissions.
The user interface can change over time, so menu labels and placement may vary slightly.
Review the connection settings and confirm that every required source can be reached.
Open the data source credentials section. Sign in using the supported authentication method for each source and save the settings.
Credentials can become invalid when a password expires, a user account is disabled, access permissions change, or an authentication token expires. If credentials change, update the saved configuration in Power BI as well.
After saving the schedule, use Refresh now to test the configuration if an immediate refresh is appropriate. This helps verify connectivity, credentials, and query execution before the scheduled run.
After the refresh completes, inspect the refresh history. Confirm the status and verify that the resulting report contains the expected data.
Suppose a company prepares its sales report before the daily team meeting. It wants the report refreshed before 8:00 AM and updated again at lunchtime.
| Setting | Example Configuration |
|---|---|
| Semantic model | Sales Analytics Model |
| Refresh frequency | Daily |
| First refresh | 6:00 AM |
| Second refresh | 12:00 PM |
| Time zone | Business reporting time zone |
| Failure notifications | Semantic model owner or designated internal recipients |
| Validation | Review refresh history and confirm key sales totals. |
Important: This is an example schedule, not a guarantee that refresh will finish at those times. Power BI aims to initiate a refresh near its scheduled time, but resource availability and source performance can cause delays. Plan sufficient time for refresh completion.
Refresh frequency determines how often a scheduled refresh can be initiated. The maximum number of daily scheduled refresh slots depends on the licensing and capacity configuration.
| Capacity or License | Typical Scheduled Refresh Limit | Planning Consideration |
|---|---|---|
| Power BI Pro shared capacity | Up to 8 scheduled refreshes per day | Choose times that align with business reporting needs. |
| Power BI Premium per user (PPU) | Up to 48 scheduled refreshes per day | Confirm workspace and model eligibility. |
| Eligible Premium or Fabric capacity | Up to 48 scheduled refreshes per day for standard schedule settings | Capacity resources and other operational constraints still apply. |
These are common schedule limits for Import-mode semantic models and should be verified against current Microsoft licensing and capacity documentation. API-triggered operations, XMLA-based processing, Direct Lake, and other advanced scenarios may follow different rules or resource constraints.
A refresh schedule should reflect how frequently source data changes and how quickly users need the changes to appear in reports.
Power BI's standard scheduled refresh settings do not provide a simple monthly frequency option in the same way as daily scheduling. For monthly business workflows, an external orchestration mechanism may be needed. For example, an automation can trigger a refresh at the appropriate monthly date, subject to the API, licensing, permissions, and capacity constraints.
The time at which a refresh is initiated is not the same as the time at which it finishes. A refresh can take longer when the source database is busy, queries are complex, the model is large, or the gateway is under heavy load.
When planning schedules, allow enough time for the refresh to complete before users need the data. Avoid scheduling many large models to refresh simultaneously when they compete for the same source or capacity resources.
Time-zone configuration is important when users, data sources, and business operations are located in different regions.
A schedule configured for one time zone may run at an unexpected local time if the team assumes a different time zone. This can affect morning reports, daily reconciliations, and business opening dashboards.
A company based in India wants its dashboard refreshed before employees begin work at 9:00 AM Indian Standard Time. The administrator should configure and verify the intended time zone and choose a refresh time early enough to accommodate source processing and possible service delays.
Power BI must authenticate to a data source before it can retrieve protected data. A successful manual refresh in Power BI Desktop does not automatically guarantee that the Power BI service has the credentials and permissions required for scheduled refresh.
| Authentication Method | Description | Example Use |
|---|---|---|
| Organizational account | Uses a work or school account and supported organizational authentication. | Supported Microsoft 365 or organizational services. |
| Database credentials | Uses a database-specific username and password. | Supported SQL database connections. |
| Windows authentication | Uses Windows identity-based authentication where supported. | Some on-premises database environments. |
| OAuth-based authentication | Uses an authorization flow to grant access to a service. | Supported cloud connectors. |
| Anonymous access | Connects without user credentials where the source permits it. | Public data sources that explicitly support anonymous access. |
An on-premises data gateway allows Power BI service to access supported data sources that are not directly reachable from the cloud service. It acts as a secure bridge between Power BI and sources located inside a company network or on a local machine.
A gateway is generally required when the Power BI service cannot connect directly to a source because the source is located on an internal network or is otherwise inaccessible from the service. The exact requirement depends on the source, network setup, connector, and authentication method.
The standard, also called enterprise, gateway mode is intended for shared and managed environments. Administrators can configure data source definitions and control which users or semantic models can use them.
This mode is usually preferable for organizations that need centrally managed connections, multiple users, and governed access to on-premises sources.
Personal mode is designed for individual scenarios in which one user manages the gateway and the relevant semantic models. It has fewer sharing and management capabilities than standard mode.
If the gateway is offline, verify that the host machine is powered on, the gateway service is running, network connectivity is available, and the gateway has not encountered an authentication or configuration error.
If the gateway is online but refresh fails, check the data source mapping, source credentials, network access, and query error details. A gateway being online does not guarantee that every configured data source is accessible.
Refresh failure notifications help the semantic model owner or designated internal recipients respond when a refresh fails. Power BI can send notifications by email, depending on the configuration and recipient eligibility.
Without notifications, a report may continue to display data from an earlier successful refresh while users assume that the data is current. Notifications help teams identify refresh failures before they affect business decisions.
Power BI can disable a scheduled refresh after repeated consecutive failures or when it detects an unrecoverable configuration problem. Invalid credentials, unavailable gateways, and source errors may require corrective action before the schedule can be enabled again.
After fixing the underlying issue, open the semantic model's refresh settings, enable the schedule if it has been disabled, save the configuration, and verify the next refresh.
Refresh history is one of the most useful tools for understanding whether scheduled refresh is working correctly. It provides details about previous refresh attempts and helps identify recurring failures.
| Field | Meaning |
|---|---|
| Status | Indicates whether the refresh succeeded, failed, or completed with warnings where shown. |
| Start time | Shows when the refresh operation began. |
| Duration | Indicates how long the refresh took. |
| Refresh type | Helps identify whether the operation was scheduled or initiated through another supported method. |
| Error details | Provides information that can help diagnose a failed refresh. |
| Execution details | May provide additional metrics and diagnostic information when available. |
| Date | Scheduled Time | Status | Duration | Action |
|---|---|---|---|---|
| Monday | 6:00 AM | Completed | 4 minutes | No action required. |
| Tuesday | 6:00 AM | Failed | 1 minute | Check credentials and source connectivity. |
| Wednesday | 6:00 AM | Completed | 5 minutes | Confirm that expected records are present. |
| Thursday | 6:00 AM | Completed with warnings | 6 minutes | Investigate the reported warning. |
The entries above are illustrative examples, not actual Power BI refresh records.
Problem: Refresh fails because Power BI cannot authenticate to the data source.
Possible causes: An expired password, changed credentials, revoked permissions, or an expired authorization token.
Solution: Update the data source credentials, confirm access to the source, and run a test refresh.
Problem: Power BI cannot reach the on-premises source through the gateway.
Possible causes: The host computer is switched off, the gateway service has stopped, or a network issue prevents the connection.
Solution: Check the gateway host, service status, network connectivity, gateway configuration, and software updates.
Problem: The gateway is online, but the semantic model cannot find a matching data source definition.
Possible causes: The server or database name differs, the source was not configured on the gateway, or the user lacks permission.
Solution: Ask the gateway administrator to configure the correct source definition and grant the required permissions. Verify that the semantic model maps to the correct source.
Problem: A query works in Power BI Desktop but cannot be refreshed in the service.
Possible causes: A dynamically constructed source path or unsupported connector pattern prevents Power BI service from determining the source connection.
Solution: Review the query design and connector documentation. Where possible, use supported static source definitions, parameters, and approved connection patterns.
Problem: A refresh fails after a source table or column is renamed or removed.
Possible causes: Power Query steps, model relationships, measures, or visuals still refer to the previous schema.
Solution: Open the PBIX file in Power BI Desktop, correct the queries and dependent model objects, refresh and validate the model, and republish it to the service.
Problem: The refresh duration has increased or the model does not finish before users need the data.
Possible causes: Large data volumes, complex transformations, slow source queries, source contention, gateway limitations, or capacity pressure.
Solution: Optimize queries, remove unnecessary columns and rows, reduce expensive transformations, use incremental refresh where appropriate, and coordinate refresh times with source administrators.
Problem: The expected schedule no longer runs.
Possible causes: Repeated refresh failures, an unrecoverable configuration issue, or automatic pausing after a period of inactivity.
Solution: Review refresh history, resolve the underlying problem, and re-enable the schedule if required. If the model was paused due to inactivity, visit a report or dashboard using the model and check its schedule settings.
Problem: The refresh history shows success, but the report still displays unexpected or older information.
Possible causes: The source itself has not been updated, query filters exclude new records, a report visual has not refreshed its results, or the report uses a different semantic model.
Solution: Verify source records, query filters, model relationships, the model referenced by the report, and the report's current visual results.
| Issue | First Check | Recommended Next Step |
|---|---|---|
| Authentication failure | Data source credentials | Reauthenticate and test. |
| Gateway unavailable | Gateway status | Restore gateway service and connectivity. |
| Source mapping failure | Gateway connection settings | Verify source definitions and permissions. |
| Schema mismatch | Power Query steps and source schema | Update queries and republish the model. |
| Long refresh duration | Refresh duration and source performance | Optimize queries and scheduling. |
| Old report results | Model identity and source data | Validate filters and report visual updates. |
Schedule refreshes to complete before the reports are needed. For a morning management meeting, a refresh should start early enough to account for processing time and possible delays.
Refreshing a model too frequently can increase source-system load and consume available Power BI capacity. Match the refresh schedule to the actual business requirement rather than choosing the highest possible frequency by default.
Incremental refresh can reduce the amount of historical data that needs to be processed during each refresh for supported models and sources. It is especially useful for large fact tables where new or changed data is concentrated in a recent period.
Incremental refresh requires appropriate configuration, typically including date/time parameters and refresh policies. Confirm the source and model support the intended policy before using it.
Review refresh history on a routine basis. Investigate repeated failures, unexpected duration increases, and warnings. A refresh that succeeds but takes significantly longer than normal may indicate an emerging performance problem.
For enterprise reporting, use a properly managed gateway deployment, keep it updated, and coordinate gateway maintenance with reporting schedules. Avoid relying on a personal computer that may be switched off or disconnected from the network.
Use supported authentication mechanisms and appropriate access controls. Avoid embedding secrets in query text, scripts, or documentation. Keep credentials current and make sure ownership and permissions are maintained.
If the semantic model depends on a file that is updated by another process, schedule the model refresh after the file update has completed. Otherwise, Power BI may refresh successfully while importing the previous version of the file.
Scheduled refresh can be paused after an extended period of inactivity, such as when no one visits a report or dashboard using the semantic model for two months. Monitor the schedule status and follow the service instructions to resume refresh when needed.
Record the semantic model owner, data source details, gateway dependencies, schedule, time zone, expected duration, support contact, and recovery procedure. This documentation helps other team members maintain the solution when ownership changes.
A retail company maintains sales data in a SQL Server database. The management team uses Power BI to review revenue, sales quantity, regional performance, and product profitability. The team needs updated data before the workday begins.
The following DAX measures can be used in the sales model. They are examples and assume that the model contains the indicated columns and relationships.
Total Sales = SUM(Sales[SalesAmount])
Total Quantity = SUM(Sales[Quantity])
Total Orders = DISTINCTCOUNT(Sales[OrderID])
Average Order Value =
DIVIDE([Total Sales], [Total Orders], 0)Scheduled refresh updates the imported data used by these measures. It does not replace the need to validate the DAX logic, source data quality, relationships, or report design.
Objective: Publish a simple sales report and configure its scheduled refresh.
Instructions:
Scenario: A sales report refresh fails after a database password is changed.
Tasks:
Scenario: A business requires refreshed data before its 9:00 AM meeting and again at 1:00 PM.
Tasks:
Answer: Scheduled data refresh automatically initiates a refresh of a supported semantic model at configured times so that imported data can be updated without a user manually starting each refresh.
Answer: In Power BI service, open the relevant workspace, locate the semantic model, and open its settings or refresh options. Configure the schedule, credentials, and gateway connection as required.
Answer: For typical Import-mode scenarios, scheduled data refresh is configured on the semantic model. Reports use the data available from that model.
Answer: Refresh now starts an on-demand refresh, while scheduled refresh initiates refresh operations automatically according to a saved schedule.
Answer: The service may have different network access, credentials, gateway requirements, connector support, or query limitations. These must be checked independently.
Answer: It is software that enables supported Power BI service connections to data sources located within a private network or on a local system.
Answer: A gateway is generally required when the Power BI service cannot directly access a data source, such as a database on an internal network. The requirement depends on the connector and connection configuration.
Answer: Standard mode supports centrally managed connections and shared enterprise use. Personal mode is intended for individual use and offers fewer centralized management capabilities.
Answer: Common limits are up to eight daily scheduled refreshes for Power BI Pro shared capacity and up to 48 for eligible PPU, Premium, and Fabric capacity scenarios. The exact behavior depends on the capacity, model type, and current service rules.
Answer: Review refresh history, examine the error details, verify credentials, check gateway status and source mappings, test source connectivity, and investigate query or schema changes.
Answer: The saved credentials may become invalid. Update the credentials in the relevant semantic model or gateway configuration and test the refresh again.
Answer: Refresh history records previous refresh attempts, including status, start time, duration, and available error details.
Answer: Incremental refresh is a supported model configuration that refreshes selected portions of historical data rather than processing all historical records on every refresh. It is useful for large datasets when configured appropriately.
Answer: The source may not contain new records, query filters may exclude them, the report may use a different semantic model, or report visuals may not yet have retrieved updated results.
Answer: DirectQuery models generally query the source as users interact with reports instead of importing all source data through a scheduled refresh. Some metadata, caches, or other supported components may still have separate update behavior.
Answer: Repeated consecutive failures, unrecoverable configuration errors, or an inactivity-related pause may disable the schedule. Review the service message and refresh history, fix the underlying issue, and re-enable the schedule when appropriate.
Answer: No. Power BI aims to initiate the refresh near the scheduled time, but service load and source performance can delay the start or completion. Allow sufficient processing time.
Answer: Choose business-appropriate times, optimize queries, keep credentials and gateways healthy, monitor refresh history, configure notifications, use incremental refresh where suitable, and document the recovery process.
| Term | Definition |
|---|---|
| Scheduled refresh | An automated refresh initiated at configured times. |
| Semantic model | The analytical model that organizes data, relationships, and calculations for reports. |
| Power BI service | The online service used to publish, share, manage, and refresh Power BI content. |
| Data source credentials | Authentication details used to access a connected data source. |
| On-premises data gateway | A bridge that enables supported cloud-service connections to internal data sources. |
| Refresh history | A record of previous refresh attempts and their available status details. |
| Incremental refresh | A configuration that refreshes selected portions of data rather than reprocessing all historical data each time. |
| Import mode | A storage mode in which data is loaded into the semantic model. |
| DirectQuery | A storage mode in which queries generally retrieve data from the source rather than importing all source data into the model. |
| Query folding | The process of translating supported Power Query transformations into operations executed by the source system. |
| Refresh failure notification | An alert that informs the model owner or supported internal recipients about a failed refresh. |
| Time zone | The regional time setting used to interpret the configured refresh schedule. |
Configuring scheduled data refresh is an essential Power BI administration and reporting skill. It allows supported semantic models to update automatically, helping business users access recently refreshed data without depending on repeated manual operations.
A reliable refresh solution requires more than selecting a time. Analysts and administrators must verify source connectivity, authentication, gateway configuration, refresh frequency, time zones, capacity limits, and failure notifications. They should also monitor refresh history and investigate performance problems before those problems affect reporting.
By combining a suitable refresh schedule with efficient Power Query transformations, reliable connectivity, appropriate security, and regular monitoring, organizations can maintain dependable Power BI reports and dashboards.
