This semantic model uses a deprecated gateway version. Upgrade required.

We also started seeing those messages on reports connected to several of our gateway clusters this past week. 

Similar to what was stated in DClark21044​'s post, we have also generally stayed one version behind without users receiving messages like this in the past. 

We will be doing some restarting and maintenance on those impacted gateway clusters tomorrow, but just wanted to let DClark21044​ know, you are not alone with your scenario.

DClark21044​ 

This is more likely the gateway deprecated warning rather than Power BI refresh failure.

Suggested pathway:

• Restart the gateway service, as you already did.
• Upgrade the gateway to the latest available version instead staying one version behind.
• Check that all gateway cluster nodes are running the same version.
• If the warning persists for some users after the upgrade/restart, allow some time for the Power BI Service to refresh its gateway status, hope these steps will eradicate your problem.
  
  Please accept this answer yes and give kudos if this is helpful

DClark21044​  If it's critical, reach out to your Fabric Admin and raise a support ticket. So that issue will be sorted ASAP

Hi DClark21044​ ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

Regards,
Chaithanya

Hi all,

Here another victim looking for an answer.
Over the last month, we've started receiving "Refresh succeeded with critical warnings" alerts for virtually all semantic model refreshes that use an on-premises gateway to connect to a SQL Server. This is the first time in 4 years that I get this template alert. As you can imagine, this has resulted in a flood of emails landing in our inboxes every day.
The warning indicates that the gateway version is deprecated and may stop working in the future. The thing is, when the alerts started, our gateway was only a few versions behind the latest release. We immediately upgraded to the August 2026 version, but the warnings have continued unchanged.
We're now considering upgrading again to the September 2026 release, but ideally we don't want to be forced to run the very latest gateway version at all times, especially in enterprise environments.
Has anyone from Microsoft been able to confirm whether these warnings are expected behavior, a bug, or an indication that the gateway will genuinely stop working soon if not updated to the latest version?

Also, is opening a MS support ticket the recommended path to get clarification on this, or is there already guidance available on the deprecation policy behind these alerts?

Would appreciate any insights from the product team or others experiencing the same issue.

Current GW Version: 3000.330.1

Thanks!

Hi DClark21044​ ,

Thank you for the update. Since restarting the gateway cluster only reduces the frequency and does not resolve the issue, this suggests a temporary gateway/node state rather than a permanent fix.

Since upgrading the gateway is restricted by your organization's policy, please check the following:

• Confirm all cluster nodes are running the same gateway version.
• Collect the gateway logs before restarting the cluster when the issue occurs.
• Check Event Viewer on each gateway node for errors at the time of failure.
• If possible, identify whether the issue occurs on a specific gateway node by taking nodes out of rotation one at a time.

Thanks,
Chaithanya.

We are also having this issue and are unable to do the upgrade so we have to create new gateway/connections and then update the gateways for our existing models. We have reached out to Microsoft to find out how long before the gateway is deprecated but had no response. 

This sounds more like a gateway-version warning/service-state issue than an actual refresh failure, especially since restarting the gateway cleared it for many users.

Microsoft says Power BI can show gateway warnings during the 90 days before a gateway version reaches end of support; after that, refresh/DirectQuery operations can eventually be blocked.

A few things I would check:

Check the exact gateway version on every node in the cluster. Don't rely only on the gateway UI—confirm both Primary and Secondary.

Check Microsoft's currently supported gateway versions and determine whether your version is actually unsupported or simply not the latest recommended version.

Since restarting cleared the warning for many users, restart the gateway service on all cluster members, one at a time.

For the users/models where the warning remains, check whether their semantic models are actually mapped to the same gateway cluster/data source.

Check refresh history. If refreshes are succeeding, this is currently a warning rather than an outage. Power BI documents that outdated gateway versions can produce warnings even when the refresh completes successfully.

If you're only one monthly release behind and still within Microsoft's supported window, you don't necessarily need to panic or immediately upgrade every gateway just because the service recommends a newer build. Similar warning behavior has been reported in the Fabric community.

Given that this suddenly appeared across many reports and restarting the gateway fixes it for some users, I'd first verify the exact gateway build/support status and restart both cluster members before doing a production upgrade.

Hi DClark21044​ ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

Regards,
Chaithanya