MetricSign
Start free
Critical severitygateway

Power BI Refresh Error:
ServiceBusCommunicationException

What does this error mean?

The on-premises data gateway cannot connect to Azure Service Bus, which is the communication channel between Power BI Service and the gateway. Without this connection, the gateway is effectively offline.

Common causes

  • 1Outbound HTTPS (port 443) or AMQP (port 5671/5672) traffic from the gateway machine is blocked by a firewall
  • 2A proxy server is intercepting and terminating the gateway's outbound TLS connections
  • 3The gateway machine has no internet access or DNS resolution is failing for Azure endpoints
  • 4Antivirus or endpoint security software is blocking the gateway process's network calls
  • 5The gateway Windows service account was modified and lost necessary network permissions

How to fix it

  1. 1On the gateway machine, open the On-premises data gateway app and check the connection status — it should show 'The gateway is online'.
  2. 2Verify outbound access to *.servicebus.windows.net on port 443 and 5671/5672.
  3. 3If behind a proxy, configure proxy settings in the gateway configuration file (Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config).
  4. 4Temporarily disable antivirus/firewall on the gateway machine to test if it is causing the block.
  5. 5Run the gateway connectivity test tool from the gateway app's diagnostics section.
  6. 6Check the Windows Event Log on the gateway machine for specific Service Bus error codes.

Frequently asked questions

Does this error affect all datasets using the same gateway?

Yes — all datasets routed through the affected gateway will fail simultaneously. Resolving the gateway configuration or credential issue restores all of them at once.

Does this error appear in Power BI Desktop?

No — Power BI Desktop connects directly to data sources. Gateway errors only occur when Power BI Service initiates a scheduled or manual refresh.

Can this error resolve itself without intervention?

No — gateway errors require manual action: re-entering credentials, restarting the gateway service, or correcting the network path between the gateway and the data source.

How long does it typically take to fix?

A simple credential refresh takes 5–10 minutes. Network or firewall issues can take 30–120 minutes depending on your infrastructure access.

Source · learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-tshoot

Other gateway errors