Gateway troubleshooting

Power Automate gateway readiness checklist

Use this checklist before troubleshooting a specific connector. It confirms the gateway host, region, service status, network path, and account context that Power Automate will use.

On-premises data gatewayFast

Use this guide when

Gateway not visible in Power Automate
Connection test failed with no connector-specific error
Unclear whether the data source should use localhost, machine name, or IP address
Preparing a customer environment before importing generated flows

Prerequisites

Install the standard on-premises data gateway, not personal mode, for Power Automate team or production use.
Sign in to the gateway with the same tenant/environment family used by the Power Automate flow.
Use an account that can create connections and that has permission to use the selected gateway.

Fast checks before you debug

Power Automate evaluates localhost from the gateway machine, not from the cloud service.
A gateway installed in the wrong region may not appear in the Power Automate environment.
Database drivers and client libraries must be installed on the gateway machine, not just on your laptop.
Mapped drives are unreliable for cloud-triggered runs; use UNC paths for file shares.

Step-by-step diagnostics

Confirm the gateway is online and in the right environment

Open Power Automate, select the same environment where you are creating the connection, then go to Data > Gateways. If the gateway is missing, verify the gateway region and the environment region before changing connector settings.

Run the network ports test from the gateway app

On the gateway machine, open the On-premises data gateway app and run the built-in network/ports test. If the test fails, fix firewall, proxy, or outbound connectivity before testing SQL, MySQL, SharePoint, or file system connections.

Test from the gateway machine, not your workstation

Power Automate reaches the data source through the selected gateway. Every host name, port, file path, driver, and credential test should be repeated from the gateway machine.

Test-NetConnection <server-name-or-ip> -Port <port>

Resolve-DnsName <server-name>

Get-Service PBIEgwService

Restart the gateway after driver or credential changes

After installing database drivers, changing Oracle/PostgreSQL/MySQL client software, or changing the gateway service account, restart the gateway service so the runtime loads the new configuration.

Restart-Service PBIEgwService

Common errors and fixes

The gateway does not appear in Power Automate.

Likely cause: Gateway region, tenant, environment, or permissions do not match the current Power Automate environment.
Fix: Verify the selected environment, gateway region, and gateway admins. Reinstall only if the region is wrong.

The connection works locally but fails in Power Automate.

Likely cause: The local test was run from a different computer or under a different account than the gateway runtime.
Fix: Repeat the same connection test from the gateway machine and verify the data source is reachable there.

A driver-dependent connector fails after installing a driver.

Likely cause: The gateway service has not restarted, or the driver architecture/provider is wrong for the gateway runtime.
Fix: Install the required 64-bit provider on the gateway host and restart PBIEgwService.

Power Automate connection fields

Field	Use this value
Gateway	Select the online gateway installed closest to the data source.
Server / path	Use a value resolvable from the gateway host; localhost means the gateway machine.
Authentication	Use the same credential type that succeeds from the gateway machine.

Validation checklist

Gateway appears under Data > Gateways in the intended Power Automate environment.
Gateway network test succeeds or known firewall/proxy exceptions are documented.
The data source host resolves from the gateway machine.
The data source port is reachable from the gateway machine.
Any required connector driver is installed on the gateway machine.

Related gateway guides

File SystemTroubleshoot local and network file paths, gateway service account access, UNC paths, mapped drives, permissions, and file-system connector connection tests.SQL ServerDiagnose SQL Server connection failures, invalid credentials, gateway reachability, table metadata issues, and V2 trigger requirements for Flow Migrator SQL actions.MySQLTroubleshoot MySQL connection tests, server name resolution, Connector/NET driver issues, user host grants, SSL/encryption errors, and primary key behavior.