DocumentDB for VS Code Extension v0.11

We are excited to announce DocumentDB for VS Code Extension v0.11. Explore your databases at a glance with the new Cluster Dashboard, work faster in a more helpful Interactive Shell, connect from Azure VMs with Managed Identity authentication, and carry indexes along when you copy and paste collections. Local setup is more dependable, too.

What’s New in v0.11

⭐ Cluster Dashboard

We are introducing a major new feature: the Cluster Dashboard. Opened from a cluster tree node, it gives you a focused inventory of everything a cluster holds, without leaving VS Code. The dashboard shows an overview with cluster identity, connection status, round-trip time, and Azure high-availability facts, plus a details view with server and other metadata you can copy directly.

Cluster Dashboard for Contoso Production showing connected and high availability status, cluster storage and document metrics, and a filterable database inventory with storage, data, index, collection, and document statistics

Below the header, a database and collection inventory reports storage, data, index, collection, and document statistics where the server provides them, with sorting, filtering, drill-in, refresh, create, and delete actions. Open Shell and Copy Connection String are one click away, and a failed or partial read shows a clear retry state instead of a guessed number.

Use the dashboard to get oriented and navigate your cluster on demand. It presents a snapshot of your data rather than a live view of running operations.

⭐ A More Helpful Interactive Shell

The Interactive Shell now helps you find your way from the first prompt, with more context up front and useful guidance as you type.

Know where you are

The new connection header shows your saved connection name, host, authentication method, active database, and identity when available. For example:

Connected to: Local development (mycluster.example.com)
Identity: admin | Authentication: Username and Password (SCRAM) | Database: myDatabase

With Microsoft Entra ID account sign-in, the header makes your signed-in identity just as clear:

Connected to: Production (prod.example.com)
Identity: alex@contoso.com | Authentication: Microsoft Entra ID (Account) | Database: inventory

Discover as you type

After connecting or switching databases, collection suggestions are prepared for you. Type db. to see how many collections are available in the current database; press Tab to browse their names and the database methods. Once you finish typing a method, the shell explains it before you run it:

myDatabase> db.
  🛈 7 collections

myDatabase> db.restaurants.countDocuments
  🛈 Counts documents matching a filter (uses aggregate)

Complete the query with ({}) to count documents. Previously entered commands can also appear as inline history suggestions, and terminal resizing or narrow widths no longer disrupt your input and cursor.

Let Tab handle tricky names

For a collection named restaurants-something, the shell previews the bracket notation it needs. Press Tab to replace the dot notation with valid syntax:

myDatabase> db.rest
  🛈 ['restaurants-something']

myDatabase> db['restaurants-something']

Need to change how the shell behaves? Run help and follow the clickable link directly to the Interactive Shell settings.

Learn more in the Interactive Shell user manual.

⭐ Managed Identity Authentication

We’ve added managed identity authentication for Azure DocumentDB (vCore) connections from VS Code running on Azure VMs. Connect with a system-assigned or user-assigned identity, and keep using it across the Collection View, Query Playground, and Interactive Shell. Your choice is remembered when you save, reconnect, or update a connection, with guidance when an identity endpoint is unavailable or a cross-tenant configuration is unsupported.

Signing in is easier to navigate, too. Choose Username and Password, Microsoft Entra ID, or No Authentication first; if you choose Microsoft Entra ID, you can sign in with your account, use a managed identity from the connection string or current machine, or enter a user-assigned identity’s client ID. You can return to the authentication choice at any step.

Learn more in the Managed Identity user manual.

⭐ Copy and Paste Indexes

We’ve extended Copy and Paste Collections with full support for indexes, so you no longer have to recreate them by hand, whether you’re copying an entire collection or just moving index definitions on their own.

  • Indexes with your collection: When you paste a collection, choose whether to recreate eligible secondary indexes on the target. To protect the data being copied, TTL and unique indexes are not included in this option; copy the documents first, then apply those indexes with the dedicated workflow below.

  • Indexes on their own: Use Copy Index…, Copy Selected Indexes…, or Copy Indexes… on a collection’s Indexes node, then Paste Indexes… into a target collection, database, or another connected cluster. This workflow can include TTL and unique indexes without moving any documents.

Existing equivalent indexes are skipped, conflicting names are handled automatically, and vector options and hidden-index state carry over. Your copied selection stays ready for the next target, making it easy to apply the same indexes across collections. Learn more in the Copy and Paste user manual.

Key Fixes and Improvements

  • DocumentDB Local Quick Start Reliability
    • Set up or start fresh with greater confidence: Quick Start checks that setup can proceed before removing an existing data volume.
    • See useful Docker errors promptly and catch unsupported credentials or empty ports during configuration.
    • Pick up where you left off after an interrupted setup or external container or data removal. Your instance password stays out of the setup output channel, and temporary credentials are cleared as soon as the container starts.
  • Settings Organization
    • Find settings in eight expandable sections: General, Connections & Discovery, Queries & Results, Copy & Paste, Query Playground, Interactive Shell, AI Assistant, and Accessibility.
    • Shell and Query Playground connection timeouts now share documentDB.connectionTimeout. Nine settings have been renamed; if you customized any of the old settings, set their new equivalents again because previous values are not migrated.
  • Azure Discovery Connections
    • Connect more reliably to Azure Cosmos DB for MongoDB (RU) clusters from the Azure Resources view. Azure VM Discovery also shows VMs without a reachable address as unavailable, so you can see them without attempting a connection that cannot succeed.
  • Connection Startup Diagnostics
    • See whether a slow connection is waiting on Microsoft Entra ID authentication or the database, with separate timing information across Collection View, Interactive Shell, and Query Playground.
  • Completion and UI Polish
    • Field completions and Collection View now show document fields instead of internal BSON properties, including MinKey and MaxKey fields in completions.
    • Keyboard focus remains visible on the Create Index drawer’s Standard and Vector tabs. When you select multiple connections, the deletion command clearly says Delete Selected Connections.

Changelog

See the full changelog entry for this release: ➡️ CHANGELOG.md#0110

Patch Release v0.11.1

This patch release restores SRV connections on affected networks and makes database tooltips and query documentation safer without changing your stored data or everyday workflows.

What’s Changed in v0.11.1

💠 SRV Connections Work Again on Affected Networks (#993, #997)

After a recent VS Code update, some mongodb+srv:// connections started failing before they reached the database, with querySrv EBADRESP. This happens when the built-in DNS resolver rejects compressed replies sent by some home routers, phone hotspots, VPNs, or corporate DNS servers, even though other tools on the same machine can connect.

The extension now automatically tries a fallback for affected DNS lookups, using the same DNS servers your system is configured with. This works across the tree, Collection View, Interactive Shell, and Query Playground, without requiring you to replace your connection string or change your network settings. The resolved server list stays in memory: saved connections, Copy Connection String, and exports keep the original mongodb+srv:// string.

Connections whose DNS lookups already work keep their existing behavior. Fallback connections look up the server list again when a new connection is created, but do not periodically refresh it while open. If resolution still fails, the error provides guidance and a link to the new SRV DNS troubleshooting guide, including workarounds and support options.

💠 Safer, More Readable Tooltips and Documentation (#996)

Index tooltips now display database metadata as literal content rather than interpreting it as links, HTML, icons, or commands. Index and shard-key details remain readable even when values contain backticks, newlines, or other special characters. Your database names and stored values are unchanged.

Operator hovers and completion documentation in Collection View and Query Playground no longer allow command links. Regular web documentation links, formatting, and query completions continue to work as before.

Changelog

See the full changelog entry for this release: ➡️ CHANGELOG.md#0111

Patch Release v0.11.2

DocumentDB for VS Code v0.11.2 updates panel loading, contributor tooling, and the checks used before shipping.

What’s Changed in v0.11.2

💠 Lighter Panel Loading (#880)

Panels now load their own code on demand. Local Quick Start and Atlas Credentials do not load the document editor or results grid dependencies. Other panels continue to load the components they need.

💠 Updated Contributor Tooling (#880)

The extension host and webviews now build with Vite instead of webpack. Unit tests use Vitest instead of Jest, and the legacy Mocha harness is removed. The extension and all seven workspace packages use ES modules, with TypeScript 6 for development.

For package consumers, @documentdb-js/operator-registry, @documentdb-js/shell-api-types, and @documentdb-js/shell-runtime 0.9.0, plus @documentdb-js/schema-analyzer 2.0.0, are ESM-only and require Node.js 22.18.0 or later. Review each package’s migration notes before upgrading.

💠 Checks Before Shipping (#880)

CI inspects the packaged extension, reports size changes on each pull request, and tests activation after installing the VSIX. Package verification also runs in CI and the Azure DevOps npm build. These checks help catch packaging failures before release.

Changelog

See the full changelog entry for this release: ➡️ CHANGELOG.md#0112