Blog Post

Fabric Updates Blog
2 MIN READ

On-premises data gateway June 2026 release

goupadhy's avatar
goupadhy
Icon for Microsoft Employee rankMicrosoft Employee
3 months ago

The June 2026 release of the on-premises data gateway is version 3000.322. This new version (3000.322) continues our focus on improving gateway manageability, operational visibility, and enterprise governance while maintaining secure and reliable connectivity between on-premises data sources and Microsoft Fabric services.

Windows broker authentication update

The June 2026 release introduces support for Windows Web Account Manager (WAM) authentication, helping organizations improve token security and align gateway authentication with Microsoft's modern identity platform. This change reduces administrative complexity while providing stronger protection for authentication tokens. Learn more by exploring Acquire a token to call a web API by using Web Account Manager (desktop app).

Apache Log4j update

To further strengthen gateway security, this release updates the bundled Apache Log4j library to version 2.25.4. The update addresses vulnerabilities identified in the previous version and helps organizations maintain a secure gateway environment.

New diagnostics capabilities

Organizations can now enable gateway diagnostic uploads through a consent-driven model that provides greater control over how operational data is shared. Enable the Diagnostics settings, when enabled the diagnostic information can help accelerate troubleshooting and provide richer insights when investigating gateway issues.

Diagnostic information is also integrated directly into the Dataflow Gen2 run experience, allowing administrators and support teams to access relevant insights without switching between multiple tools and diagnostic sources.

Note: Your gateway must be running the latest On-premises Data Gateway version to use these diagnostic capabilities. We strongly recommend keeping the on-premises data gateway updated to the latest version to take advantage of new capabilities, security improvements, and troubleshooting. enhancements. Gateway administrators can initiate gateway updates directly from the Manage connections and gateways experience in Microsoft Fabric.

Power BI Desktop compatibility

This update brings the on-premises data gateway up to date with the June 2026 release of Power BI Desktop.

Download on-premises data gateway (standard mode)

Download on-premises data gateway (personal mode)

This version of the gateway will ensure that the reports that you publish to the Power BI Service and refresh via the gateway will go through the same query execution logic/run-time as in the June version of Power BI Desktop.

Thank you!

Upgrade to version 3000.322 to take advantage of the latest security, authentication, and diagnostics improvements. We encourage you to share feedback and feature requests through the Power BI Ideas forum to help shape future gateway investments.

Updated 3 months ago
Version 1.0
data factory

46 Comments

  • KirstyL's avatar
    KirstyL
    New Member
    3 months ago

    We have just installed the new version of the gateway and this has stopped some of our connections working - particularly those connecting to an on-premise Oracle database. I can't see anything in the release notes that would explain why this would happen. Is anyone able to shed any light? Our current solution is to roll-back to an older version of the gateway

  • AlexisAllerborn's avatar
    AlexisAllerborn
    Icon for Advocate I rankAdvocate I
    2 months ago

    Hi, We've upgraded to the June Release last week, and since then we've started receiving DataSourceAccessError messages randomly in all of our reports going against Synapse SQLs (either dedicated or on-demand).

    This happens either when running scheduled and on-demand refreshes, regardless of the time of the day and semantic model we want to update. When you retry the refresh it works ok.

    Data source error: {"error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_DataSourceAccessError","parameters":{},"details":[],"exceptionCulprit":1}}}
    Cluster URI: WABI-SOUTH-CENTRAL-US-C-PRIMARY-redirect.analysis.windows.net

  • goupadhy's avatar
    goupadhy
    Icon for Microsoft Employee rankMicrosoft Employee
    3 months ago

    Quick update here > A workaround without uninstalling steps:

    1. Go to C:\\Programa Files\\On-premises data gateway
    2. edit the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
    3. update the following:

    <setting name=\"MashupFlight_DisableOracleBundledOdacProviderV2\"
    serializeAs=\"String\">
    <value>False (change to True)</value>
    </setting>

    4. restart the On-premises data gateway service windows service

  • CjApplequist's avatar
    CjApplequist
    Regular Visitor
    3 months ago

    FWIW, we applied 3000.322.5 and reauthenticated connections which seems to have resolved SharePoint list connection issues.

  • kdoherty's avatar
    kdoherty
    Icon for Advocate I rankAdvocate I
    3 months ago

    Microsoft support provided this mitigation, which solved the issue for our Oracle direct query reports.

    Mitigation — DirectQuery (Gateway and Power BI Desktop): Set the TNS_ADMIN environment variable to the directory containing tnsnames.ora, for the account running Power BI Desktop or the On-premises Data Gateway, then restart. For DirectQuery this is currently the only method that resolves a TNS alias. For the gateway, set TNS_ADMIN at system (machine) scope — the gateway service account does not see user-scoped variables — and restart the gateway service. See Use an environment variable.

  • akejoh's avatar
    akejoh
    Icon for Advocate I rankAdvocate I
    2 months ago

    Hi RiaKreulen ,
    As I understand the version 3000.326.11 is the "July" version released August 4.
    I doubt there are an "August" version released.
    The lack of information Currently supported monthly updates to the on-premises data gateways | Microsoft Learn from Microsoft regarding the "July" version released August 4 doesn't give any comfort...
    We're still running May version as we haven't dared to install June version due to all issues mentioned in this post and that was why I asked goupadhy if the (Oracle) issues mentioned in June version has been addressed in July version.

  • goupadhy's avatar
    goupadhy
    Icon for Microsoft Employee rankMicrosoft Employee
    3 months ago

    Thanks, Kirsty, for your feedback and for trying our latest gateway release. We apologize for the disruption you've experienced. We're actively investigating the issue affecting Oracle connections and will share an update as soon as we have more information. In the meantime, thank you for letting us know about your rollback experience.

  • akejoh's avatar
    akejoh
    Icon for Advocate I rankAdvocate I
    3 months ago

    Hi goupadhy ,
    Will there be a update released of the June 2026 / 3000.322-version for the Oracle issue or will the fix be implemented in the July 2026 version ?.

  • eric_stephan-sk's avatar
    eric_stephan-sk
    Regular Visitor
    3 months ago

    @goupadhy We tried to perform the workaround, but after updating the flag from False to True the On-premises data gateway service stays stuck in Starting status. We tried restarting the service, killing the service completely and having it auto restart, as well as restarting the whole server, but the service never restarts. When I put the flag back to False and restart the service, it starts up like normal.