Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

lrtoyou1223
Microsoft Employee
‎03-18-2026 05:46 AM

On-premises data gateway auto-update (admin triggered) (Generally Available)

If you haven’t already, check out Arun Ulag’s hero blog “FabCon and SQLCon 2026: Unifying databases and Fabric on a single, complete platform” for a complete look at all of our FabCon and SQLCon announcements across both Fabric and our database offerings. 

The on-premises data gateway auto-update (admin triggered), this capability gives administrators greater control over how and when gateway updates are applied, making it easier to align with organizational maintenance windows, change management processes, and compliance requirements.

With auto-update (admin triggered), gateway administrators can trigger upgrades on demand. This helps organizations adopt new features, performance improvements, and security patches at a time that best fits their operational needs.

What’s new with auto-update (admin triggered)

With this release of auto-update (admin triggered), administrators can:
  • Trigger gateway updates on demand instead of installing/uninstalling in local machines.
  • Control update timing to match internal maintenance windows and policies.
  • Reduce operational risk by planning and validating updates before deployment.
  • Apply updates programmatically using PowerShell or scripts for automation scenarios.
  • Standardize update processes across multiple servers or clusters.
Auto-update (admin triggered) is especially useful for enterprises that require staged deployment, validation in test environments, or strict change control procedures.

Baseline version requirement

The November 2025 release serves as the baseline version for the auto-update (admin triggered) feature. Gateways must be updated to this version (or later) to use auto-update (admin triggered) capabilities.

Getting started

  1. Update to the baseline version - Ensure your gateway is running the November 2025 release or a newer version.
  2. Check for available updates in the gateway UI - Open the on-premises data gateway UI. When a newer version is available, you will see an update indicator that shows version availability details.
Screenshot_of_the_gateway_manual_update_from_the_UIScreenshot_of_the_gateway_manual_update_from_the_UI

Figure: Administrators can trigger on-premises data gateway auto-updates to quickly apply the latest improvements, security fixes, and reliability enhancements.

  1. Trigger the update manually - Select the update icon to start the manual upgrade process when you are ready.
  2. Use PowerShell for programmatic updates (optional) - You can also initiate updates through PowerShell or automation scripts.
Example:

Update-DataGatewayClusterMember -GatewayClusterId DC8F2C49-5731-4B27-966B-3DB5094C2E77

This enables centralized and repeatable update workflows across environments.

Looking ahead

Auto-update (admin triggered) is a key step toward more flexible and enterprise-ready gateway lifecycle management. We will continue investing in update and maintenance experiences, including additional automation and management options to further simplify gateway operations at scale.

To learn more about gateway update options and best practices, explore the documentation: Update an on-premises data gateway.

Labels:
0