The headline is "GA." The feature list is not new. Most of what follows has been shipping for months, and the reader value lies in knowing what you're getting, where it stops, and how to try it safely.
What the extension is
The extension is a free, open-source GUI for VS Code. It targets Azure DocumentDB and any MongoDB API-compatible database. The marketplace listing describes it as a free DocumentDB GUI and MongoDB GUI for Azure DocumentDB, DocumentDB and MongoDB (including Atlas).
The Microsoft GitHub repository says one extension covers three groups:
- Azure DocumentDB and Azure Cosmos DB for MongoDB (RU), with Microsoft Entra ID sign-in.
- The open-source DocumentDB engine, on a laptop, a VM or in Kubernetes.
- MongoDB Atlas, self-hosted MongoDB, and any other database that speaks the MongoDB API.
The project is MIT-licensed. It runs on Windows, macOS and Linux, and bundles its own shell and query runtime.
How you connect
The repository documents several routes:
- Azure browsing: clusters and accounts appear across subscriptions and tenants, and in the Azure Resources view. You sign in with Entra ID, or with a managed identity when VS Code runs on an Azure VM.
- DocumentDB Local: a setup option starts a local instance in Docker or Podman, with a persistent volume, generated credentials and optional sample data.
- MongoDB Atlas: sign in with a service account or API key, then pick a cluster.
- Kubernetes: clusters on AKS, EKS, GKE, kind, minikube or Docker Desktop are found from your kubeconfig, and port forwarding is handled for you.
- Connection string: the fallback for anything else.
The 365Fanatic mirror of the Azure update also lists Azure Cosmos DB for MongoDB accounts and self-hosted servers. It says authentication supports Entra ID and managed identity.
Three ways to work with the same query
- Collection View: build queries with filter, project and sort editors. Browse results as Table, Tree or JSON, and edit documents in place.
- Interactive Shell: a full shell in the VS Code terminal. It reuses your saved connection, including Entra ID credentials. Familiar commands such as
show dbsanduse <db>work, and variables persist between commands. - Query Playground: JavaScript in
.documentdb.jsfiles, with a Run button per block. Because a playground is an ordinary file, you can commit it and share it with your team.
Microsoft's own 1.0 notes add a caveat. Loops, aggregations and multi-statement blocks may not map back to the visual Collection View.
Diagnosing slow queries
Query Insights works in three steps: the query plan, then execution statistics with a Good, Fair or Poor rating, then optional AI recommendations. The AI step needs the GitHub Copilot extension. The repository says it sends the query shape and execution statistics, not your documents. The three core query workflows don't need Copilot.
Index management sits beside it. You can see which indexes are used, create standard, wildcard and vector indexes, and hide an index to test the impact before deleting it. The Cluster Dashboard shows connection status, round-trip time, and an inventory of databases and collections with storage and document counts. Microsoft describes it as a snapshot you refresh on demand, not a live monitor.
Version history
Don't read GA as the arrival of 1.0. Microsoft's GitHub discussion announced version 1.0 on October 14, 2026. That release arrived alongside DocumentDB 1.0, which the DocumentDB site dates to October 19, 2026. The 1.0 release itself was mostly fixes and polish. It also raised the minimum VS Code version to 1.109.0.
Later patches matter if you're deciding what to install:
- v1.0.1 renamed the product to "DocumentDB extension for Visual Studio Code," with "DocumentDB" as the short in-product name. The extension ID
ms-azuretools.vscode-documentdb, settings, saved connections and commands are unchanged. - v1.0.2 adds cloud-aware Entra ID sign-in for Azure US Government, Azure China and custom clouds. It also mitigates reported security issues in connection links and token handling. Microsoft recommends that all users update. It restricts which hosts can receive Entra ID tokens, and custom domains must be trusted through a machine-scoped setting.
The available sources don't establish whether these patches were part of the GA event. Check which build you actually have.
Getting started
- Make sure VS Code is 1.109.0 or later.
- Open the Extensions view (Ctrl+Shift+X) and search for DocumentDB. Install it and reload if prompted. From a terminal, DocumentDB's quickstart gives
code --install-extension ms-azuretools.vscode-documentdb. Add--forceto update an older install. - For a local database, you need Docker Engine or Docker Desktop (or Podman) running Linux containers. Docker must be reachable from the environment where VS Code runs. Use the DocumentDB Local setup option.
- For Azure, sign in with Entra ID and browse your clusters. Otherwise paste a connection string.
Reload VS Code after updating, because the running window keeps using the previous version until you do. If you use mongodb+srv:// connections, note that an earlier release fixed querySrv EBADRESP failures on networks that return compressed SRV replies.
Limits to keep in mind
- Feature parity isn't guaranteed. Microsoft says available commands, sign-in methods, metrics and index types depend on the connected database and your permissions. Crawford Group Holdings notes it didn't test parity across engines.
- Free software isn't free hosting. The extension costs nothing, but the databases you connect to may. The Azure update text doesn't cover pricing for connected services.
- Copy and paste isn't a migration service. The repository says it suits development and small-to-medium datasets. For large production migrations it recommends a dedicated service. The separate Azure DocumentDB Migration extension is a different product.
- Network and permissions still apply. Crawford Group Holdings advises trying it first against a development database with minimal permissions and keeping production write access out of the trial. That is the outlet's own advice, not Microsoft guidance, but it is sensible. An editor extension makes a database easier to reach without changing who should be allowed to modify it.
Analysis
The GA label is a maturity signal for a tool that was already shipping and is already at 1.0.x. This is general industry reasoning rather than anything Microsoft stated. Teams that were waiting for a "production-ready" designation before standardizing on it now have one. Teams on a mixed estate (Azure, Atlas, local containers) get one interface and one saved-connection model across all of them.
If you manage developer workstations, there's one concrete task. Make sure users are on 1.0.2 or later, and check that sovereign-cloud users have the right cloud selected in VS Code.
References
- (Launched) Generally Available: DocumentDB extension for VS Code Azure Updates · 2026-11-17T20:00:32Z
- DocumentDB extension for Visual Studio Code github.com
- DocumentDB extension for Visual Studio Code v1.0 Released! 1️⃣.0️⃣ · microsoft vscode-documentdb · Discussion #1012 · GitHub github.com