Azure SQL Database Now Supports Portal-Based Restarts and Failovers
Database administrators can now restart or fail over Azure SQL databases directly through the Azure portal. This capability applies to single databases, Hyperscale databases, and databases within elastic pools.
What changed From the source
Microsoft has made it possible to restart or fail over databases directly within the Azure portal. The update removes the previous requirement to write scripts against the Rest API or reach out to support for these actions.
The newly supported functionality covers several deployment models within Azure SQL Database. Users can manage single databases, Hyperscale databases, and databases configured in elastic pools using this interface.
- Direct restart and failover capability added to the Azure portal
- Supports single databases
- Supports Hyperscale databases
- Supports databases in elastic pools
- Eliminates the need for REST API scripts or support tickets
At a glance · SQL Server & Data
What changedWhy it mattersWho should careUpgrade and migration considerations
Why it matters Analysis
By moving database restart and failover operations into the graphical user interface, the update streamlines routine administrative tasks. Teams managing Azure SQL infrastructure can handle maintenance and troubleshooting scenarios more rapidly without building or maintaining custom automation scripts.
This reduction in operational friction improves overall responsiveness during incident management, allowing operators to execute necessary database restarts immediately through the browser.
- Reduces reliance on custom REST API automation scripts
- Accelerates troubleshooting and incident response workflows
- Simplifies daily database management tasks
Who should care Analysis
Database administrators, cloud engineers, and operations teams managing Azure SQL deployments are directly affected by this feature. Teams that previously relied on support channels or internal scripting to trigger database restarts or failovers will find their workflows simplified.
Developers and architects working with Hyperscale databases or elastic pools can also benefit from improved visibility and control during testing and maintenance cycles.
- Database administrators overseeing Azure SQL environments
- Cloud operations teams responsible for infrastructure reliability
- Developers working with Hyperscale or elastic pool configurations
Upgrade and migration considerations Analysis
The source material does not specify any required migration steps, downtime windows, or configuration updates to utilize this portal feature. Because the change is implemented directly in the Azure portal, no application code modifications or SDK updates are mentioned as necessary.
- No specific migration steps or application changes mentioned in the source
- Feature is natively available via the Azure portal
Sources and further reading
- Original post on Azure Updates (original source)
Original: “Generally Available: Restart databases in Azure SQL DB via the Azure portal”, Azure Updates, published 2 Nov 2026, retrieved 2 Nov 2026. This article was drafted with AI assistance from the official source and passed automated fact and quality checks. Spotted a mistake? See our corrections policy.