Launch Deal · 50% off 1st month ·

4.4 — Identify When a Gateway Is Required and Configure Scheduled Refresh

PL-300 Domain 4 · Skill 4.4

What You Need to Know

When you need a gateway

The Power BI service runs in the cloud. An on-premises data gateway is the bridge it uses to reach data it can't reach directly.

Source Gateway needed?
SQL Server, Oracle, file shares, Excel or CSV files on a local or network drive Yes (on-premises)
A source in an Azure virtual network or behind a private endpoint Yes, or a virtual network data gateway (managed by Microsoft, needs a capacity)
Azure SQL Database, Synapse, Fabric, Dataverse, Salesforce, SharePoint Online, OneDrive for work or school No (cloud sources reachable from the service)
Web sources open to the internet Usually no

The gateway is needed for Import refresh and for DirectQuery queries to on-premises sources. A single semantic model that mixes cloud and on-premises sources uses the gateway for the on-premises ones.

Standard vs personal mode

Standard mode Personal mode
Users Many users and semantic models One user
DirectQuery / live connection Yes No, Import refresh only
Runs as A Windows service An app tied to the user
Managed Centrally, with connections and admins By that user only
Use Teams and production Quick personal projects

After installing a standard gateway, an admin creates connections in Settings > Manage connections and gateways, with credentials, and grants users permission to use them. The semantic model's Settings > Gateway and cloud connections then maps each source to a connection. Server and database names must match exactly.

Scheduled refresh

In the service, open the semantic model > Settings > Refresh:

Setting Detail
Configure a refresh schedule On/off, time zone, daily or weekly, specific times
Refreshes per day Up to 8 on shared capacity (Pro); up to 48 on Premium, PPU or Fabric capacity
Failure notifications Email the owner and other contacts
Data source credentials Must be valid; expired OAuth tokens are a common cause of failures

Also know:

  • Refresh now runs an on-demand refresh.
  • A refresh times out after 2 hours on shared capacity (longer on Premium/Fabric).
  • Power BI pauses scheduled refresh after the model hasn't been used for two months, and after repeated failures. The owner is notified.
  • DirectQuery and Direct Lake models don't need data refresh for freshness (only for schema or framing), but can refresh visual caches.
  • Incremental refresh (with RangeStart and RangeEnd, lesson 1.3) refreshes only recent partitions, which makes large refreshes faster and more reliable.
  • Dataflows and the semantic models that use them each have their own schedule. Schedule the dataflow first.

Key Concept: On-premises (or private network) sources need a gateway, in standard mode for anything shared or DirectQuery. Scheduled refresh is configured per semantic model, up to 8 times a day on Pro and 48 on capacity, with valid credentials.

Exam Traps

  • Installing a gateway for Azure SQL Database or SharePoint Online data
  • Using a personal-mode gateway for DirectQuery or for a team's semantic models
  • Scheduling 24 refreshes a day for a model in a Pro workspace
  • Forgetting to map the data source to a gateway connection after publishing
  • Expecting scheduled refresh to keep running on a model nobody has opened for months

Check your understanding

Practice Scenario

🔒 This practice scenario is part of Skillmarked Pro

The lessons stay free. Pro unlocks the other 22 PL-300 practice scenarios and the 50-question timed mock exam, plus everything for every other exam.

See plans

Launch Deal: first month €9.95, then €19.90/month. Enter code LAUNCH50 at checkout. Ends 1 December.

Cancel anytime. Or €199 a year, which saves 17%.

Not sure yet? Try 10 free mock exam questions.

Already Pro? Log in.

Sources