How should the Power BI on-premises data gateway be architected, sized and made highly available?

The architecture in one paragraph

Microsoft describes the on-premises data gateway as locally installed Windows software that connects the Power BI service to data sources in an on-premises network, using outbound connections so that no inbound ports are opened, and it lists three options: standard mode for centrally managed shared connections, DirectQuery, live connections and clusters; personal mode for one user's Import refreshes; and the Microsoft-managed virtual network data gateway for sources inside an Azure virtual network (Microsoft Learn, On-premises data gateways in Power BI, accessed 2026-10-20). The enterprise pattern EPC Group's Power BI consulting practice builds follows from that: standard-mode gateways only, on dedicated always-on servers close to the data, grouped into clusters of two or more members per workload and per environment, with connections owned by named stewards, access granted to security groups, and the gateway's own logs feeding a monitoring report. Most refresh failures EPC Group investigates trace back to one of those decisions being skipped.

Standard versus personal mode

Microsoft's comparison is unambiguous. The standard gateway serves Power BI, Power Apps, Power Automate, Azure Logic Apps, Azure Analysis Services and Power BI dataflows (legacy); runs under credentials configured by authorized gateway users; installs only as a local administrator; and supports centralized gateway and data source management, Import and scheduled refresh, DirectQuery and live connection to Analysis Services. Personal mode serves Power BI only, runs under the installing user's Windows credentials or per-source credentials, and supports only Import semantic models with scheduled or on-demand refresh. It does not support DirectQuery, live connections, composite models, virtual network data gateways, clustering or high availability (Microsoft Learn, Use a personal gateway in Power BI, accessed 2026-10-20). A machine can host one gateway of each mode, never two of the same mode (Microsoft Learn, Install an on-premises data gateway, accessed 2026-10-20). EPC Group inventories personal gateways during governance reviews, because a certified semantic model refreshing through an analyst's laptop is an availability risk the tenant cannot see until it fails.

Sizing the gateway machine

Microsoft's installation requirements set the baseline: .NET Framework 4.8 and a supported Windows or Windows Server version at minimum, with an 8-core CPU, 8 GB of memory, a 64-bit edition of Windows Server 2019, 2022 or 2025, and solid-state storage for spooling recommended. Gateways are not supported on Server Core or Windows containers, cannot be installed on a domain controller, and should not run on a machine that sleeps, uses wireless networking or shares resources with other applications; Windows authentication to sources requires the gateway machine to be in the same directory environment as the sources (Microsoft Learn, Install an on-premises data gateway, accessed 2026-10-20).

Microsoft's sizing guidance adds the method. Start with at least 8 CPU cores, 8 GB of RAM and multiple Gigabit network adapters, measure a typical workload with CPU and memory counters, and plan for reliable, low-latency connectivity in both directions: fewer hops between gateway and source, no proxy throttling, Azure ExpressRoute where appropriate, and good connectivity to Active Directory for live connections that use dynamic row-level security (Microsoft Learn, On-premises data gateway sizing, accessed 2026-10-20). Microsoft's implementation planning guidance explains why the workload type matters: for Import models, the number of refreshes drives resource needs such as RAM, while for DirectQuery and live connections the number of report consumers drives needs such as CPU (Microsoft Learn, Power BI implementation planning: Data gateways, accessed 2026-10-20). EPC Group therefore separates Import refresh and DirectQuery traffic onto different clusters once either grows, rather than adding cores to a shared one.

Clustering and load balancing for high availability

A cluster is a set of gateways on different machines registered as one logical gateway. Each cluster supports up to 10 members; the gateway cloud service always uses the primary member unless it is unavailable, then moves to the next; management operations such as granting admin permissions or adding connections apply to every member; and members should run the same gateway version. With Distribute requests across all active gateways in this cluster enabled, members are selected at random, and administrators can add throttling in the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file with CPUUtilizationPercentageThreshold, MemoryUtilizationPercentageThreshold and ResourceUtilizationAggregationTimeInMinutes, which defaults to 5 minutes; a request fails only if every member is over its limit. Microsoft also recommends disabling or removing offline members rather than leaving them registered (Microsoft Learn, Manage on-premises data gateway high-availability clusters and load balancing, accessed 2026-10-20).

For business-critical use, Microsoft advises against a single cluster for an entire company, recommends a minimum of two gateways per cluster, and illustrates separate clusters for enterprise BI, individual departments and personal workloads (Microsoft Learn, Plan, scale, and maintain a business-critical gateway solution, accessed 2026-10-20). It also recommends separate clusters per development, test and production environment and updating one cluster member at a time, at least quarterly, to avoid downtime (Microsoft Learn, Power BI implementation planning: Data gateways, accessed 2026-10-20). The recovery key entered at installation is what lets a new machine join or replace a member, and Microsoft cannot retrieve it (Microsoft Learn, Install an on-premises data gateway, accessed 2026-10-20), so EPC Group stores it in the client's credential vault on day one.

Connections, roles and monitoring

Access is two-layered. Gateway roles are Admin, Connection creator and Connection creator with sharing; connection roles are Owner, User and User with sharing, and only an Owner can see or update stored credentials (Microsoft Learn, Manage security roles of an on-premises data gateway, accessed 2026-10-20). Credentials are encrypted so they cannot be decrypted in the cloud and are decrypted only on the gateway machine (Microsoft Learn, Add or remove a gateway data source, accessed 2026-10-20). For monitoring, standard gateways log by default to four reports, with query durations, spooling times and the SystemCPUPercent, SystemMEMUsedPercent, GatewayCPUPercent and GatewayMEMKb counters; Microsoft supplies a Power BI template for them, notes that the StreamBeforeRequestCompletes setting can speed loads at some reliability cost, and advises watching spooler disk space (Microsoft Learn, Monitor and optimize on-premises data gateway performance, accessed 2026-10-20). EPC Group's Power BI admin and governance support team consolidates those files across members and reviews them with the refresh history each week.

Documented work

ANON-CASES: EPC Group engagement data for gateway architecture covers mid-size and large manufacturing and energy organizations moving refreshes off single gateway servers and personal-mode gateways onto clustered standard-mode gateways separated by workload and environment, delivered by the firm's Power BI consulting practice. Client names are not published here. Engagements are described by industry and organization size only, and no outcome figures are quoted that cannot be traced to a signed deliverable. EPC Group is a Microsoft Solutions Partner with all six Solutions Partner Designations as of October 2026.

Frequently Asked Questions

Talk to a senior architect

If refreshes depend on a single gateway server, or certified models run through personal gateways, a 30-minute discovery call with a senior EPC Group architect will map your gateway estate and set out the cluster, role and monitoring changes. See the Power BI consulting service hub for engagement structures.

Email contact@epcgroup.net or call 888-381-9725.

a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.