(+351) 21 24 10006  ·  info@bconcepts.pt
Carnaxide, Lisbon
Certificação PL-300 (Power BI)

PL-300: how to manage refresh schedules and gateways

João Barros 05 de November de 2026 6 min read

This practice teaches the skill of managing and configuring refresh schedules and gateways in Power BI — an essential capability for the PL-300 exam and real life to ensure reports show current, secure and efficient data. Mastering these concepts prevents stale reports, reduces production failures and ensures the team trusts decisions based on Power BI.

What you need to know

Data refresh in Power BI updates datasets based on their sources. There are two main scenarios: cloud data and on-premises data. In cloud scenarios you can use Import, DirectQuery or Live Connection, and even hybrid modes such as Composite. In Import mode the data are copied to the Power BI service and require schedules to stay current; DirectQuery and Live Connection query the source in real time, which eliminates the need for full refresh, but can introduce query latency and restrictions on features such as some types of modeling.

For on-premises sources the On-premises data gateway (gateway) is required. This component acts as a secure "tunnel" between the Power BI service and your local databases. The gateway can be installed on a single server or configured in cluster mode for high availability — at least two instances are recommended in critical production environments. In practical limits, users with Power BI Pro can typically schedule up to 8 refreshes per day per dataset, while Power BI Premium raises that limit to 48 refreshes per day (always check current quotas in the Microsoft documentation, as they may vary).

Concrete example: you have a report that imports daily sales from an on‑premises SQL Server database with about 10 million historical rows. Instead of refreshing all 10 million rows every night, you implement incremental refresh to keep only the last 90 days updated and reduce the processed volume by more than 90% during each run. By installing a gateway on a VM in the same network as the SQL Server, registering it with the service and scheduling a refresh at 02:00, we ensure reports are ready when managers arrive at work.

How it works in practice

Essential steps to implement scheduled refresh and gateways:

  1. Install and register the On‑premises data gateway (preferably on a server with good connectivity to the source).
  2. Configure data sources in the gateway with correct credentials and appropriate authentication policies (Windows, SQL authentication, OAuth2).
  3. Publish the report/dataset to a workspace in the Power BI Service.
  4. Assign the gateway to the dataset in the service and validate the connection credentials.
  5. Configure the refresh schedule (frequency, time windows and number of retries in case of error).
  6. Monitor the refresh history, performance metrics and configure alerts for failures.

Practical details and common parameters:

1) Gateway installation:
   - Run the On‑premises data gateway installer on a VM/server with access to the source.
   - Select the 'Standard' mode for sharing among users.
   - Associate with an organizational account (Azure AD) with appropriate permissions.
   - Sizing recommendations: minimum 4 vCPU and 8 GB RAM for small loads; 8+ vCPU and 16+ GB RAM for medium/large loads.

2) Configuration in the Power BI portal:
   - Workspace > Settings > Datasets > Gateway connection
   - Select registered gateway or cluster.
   - In "Data source credentials" enter credentials (Windows/Database/Basic/OAuth2 depending on the source).

3) Scheduled refresh:
   - Settings > Datasets > Scheduled refresh
   - Refresh frequency: Daily / Weekly (Pro: up to 8/day; Premium: up to 48/day per dataset)
   - Time slots: choose windows (e.g.: 02:00, 06:00, 10:00) and coordinate time zones.
   - Failure notifications: enable for administrators and for an operations group.

Common errors

  • Invalid credentials on the gateway: the gateway is installed, but the data source credentials are incorrect or expired (e.g.: OAuth tokens with a 1-hour validity). Result: repeated refresh failures. Solution: periodic validation and use managed service accounts whenever possible.
  • Undersized gateway: installing the gateway on a machine with insufficient resources (CPU/RAM/network latency) causes timeouts on refreshes that process millions of rows. Typical scenario: a 50M-row dataset that times out after 1 h. Solution: increase resources, place the gateway close to the source (same VNet/AZ) and optimize queries.
  • Too many schedules in a shared workspace: many datasets with simultaneous schedules can overload a gateway or hit connection limits. Best practice: stagger windows (e.g., between 01:00 and 05:00) and use incremental refresh to reduce load.
  • Blocked ports and firewall: although the gateway uses outbound HTTPS (port 443), firewall rules or proxies can disrupt communication. Test the connection with the gateway diagnostic tools.

How to practice

To practice in a controlled environment, create a small scenario that reproduces the real steps:

  1. Install the On‑premises data gateway on a VM (it can be local or an Azure VM connected to the company network).
  2. Configure a SQL Server Express data source with about 100k–1M records and publish a Power BI report in Import mode that queries that database.
  3. Register the gateway in the Power BI service, add the data source with tested credentials and run a connection test.
  4. Configure a daily refresh schedule at 03:00; implement incremental refresh for 30 days and run a manual refresh to validate times (goal: < 30 min for a small dataset).
  5. Check the refresh history for 7 days, interpret error messages (timeouts, credentials, out-of-memory) and apply fixes.

Useful official and free Microsoft resources:

  • Official Microsoft Practice Assessment for PL‑300 (free) — use it to evaluate your practical skills.
  • Official PL‑300 study guide from Microsoft (free) — consult the sections on "Manage and deploy Power BI content" and "Data refresh" to cover what is required in the exam.

In summary

  • Refresh and gateways are essential to keep data updated and secure when there are on‑premises sources; without them, reports lose reliability.
  • Install the gateway on a reliable machine, preferably with dedicated resources, and consider a cluster for high availability.
  • Plan schedules carefully: use incremental refresh, off-peak windows and staggers to optimize resources and reduce failures.
  • Act quickly in case of failures: the refresh history and notifications provide crucial clues to resolve issues and restore service availability.
← Back to Certificação PL-300 (Power BI) Book a free consultation →