Microsoft has released the October 2026 on-premises data gateway, version 3000.338, for Microsoft Fabric and Power BI workloads. The update focuses on accessibility, configuration reliability, diagnostics and compatibility with the October 2026 release of Power BI Desktop.
The release includes Power Query Engine 2.159.229. Microsoft says reports published to the Power BI Service and refreshed through the gateway now use the same query execution logic and runtime as the October 2026 version of Power BI Desktop.
Accessibility and configuration fixes
The installer and configurator have received further accessibility work after changes in the September release. Keyboard navigation is intended to be more predictable, screen readers give clearer announcements for controls and status changes, and Windows high-contrast themes have better readability and visual consistency.
The update also changes how connection tests interact with Power Query configuration. Running a connection test no longer changes those settings, so administrators do not need to reapply them after validating connectivity.
Service-start failures should also be easier to diagnose. When the gateway service fails to start, the gateway now provides more detailed diagnostics so administrators can identify the cause and restore connectivity.
Preview APIs for tenant-wide connection administration
Version 3000.338 introduces preview Admin Connections REST APIs for connections and gateways. These APIs give Fabric administrators visibility and control across connections in the tenant, including on-premises data gateway, virtual network gateway and cloud connections.
Before this preview, administrators could only see connections for which they had been given permission. The new APIs can be called by Fabric administrators or service principals, which makes them suitable for governance and audit automation. Admin actions such as viewing or deleting a connection and changing role assignments are recorded in audit logs.
Upgrade planning
Microsoft recommends validating version 3000.338 in a lower environment before upgrading production gateways. The test gateway should match production as closely as possible, including data sources, connectors, authentication methods and network configuration.
Administrators should test scheduled and on-demand refreshes for critical semantic models and dataflows, DirectQuery and live connection reports, connection tests for each data source type, any custom connectors, gateway service start-up and sign-in. Microsoft also recommends monitoring the test gateway for a representative period, such as a few refresh cycles, before promotion.
For production upgrades, administrators should store the gateway recovery key securely and keep a record of the gateway configuration. In gateway clusters, Microsoft recommends upgrading one member at a time while other members continue serving requests, then confirming that each upgraded member is healthy before moving to the next. All members should end on the same version, because mixed versions can lead to inconsistent behaviour.
Production upgrades should be scheduled during periods of low refresh activity. Microsoft supports only the last six releases of the on-premises data gateway, so regular upgrades remain part of keeping gateway deployments supported.
Gateway upgrades that preserve Power Query settings, expose tenant-wide connection governance and keep Desktop and service refresh behaviour aligned are the operational issues ECS's Data topic handles, alongside Microsoft Fabric, Power BI, SQL Server and Dataverse. Sessions give attendees practitioner experience on Fabric and Power BI administration, including the controls and upgrade choices behind production data platforms. Bring the gateway scenarios that are difficult to settle from release notes alone.
Photo: Coolcaesar, CC BY-SA 4.0, via Wikimedia Commons, cropped
This article was written by the ECS editorial team with the assistance of Amal Agent, run.events' AI assistant, which supported the research, drafting and proofreading.