Back
Database Management

Reliable database management for modern, high-performance systems.

Back
Data Modernisation

Reliable database management for modern, high-performance systems.

Back
Data Engineering

Reliable database management for modern, high-performance systems.

Back
Analytics & Intelligence

Reliable database management for modern, high-performance systems.

Back
Data Strategy Consulting

Reliable database management for modern, high-performance systems.

Azure SQL Query Editor Is Now Generally Available: A DBA's Hands-On Walkthrough

Kalaimani S
Published on
November 19, 2026
Azure SQL Query Editor is now generally available: a DBA's hands-on walkthrough

The Azure SQL query editor in the Azure portal is now generally available. Microsoft's release notes list general availability in September 2026, and the Azure SQL team announced it on its blog on 22 October 2026. The new version replaces the older single-pane editor with a proper workspace for Azure SQL Database: an Object Explorer, multiple query tabs, a results grid you can sort and filter, and one-click export.

Our DBA team tried it on a demo Azure SQL Database to see how far it goes for everyday work. Everything we checked ran inside the browser, with no client tools installed on the machine. This post walks through what we found, step by step, with screenshots from that environment, and ends with the limits worth knowing before you rely on it.

What is new in the Modern Query Editor

The query editor is a browser-based tool in the Azure portal for running T-SQL against an Azure SQL Database. The generally available release brings these changes.

FeatureWhat it does
Object ExplorerBrowse schemas, tables, views, stored procedures, functions and saved queries, with search by name
Multi-tab workspaceKeep several query tabs open in one browser session
IntelliSenseSuggests T-SQL keywords, schemas, tables, views and procedures while you type
Interactive results gridSort, filter and copy results, with the data type shown for each column
ExportDownload results as CSV, JSON or Excel (.xlsx)
TemplatesStarter T-SQL for new schemas, tables, views, stored procedures and functions
Open inPass the same database to Visual Studio Code or SQL Server Management Studio
AuthenticationMicrosoft Entra ID or SQL authentication
Classic experienceThe older editor is still available through a toggle

What is new in the Modern Query Editor

A walkthrough from our demo environment

The screenshots below come from a Geopits demo environment loaded with the SalesLT sample schema. The server and login happen to be named "prodserver", but this is a test database, not a production system.

1. Opening the query editor from the Azure portal

In the Azure portal, open the Azure SQL Database resource and select Query editor from the resource menu on the left. The editor opens in the same blade, with the Explorer pane on one side and New query, Templates and Open in along the top. There is nothing to install locally, which makes it handy on a machine that does not have SSMS.

Azure SQL query editor opened from the Query editor option in the Azure SQL Database resource menu
The query editor opened from the Azure SQL Database resource menu.

2. Signing in with Microsoft Entra ID or SQL authentication

The first screen asks how to connect. The editor supports passwordless Microsoft Entra authentication as well as native SQL authentication with a username and password. Sign-in happens inside the Azure portal itself, which ensures secure, identity-driven access to the database.

Each method needs a little groundwork. For SQL authentication, the login has to exist in the logical server's master database, or as a contained user in the database itself. For Entra authentication, the database needs Entra authentication configured and an Entra user created inside it. We cover the wider picture in our post on security in Azure SQL.

Azure SQL query editor sign-in screen with Microsoft Entra authentication and SQL authentication options
The sign-in prompt offers Microsoft Entra authentication and SQL authentication.

3. Getting around the Object Explorer

Once connected, the workspace opens with the Explorer on the left and a quick-start canvas in the middle. The tree is grouped by schema, with folders for tables, views, stored procedures and functions, and a Queries node at the bottom.

Modern Query Editor workspace showing the Object Explorer with schemas, tables, views, stored procedures and functions
The new workspace with the Object Explorer and quick-start canvas.

Expanding a table lists its columns with the data type, nullability and primary key shown inline. That covers the quick checks we would normally do with sp_help or a query against the system views, and it sits right next to the results grid.

Object Explorer in the Azure SQL query editor showing columns with data types, primary key and null constraints
Column names, data types, primary keys and nullability shown in the Explorer tree.

Right-clicking the Tables folder offers Create table and Refresh, so a newly created object appears in the tree without reconnecting.

Context menu in the Azure SQL query editor Object Explorer with Create table and Refresh options
Context menu on the Tables folder with Create table and Refresh.

4. Writing queries with IntelliSense

Typing in a query tab brings up suggestions as the statement takes shape. In our test the list offered T-SQL keywords, the dbo and SalesLT schemas, and stored procedures such as uspLogError and uspPrintError. Microsoft's documentation notes one gap: IntelliSense covers tables and views but not column names. For heavier development with full column completion, SSMS or VS Code is still the better place.

IntelliSense suggestions for T-SQL keywords, schemas and stored procedures in the Azure SQL query editor
IntelliSense suggesting keywords, schemas and stored procedures while typing.

5. Running a query and reading the results

We ran a multi-table aggregate query against the SalesLT schema: the top 10 customers with their total orders and total spend, joining the Customer table to SalesOrderHeader. The results load into a grid that shows the data type of each column. You can sort and filter the grid, and copy cells, rows or columns straight out of it.

Multi-table aggregate T-SQL query with results grid showing customers, total orders and total spend in the Azure SQL query editor
A multi-table aggregate query with results in the grid.

The Messages pane and the status bar report what happened. For a SELECT TOP 5 query, the Messages pane showed "Affected rows: 5" and the status bar showed the run took 1 sec 009 ms. The Copy messages button puts that output on the clipboard, which helps when recording what was run during troubleshooting or for audit notes.

Demodatabase · Query editorSQL query 3
▶ RunSave asSave as viewDownload .sql
SELECT TOP 5 * FROM SalesLT.Product;
MessagesResultsCopy messages
9:10:35 AM
Started executing on line 1Affected rows: 5Query executed successfully
Succeeded1 sec 009 msColumns: 17 · Rows: 5
Messages paneAffected rows: 5Row count for the last statement
Status bar1 sec 009 msTotal run time for the query
Copy messagesOne clickOutput ready to paste into a ticket or audit note

Messages pane and status bar after a query run in our demo environment

6. Exporting results to CSV, JSON or Excel

The results toolbar has three download options: CSV, JSON and Excel (.xlsx). The file comes straight from the browser. For a quick extract to share with an application team or to check offline, this works without external ETL or a separate client-side export tool.

Export query results from the Azure portal query editor as CSV, JSON or Excel xlsx
Download options for CSV, JSON and Excel in the results toolbar.

7. Working across multiple tabs and saved queries

Each New query opens a separate tab, so several ad hoc scripts can stay open in one browser session. We moved between them freely without losing what had been typed in each.

Multiple T-SQL query tabs open at the same time in the Azure SQL query editor
Several T-SQL query tabs open in one session.

The Explorer also lists these scripts under the Queries node (SQL query 1, SQL query 2 and SQL query 3 in our test), so it is easy to find and switch between them from the tree. These queries live in the browser rather than in the database, so anything worth keeping long term still belongs in source control.

Queries node in the Azure SQL query editor Explorer listing SQL query 1, SQL query 2 and SQL query 3
Scripts listed under the Queries node in the Explorer.

8. Creating objects from built-in templates

The Templates menu on the toolbar offers New Schema, New Table, New View, New Stored Procedure and New Function. Each opens a tab with standard T-SQL boilerplate for that object, ready to edit. It saves retyping the same CREATE structure and keeps new objects consistent.

T-SQL DDL templates menu in the Azure SQL query editor for new schema, table, view, stored procedure and function
The Templates menu with options for schemas, tables, views, procedures and functions.

9. Handing off to Visual Studio Code or SSMS

When a task outgrows the browser, the Open in menu passes the same database to Visual Studio Code (with the MSSQL extension) or SQL Server Management Studio. For us, this is the most practical part of the release. A quick check starts in the portal and moves to a full desktop tool in one click when the work needs it. If SSMS is new to your team, our guide on connecting to Azure SQL Managed Instance with SSMS covers the connection steps.

Open in menu in the Azure SQL query editor with Visual Studio Code and SQL Server Management Studio options
The Open in menu with Visual Studio Code and SQL Server Management Studio.

Fixing the most common connection error: the server firewall

The first problem most people run into is not the editor but the network. If the logical server allows only selected networks, the browser's public IP address has to be allowed through the server firewall before the editor can connect.

To fix it, open the SQL server (the server, not the database) in the Azure portal and go to Security, then Networking. With public network access set to Selected networks, select Add your client IPv4 address under Firewall rules and save. The editor also offers a one-click option to add the client IP when it detects this error.

Fixing the first connection error
  1. Open the SQL serverThe logical server, not the database
  2. Security > NetworkingPublic access settings for the server
  3. Selected networksPublic network access stays restricted
  4. Add your client IPv4 addressUnder Firewall rules
  5. SaveThe rule applies to the whole server
  6. ReconnectBack in Query editorConnected
prodserver · NetworkingSecurity

Public network access

DisableSelected networks

Firewall rules

Allow certain public internet IP addresses to access your resource.

+ Add your client IPv4 address ()+ Add a firewall rule
Rule nameStart IPv4 addressEnd IPv4 address
The new rule appears here after you save

Allowing the client IP through the server firewall. The IP address is masked.

Two related points from Microsoft's documentation. The editor now uses only TCP port 443, so outbound HTTPS has to be open on your local network. And when Private Link is set up and the connection comes from inside the virtual network, the firewall rule is not needed.

Limits to know before relying on it

Microsoft positions the editor for lightweight querying and exploration, and the documented limits reflect that.

LimitWhat it meansWhat to do instead
Five-minute timeoutAny query still running after five minutes is stoppedRun long jobs in SSMS or VS Code
Last result onlyA batch with several statements shows only the last one's resultsRun statements one at a time, or switch to a desktop tool
No master databaseThe editor cannot connect to the logical server's master databaseUse SSMS or VS Code for server-level work
No read-only replicaConnections with ApplicationIntent=ReadOnly are not supportedQuery replicas from a desktop tool
Partial IntelliSenseTables and views are suggested, column names are notUse the Explorer tree to look up columns
1,000-row previewThe data preview for a table or view stops at 1,000 rowsWrite a query or export the results
Serverless pauseA paused serverless database must resume first, about a minuteSelect Continue, wait, then refresh

Documented limits, from Microsoft Learn as of October 2026

The editor applies to Azure SQL Database. For a side-by-side view of how it differs from Managed Instance and Amazon RDS, see our comparison of RDS SQL Server, Azure SQL Database and Azure SQL Managed Instance. These limits may change as Microsoft updates the editor.

Where it fits in a DBA's day

For us, the editor earns its place in the small moments. Checking whether a row landed after a deployment. Looking up a column's data type during a call. Pulling a quick CSV for an application team. Confirming a login works after a firewall change. It is quick to reach, needs no setup on a borrowed laptop, and access stays inside the Azure portal.

Which tool for which job

Query editor in the browser

Quick checks, nothing to install
  • Confirm a row landed after a deployment
  • Look up a column's data type during a call
  • Pull a quick CSV, JSON or Excel extract
  • Test a login after a firewall change
  • Create an object from a template
Open in
one click

SSMS or VS Code

Longer and deeper work
  • Performance tuning
  • Anything that runs past five minutes
  • Long-running maintenance
  • Full IntelliSense, including columns
  • Work on master or read-only replicas

How we split the work between the browser and the desktop

It does not replace SSMS or VS Code for serious work. Performance tuning, long-running maintenance and anything that runs past five minutes still happen on the desktop. The Open in menu makes that switch painless, so we treat the two as one workflow rather than a choice between them.

If you would rather have someone watch over your Azure SQL estate day to day, take a look at our remote DBA services. Teams still moving workloads to Azure can start with our cloud database migration practice.

Frequently asked questions

1. Is the Azure SQL query editor generally available?

Yes. Microsoft lists the Azure portal query editor for Azure SQL Database as generally available from September 2026 and announced the release on 22 October 2026. The classic experience is still available through a toggle.

2. How do I open the query editor in the Azure portal?

Open the Azure SQL Database resource and select Query editor in the resource menu. Then sign in with Microsoft Entra ID or SQL authentication.

3. Why can't the Azure SQL query editor connect to my database?

The most common cause is the server firewall blocking your browser's public IP address. Add your client IPv4 address under Security > Networking on the logical server, and make sure outbound port 443 is open on your network.

4. Can I export query results to Excel from the Azure portal?

Yes. The results toolbar can download results as CSV, JSON or Excel (.xlsx) straight from the browser.

5. Does the Azure SQL query editor replace SSMS?

No. It is built for quick queries and exploration. Queries time out after five minutes and IntelliSense does not cover columns, so the Open in menu hands longer work over to SSMS or Visual Studio Code.

6. Which authentication methods does the query editor support?

It supports Microsoft Entra authentication and SQL authentication. Entra needs an Entra user in the database, and SQL authentication needs a login in master or a contained database user.

Wrapping up

The generally available query editor makes quick T-SQL work in Azure SQL Database much easier than it used to be, and the handoff to SSMS and VS Code covers the rest. For more hands-on notes from our DBA team, browse the Geopits blog. If a second pair of eyes on your Azure SQL environment would help, talk to our team or request a free database audit.

Related reading

Sources: Microsoft Tech Community, Modern Query Editor for Azure SQL Database is now generally available; Microsoft Learn, Azure portal query editor for Azure SQL Database.

Kalaimani S, Database Administrator at Geopits

Kalaimani S

Kalaimani S is a Database Administrator at Geopits, part of the DBA team that monitors client database environments around the clock. Certifications include Microsoft Applied Skills: Migrate SQL Server workloads to Azure SQL Database, Oracle Certified Professional MySQL 8.0 Database Administrator, and Nutanix Certified Professional Database Automation 6.

Our Latest Blogs

From monitoring to modernization, GeoPITS provides expert database management services that enhance performance, strengthen security, and reduce operational costs.

Ready to Transform Your Data?

Geopits works alongside your team as a strategic partner, starting with stabilizing your current databases, then modernizing your data infrastructure, and ultimately helping you unlock the full potential of AI.

170

Happy Clients so far

2100+

Databases Managed

142+

Successful Migrations

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.