Power BI How-To / Data Refresh
Power BI On-Premises Gateway Setup, Step by Step
A correct power bi on premises gateway setup is what lets the cloud service refresh data that lives inside your network — local SQL Server, network-share files, an ERP database. This guide walks the standard-mode install end to end: the machine, the install, data sources, scheduled refresh, and the errors everyone hits.
What is the on-premises data gateway and when do you need one?
The on-premises data gateway is free Microsoft software that runs as a Windows service inside your network and brokers secure, outbound-only connections between the Power BI cloud service and local data sources. You need it whenever a semantic model refreshes from anything that is not directly reachable from the cloud.
Two details save hours of confusion later. First, the gateway makes only outbound connections (over port 443 and Azure Service Bus) — you do not open inbound firewall ports to your database, which is what makes it acceptable to most IT teams. Second, install standard mode, not personal mode: standard runs as a service independent of any signed-in user, supports multiple data sources and users, and works with DirectQuery. Personal mode is a single-user convenience that becomes a single point of failure the day its owner changes their password or leaves. If a report is slow rather than failing, that is usually a model problem, not a gateway problem — see our guide to fixing slow Power BI reports. Gateways most often front a database — see SQL Server Power BI dashboard development for the wider build.
How do you install the gateway in standard mode?
Pick an always-on Windows machine with network access to your data sources, download the standard-mode installer from Microsoft, sign in with your organizational account, name the gateway, and set a recovery key. The install itself takes about ten minutes; choosing the right machine is the part people get wrong.
- Choose the machine. Always-on, 64-bit Windows, wired network, with line of sight to the data sources. Not a laptop, and not a domain controller — Microsoft doesn’t support gateway installs on domain controllers.
- Download and run the installer from Microsoft’s gateway installation documentation (opens in new tab), keeping the default “standard mode” choice.
- Sign in with the organizational (work) account that will administer the gateway in the Power BI service.
- Name the gateway and set the recovery key. The key encrypts stored credentials; save it in a shared password manager immediately — you cannot recover or migrate the gateway without it.
- Verify status. The gateway app should report the gateway is online and ready; it should also now appear under Settings → Manage connections and gateways in the Power BI service.
One gateway can serve many models and many sources, so resist installing one per report. For resilience, larger teams add a second gateway to the same cluster later — same name, same recovery key — so refreshes survive one machine being patched.
How do you add data sources and connect your semantic model?
In the Power BI service, open Settings, then Manage connections and gateways, and create a connection on your gateway for each source — server name, database, and credentials. The names must match what the report uses exactly, or Power BI will not offer the gateway at refresh time.
This exact-match rule is the step that trips most first-time setups: if Power BI Desktop connected to SQLSRV01 and the gateway connection says sqlsrv01.internal.local, the service treats them as different sources and reports the gateway as “not configured correctly.” Use one canonical server name everywhere. After the connections exist, open the semantic model’s settings, expand Gateway and cloud connections, and map each source in the model to its gateway connection. The credentials stored on the gateway are what refresh runs under — use a service account with read access rather than a personal login that expires, and prefer a dedicated account your team controls.
How do you schedule refresh through the gateway?
Once the model is mapped to the gateway, open the semantic model’s settings, turn on scheduled refresh, and pick times and a time zone. Microsoft’s documented allowance is up to 8 scheduled refreshes per day on a Pro license and 48 on Premium Per User.
Three habits make schedules boring, in the good sense. Schedule refreshes for when the source is quiet and people aren’t reading the report (early morning beats 9 a.m.). Turn on refresh-failure notifications and send them to a shared mailbox, not one person. And keep the refresh window honest: if the model takes 40 minutes to refresh, hourly scheduling just queues failures. When a previously healthy schedule starts failing, work through our companion piece on diagnosing a failed scheduled refresh — nine times out of ten it is credentials, the gateway machine, or a changed source, in that order.
What are the most common gateway errors and how do you fix them?
Nearly all gateway failures reduce to five causes: the gateway service isn’t running, stored credentials expired, the data-source name doesn’t match the report’s, outbound network access is blocked, or the source itself refused the query. The table below gives the fix for each.
| Symptom / error | Usual cause | Fix |
|---|---|---|
| Gateway shows offline / unreachable | Machine asleep or rebooted; the Windows service stopped | Restart the “On-premises data gateway” service; set the host to never sleep; check after patch nights |
| DM_GWPipeline_Gateway_DataSourceAccessError | Stored credentials expired or lack permission on the source | Re-enter credentials on the gateway connection; move to a non-expiring service account |
| “Data source not configured correctly” / gateway not offered | Server or database name in the model doesn’t exactly match the gateway connection | Make the names identical (including FQDN vs short name), then re-map the model |
| Gateway installs but never comes online | Outbound 443 / Azure Service Bus traffic blocked by firewall or proxy | Allow outbound HTTPS per Microsoft’s documented gateway endpoints; test with the app’s network check |
| Refresh times out or fails intermittently | Source under load, query too heavy, or refresh window too tight | Refresh off-hours, reduce the model’s query load, and space schedules realistically |
If you have worked the table and refresh still fails — or it fails only sometimes, which is worse — the cause is usually one layer down: credentials policy, network appliances, or a model doing too much at refresh time. That is a scoped, senior-level diagnosis, and it is exactly what our Power BI troubleshooting service exists for: we quote the hours first, and most gateway fixes are small.
Gateway fighting you instead of refreshing?
Most gateway and refresh problems are a one-to-two-hour fix for someone who has seen them all. Bring yours to a free demo — we scope it, you approve the hours, and prepaid Flex hours that never expire cover the work.
FAQ
Frequently asked questions
Standard mode runs as a Windows service, supports multiple users and data sources, works with DirectQuery, and survives sign-outs — it is the right choice for anything a team depends on. Personal mode runs under one user’s account for import-only refresh and stops working when that account can’t run it. Install standard mode unless you have a specific reason not to.
No, and usually you shouldn’t. The gateway needs network access to the data source, not co-location: a dedicated always-on Windows machine on the same network is the standard setup. Avoid laptops (refresh dies when the lid closes) and avoid domain controllers, which Microsoft does not support for gateway installs.
The recovery key encrypts the gateway’s stored data-source credentials, and you set it once at installation. Without it you cannot restore, migrate, or add members to that gateway — losing it eventually means reinstalling and re-entering every credential. Store it in a password manager the whole team can reach, not one person’s head.
Usually not. Cloud sources like SharePoint Online, Dataverse, or an Azure SQL Database refresh directly without a gateway. You need one when any source in the semantic model lives on a private network — a local SQL Server, files on a network share, or an ERP database behind your firewall. One on-premises source in the model makes the whole refresh gateway-dependent.
Try us risk-free for 4 hours
If you’re unhappy within the first 4 hours of your block, we’ll refund you in full — no questions asked. Hours are deducted only for work you’ve reviewed and approved, and they never expire.
Book a free demo
Get senior Power BI help, on demand
Tell us the task. We scope it, you approve, and a senior consultant delivers — typically in 3–5 business days. Prepaid hours that never expire.
- Prepaid hours from $100/hour — and they never expire
- Senior-led delivery — 20+ years on the Microsoft platform
- Typical 3–5 business day turnaround
- Full refund if you’re unhappy in your first 4 hours
The fastest way to reach us is the form — tell us the task and we'll reply within one business day.