Microsoft published its list of SQL announcements for Ignite 2026 on November 16, 2026. The update spans Azure SQL Database, Azure SQL Managed Instance, SQL database in Fabric, SQL Server and the developer tools around them, with a mix of general availability releases and new previews.
Three items stand out for developers and DBAs. Hyperscale now accepts cross-database queries in preview, a local container that mimics Azure SQL Database enters public preview, and Database Hub in Microsoft Fabric reaches general availability as a single view over SQL, PostgreSQL and Cosmos DB estates.
Hyperscale Gets Cross-Database Queries
The headline engine change is a preview of cross-database querying for Azure SQL Database Hyperscale. Databases that sit in the same Hyperscale elastic pool can now be combined in one T-SQL query for reports, analytics or application logic.
Microsoft frames this as a migration unblocker. Many SQL Server applications reference objects in other databases with three-part names, and that habit has long forced rewrites when moving to Azure SQL Database. Teams can now keep separate databases with their own permissions instead of merging them or building copy pipelines.
The post also repeats that Hyperscale supports scale to zero through a serverless auto-pause preview announced earlier, with databases starting at 10 GB. Microsoft says it positions Hyperscale as the default target for both new apps and modernized ones.
Security and Search Features
Several security items moved forward at the same time:
- Regex-based dynamic data masking is now generally available, which helps mask values whose length varies.
- AES keys for Transparent Data Encryption with customer-managed keys in Azure SQL Database are GA, as an option next to RSA keys.
- TDE encryption scan suspend and resume is in public preview, so admins can pick when the scan runs.
- Database-level managed identity in Azure SQL Database is in public preview, giving each database its own passwordless identity for reaching external data.
- Built-in fuzzy string matching is GA for comparing messy names and spotting likely duplicates inside SQL.
Local Development and Tooling
A public preview of a local development container for Azure SQL Database also arrived. It is meant to be kept current with the cloud service, so you can explore Azure SQL behavior on a laptop without creating a billable resource.
The MSSQL extension for VS Code and SSMS can both create that container for you. The VS Code extension also adds Microsoft Entra sign-in and support for Podman, WSL and Apple Silicon, a Local-to-Cloud Deployment Wizard preview that guides a laptop database onto the no-cost tier of Azure SQL Database, and a Query Performance Dashboard preview built on Query Store.
SSMS gains Hot Exit and refreshed bacpac and dacpac wizards in preview, plus Fabric SQL database creation as a GA feature.
GitHub Copilot in SSMS now supports bring your own model, including models served through Foundry Local. Version 170.5 of SqlPackage and version 2.3 of the SQL Projects SDK are now GA, bringing versioned deployments, scripts that run before the plan is built, and an export switch that forces Azure compatibility.
Data API builder can now pick up new configuration when you redeploy an existing instance rather than creating a fresh one, and its CLI offers a Docker-free way to run it locally.
Database Hub, Agents and Operations
Database Hub in Microsoft Fabric is now generally available. It gathers discovery, monitoring and tuning for Microsoft SQL, PostgreSQL and Cosmos DB in one place, and flags end of support and maintenance issues across groups of databases.
Copilot in Database Hub enters public preview for natural language questions about performance. Database Agents gain three previews: better issue detection, AI skills that examine queries and execution plans, and evidence-based suggestions for rewrites, hints and indexes that a person reviews before applying.
Alerts for Azure SQL Database, built on Fabric Activator, are in preview and can trigger Teams messages or Power Automate flows across one or many databases.
Managed Instance, Fabric and SQL Server Updates
- The zone-redundant Next-gen General Purpose tier for Azure SQL Managed Instance is GA, with a flexible memory option and log throughput up to 220 MB/s.
- MI link support for Always On availability groups holding several databases is GA.
- Managed Instance backup immutability for PITR backups beyond 7 days and for LTR backups is in public preview.
- SQL database in Fabric adds GA restore of deleted databases to a point in time and smaller maximum vCore choices.
- Public previews also cover running SQL Server 2025 on Ubuntu 26.04 LTS, and version 2 of the Best Practices Assessment for Arc-enabled SQL Server, which now handles failover cluster instances.
Migration tooling also moved: Database Migration Service now works with VNet peering and custom DNS servers, and assessments in SSMS, Azure Arc and Azure Catalyst now suggest Hyperscale tiers and elastic pool sizing.
What It Means for Developers
The cross-database query preview is the item most likely to change migration plans. If an application was held on SQL Server or Managed Instance because of three-part names, test whether grouping its databases in one Hyperscale elastic pool removes the blocker before committing to a rewrite.
The local container deserves a look by anyone who targets Azure SQL Database but develops against a full SQL Server image today. Running tests against a container that tracks cloud behavior should catch feature gaps earlier. Keep in mind that most of these items are previews, so check the support terms before using them in production.
For background on related changes, see our report on managed performance monitoring for Azure SQL Managed Instance and the backup immutability lock for Azure SQL.
Conclusion
Microsoft's Ignite 2026 SQL release set pushes Hyperscale as the main Azure SQL target, adds cross-database queries to ease SQL Server moves, and gives developers a local Azure SQL container. Database Hub GA and new agent previews aim at the operations side, while security gains such as regex masking and AES keys for TDE are ready for production now.
Sources
See my articles more often when you search Google.
