An on-premises data gateway offline status means everything that reads on-premises data through that gateway stops refreshing. The cause is most often on the gateway machine itself, so start there. The gateway carries requests for Azure Analysis Services, Azure Data Factory, Azure Logic Apps, Microsoft Fabric, Power Apps, Power Automate, and Power BI.
How to tell it is the gateway
In the Power BI service, select Settings, then Manage connections and gateways. Find the gateway and read its Status column. “Offline” means the cloud service cannot currently reach it.
A failed refresh can show Microsoft’s error text “Your data gateway is offline or couldn’t be reached”. Open the error details and look for this code:
DM_GWPipeline_Client_GatewayUnreachable
On the gateway machine, open the on-premises data gateway app. A connection problem at sign-in can appear as “Network request returned unexpected error.” The app’s Network tab can also show “Connected” or “Disconnected.”
Power Automate and Power Apps administrators can open the Power Platform admin center, select Data, then open the gateway cluster. Select Check status to see whether it is online or offline. Open the cluster details and select the gateway status icon to check each member.
Find out whether you have standard mode or personal mode before continuing. Standard mode supports several Microsoft services and runs as a Windows service. Personal mode supports Power BI only and runs as an interactive application. A personal gateway can show “Not connected,” in which case Microsoft says to sign in again and check network access.
Run this on the gateway machine
The following script is read-only and needs no administrator rights. It does not change the gateway or Windows settings. It is intended for standard mode. With personal mode, the service result can be empty because personal mode does not run as a Windows service.
# Read-only. Run in Windows PowerShell on the machine where the gateway is installed. No admin needed.
# 1. Gateway version: compare it with Microsoft's list of the six supported releases.
$exe = 'C:\Program Files\On-premises data gateway\Microsoft.PowerBI.EnterpriseGateway.exe'
"Gateway version: " + (Get-Item $exe).VersionInfo.FileVersion
# 2. The gateway's Windows service: it should say Running, Auto.
$svc = Get-CimInstance Win32_Service -Filter "Name='PBIEgwService'"
"Gateway service: $($svc.State), $($svc.StartMode), runs as $($svc.StartName)"
# 3. When Windows last started.
"Windows started: " + (Get-CimInstance Win32_OperatingSystem).LastBootUpTime.ToString('yyyy-MM-dd HH:mm')
# 4. Shutdowns, restarts and sleeps in the last 7 days. Compare the times with the failed refreshes.
$since = (Get-Date).AddDays(-7)
@(
Get-WinEvent -FilterHashtable @{ LogName = 'System'; Id = 41, 1074, 6005, 6006, 6008; StartTime = $since } -ErrorAction SilentlyContinue
Get-WinEvent -FilterHashtable @{ LogName = 'System'; ProviderName = 'Microsoft-Windows-Power-Troubleshooter'; Id = 1; StartTime = $since } -ErrorAction SilentlyContinue
) | Sort-Object TimeCreated | ForEach-Object {
$msg = $_.Message -replace '[^\x20-\x7E\r\n]', ''
if ($_.Id -eq 1) {
$slept = [datetime]([regex]::Match($msg, 'Sleep Time: (\S{19})').Groups[1].Value + 'Z')
$woke = [datetime]([regex]::Match($msg, 'Wake Time: (\S{19})').Groups[1].Value + 'Z')
$text = 'Asleep from ' + $slept.ToString('yyyy-MM-dd HH:mm') + ' to ' + $woke.ToString('yyyy-MM-dd HH:mm')
} else { $text = @($msg -split "`r?`n" | Where-Object { $_.Trim() })[0] }
[pscustomobject]@{ Time = $_.TimeCreated.ToString('yyyy-MM-dd HH:mm'); Id = $_.Id; 'What happened' = $text }
} | Format-Table -AutoSize -Wrap
The version line tells you which installed build to compare with Microsoft’s six supported releases.
The service line should say Running, Auto. It also identifies the Windows account used to run the service.
The Windows started line tells you whether the machine restarted near the first failed refresh.
The final table shows power events. Event 6005 means Windows started. Event 6006 is a clean shutdown. Events 6008 and 41 indicate an unclean shutdown, such as a crash or power cut. Event 1074 means a person or program requested a shutdown or restart. “Asleep from” lines come from the Windows Power Troubleshooter.
What our test gateway showed
Tested on: on-premises data gateway 3000.338.3 (October 2026 release), standard mode, Windows 11 Home 64-bit, Windows PowerShell 5.1, 14 November 2026.
| Check | Result |
|---|---|
| Machine | TEST-GW |
| Gateway version | 3000.338.3, inside the six supported releases |
| Gateway service | Running, Auto, runs as NT SERVICE\PBIEgwService |
| Windows started | 2026-11-12 16:40 |
The script found these events in the laptop’s local time:
| When | What the System log says |
|---|---|
| 2026-11-07 22:58 to 2026-11-08 20:30 | asleep |
| 2026-11-08 22:51 to 2026-11-09 09:04 | asleep |
| 2026-11-10 23:06 | shutdown requested (shutdown.exe); Windows started again 2026-11-11 08:18 |
| 2026-11-11 23:17 to 23:24 | three restarts for a Windows update (TrustedInstaller, “Operating System: Upgrade (Planned)”) |
| 2026-11-12 22:30 to 2026-11-13 19:52 | power off chosen from the Start menu, recorded as sleep 11 seconds later |
| 2026-11-13 22:38 to 2026-11-14 11:14 | asleep |
A refresh scheduled for early morning would have found this gateway offline on every morning of that week.
The gateway’s own “On-premises data gateway service” event log showed nothing while the machine slept. It only logged “Started the ‘PbiEgwService’.” after each real start, 6 to 25 seconds after Windows started. The Windows System log showed the sleep periods. A gateway log with no errors does not prove that the gateway was up.
The power plan said “Sleep after: Never,” but the laptop still slept every night because someone selected Sleep or Shut down from the Start menu. The sleep setting alone does not prove that the machine stays on.
This was a test gateway installed on a laptop. We did not produce an Offline status in Power BI ourselves. The status and error texts above come from Microsoft’s documentation.
The checks, in order
Was the machine asleep, off, or restarting?
Compare the failed refresh time with the script’s sleep, shutdown, restart, and startup events. If the machine was unavailable at that time, you have a direct explanation for the Offline status.
Microsoft’s installation guidance says, “Don’t install a gateway on a computer, like a laptop, that might be turned off, asleep, or disconnected from the internet.” It adds that the gateway can’t run in any of those cases.
Wake or start the machine and confirm that it has internet access. If Windows restarted for an update, allow the gateway service time to start and then check the status again. Repeated overnight events mean the lasting fix is to keep that machine awake or move the gateway to an always-on machine.
Is the gateway service stopped?
For standard mode, PBIEgwService should be Running and set to start automatically. You can restart it from Service Settings in the gateway app, from Windows Services, or from an administrator Command Prompt. Restarting the service requires administrator access.
Check the account named by the script. The default gateway service account is NT SERVICE\PBIEgwService. It is separate from the account used for cloud sign-in and from the credentials used to reach your data.
Windows generally reports error 1069, “The service did not start due to a logon failure,” when configured service credentials are rejected. If your company changed the gateway to run under a person’s domain account and that password changed, have an administrator correct the account through the gateway app. Changing the service account requires the recovery key.
Is the gateway version out of support?
Microsoft releases a gateway update each month and supports the latest six releases. Its supported monthly updates list showed these versions on 14 November 2026:
| Release | Version |
|---|---|
| May 2026 | 3000.318 |
| June 2026 | 3000.322 |
| July 2026 | 3000.326 |
| August 2026 | 3000.330 |
| September 2026 | 3000.334 |
| October 2026 | 3000.338 |
Our installed file version was 3000.338.3. The Microsoft Download Center listed that full build as the October release and the newest build on the date we checked.
If your version is older than May 2026, update it. Download the latest standard mode or personal mode installer and run it. A gateway administrator can also use the update indicator under Manage Gateways in the Fabric or Power BI portal.
This table is a dated check, not a permanent list. A November release may replace May as the oldest supported release.
Is the network or proxy blocking the gateway?
The gateway makes outbound connections. Microsoft lists TCP ports 80, 443, 1433, 5671, 5672, and 9350 through 9354. It does not require inbound ports.
Open the gateway app and select Diagnostics. Under Network ports test, select Start new test. The result should be “Completed (Succeeded).” If it says “Completed (Failed, see last test results),” open the results and check which ports or hosts are closed.
If your firewall permits only ports 80 and 443, open the Network tab and turn on HTTPS mode. Select Apply. The gateway service restarts automatically.
A proxy must be configured in both gateway files with matching settings. Microsoft documents the proxy configuration and account requirements. Check these files:
C:\Program Files\On-premises data gateway\Microsoft.PowerBI.EnterpriseGateway.exe.config
C:\Program Files\On-premises data gateway\enterprisegatewayconfigurator.exe.config
Ask whoever manages the firewall or proxy to compare its logs with the failed refresh time. A successful test once does not rule out an intermittent block.
Is one cluster member down?
A cluster can stay available through another member, but an offline member still needs attention. The cloud service normally uses the primary member and moves to another available member when needed.
Open the cluster details in the Power Platform admin center. Check every member’s status and version. Microsoft recommends disabling or removing an offline member and keeping all members on the same gateway version.
Start or repair the offline member before enabling it again. If the primary member is down, restore it as well, especially when the cluster supports Dataflow Gen2 connections.
What should you collect from the logs?
In the gateway app, select Diagnostics, then Export logs. The app saves a zip file in the ODGLogs folder on the Windows desktop.
In Event Viewer, open Applications and Services Logs, then select On-premises data gateway service. Also open Windows Logs, then System. The gateway log shows service activity. The System log is where shutdown, restart, power, and sleep evidence appears.
Gateway service logs include information, error, and network files. Their timestamps use UTC, so account for the time difference when comparing them with local refresh history and Windows events.
When it is back online
Check the refresh schedule after restoring the gateway. Power BI switches a refresh schedule off after four consecutive failures, or after an error that requires a settings change. Set Configure a refresh schedule back to On and select Apply.
Run a manual refresh, then confirm that the next scheduled refresh also completes. Our guide to Power BI scheduled refresh not working covers the refresh history, credentials, timeouts, and schedule settings.
If the gateway lives on a laptop or a desk PC
Move the gateway to a supported machine that stays on, stays awake, and keeps its network connection. Find the recovery key before starting. Microsoft cannot retrieve the recovery key, and you need it to move or recover the gateway.
Microsoft groups migrate, restore, and take over into one installer flow. Migration moves the existing gateway registration to another machine. Restore or take over reconnects an installation to the existing gateway by using its recovery key. Expect active refreshes to fail during a move when the cluster has only one member.
When to hand it over
Hand the problem over if the service will not stay running, the network test fails, or the evidence does not match the failed refresh times.
With our Fix it service, we find the cause on the gateway machine, fix it, and check that the next scheduled refresh runs. We leave you a plain note covering what stopped, what changed, and what to watch.
Frequently asked questions
Why does my on-premises data gateway keep going offline?
The machine may be sleeping or shutting down, the service may be stopping, or the connection to Azure Relay may be blocked. An old gateway version or an offline cluster member can also be involved. Compare the Windows System events with each failed refresh time before changing settings.
Why is my gateway offline after a server restart?
The gateway service might still be starting, or it might have failed to start under its configured account. Check whether PBIEgwService says Running and Auto. If Windows shows error 1069, have an administrator check the service account credentials.
Which on-premises data gateway versions are supported?
Microsoft supports its latest six monthly releases. On 14 November 2026, those were May through October 2026, versions 3000.318 through 3000.338. Check Microsoft’s current list because the supported window moves when a monthly release ships.
Why does my personal gateway show offline?
Personal mode is an interactive Power BI application, not a Windows service. It depends on the Windows user and the personal gateway being signed in and connected. If it shows “Not connected,” sign in again and check network access. Installing another personal gateway on a different computer replaces the previous installation for that user.
How we checked this: every status text, version and rule on this page was checked on Microsoft Learn and the Microsoft Download Center on 14 November 2026. We ran the check script on our own test gateway (on-premises data gateway 3000.338.3, standard mode, Windows 11) the same day.
