A laptop displays a cloud database platform connected to coding, search, AI, and security tools.
Azure Cosmos DB Shell has reached general availability. Microsoft's Azure Updates entry carries the "Launched" label, which the Azure Updates page defines as a fully released, production-ready product available to all Azure customers. The preview label is gone, and the shell now joins the production toolbox for anyone running Cosmos DB. The question for teams is what they should check before pointing it, and especially its AI features, at live data.

A laptop displays a cloud database platform connected to coding, search, AI, and security tools. What was announced​

The announcement describes the shell as a terminal-style way to work with Azure Cosmos DB. The GA text, as reproduced by the 365Fanatic update tracker, lists these capabilities:

  • Navigating Cosmos DB resources.
  • Querying and managing data.
  • Importing and exporting datasets.
  • Inspecting settings such as indexing and throughput.
  • Working from a terminal, Visual Studio Code or the Azure portal.
  • MCP integration, so AI agents can use familiar shell commands.

The wording is Microsoft's own, and the productivity claims ("work faster without building custom tooling") are marketing, not measurements. I couldn't verify the exact publication time on the live Azure Updates page, which rendered no items when it was inspected. The tracker's copy dates the item November 17, 2026. It also lists a separate November 30 date that I couldn't confirm, so I'm leaving that out.

A short history​

  • May 6, 2026: Microsoft announced the public preview. It was an open-source CLI with bash-like syntax and MCP support.
  • October 1, 2026: Microsoft's Cosmos DB blog announced that you could open the shell from Data Explorer in the Azure portal. That post said plainly that the shell is still in preview.
  • November 17, 2026: The GA announcement. It lists the terminal, VS Code and the portal as ways to use the shell.

Some documentation still lags. Search results show a Learn page that says the shell is currently in private preview. Another Learn page is titled "(preview)". Microsoft's current Learn overview, last updated November 17, 2026, describes the shell without that label. If you see "preview" text on older pages, treat it as stale rather than as a contradiction of the GA notice.

What you can do with it​

The current Microsoft Learn overview gives the clearest picture of the command set:

  • Navigation and inspection: connect, cd, ls, pwd and info.
  • Diagnostics: doctor, whoami, can-i and sampled schema discovery, for checking connections and permissions.
  • Queries: queries, including query --explain to see observed index usage, and point reads with print.
  • Item operations: create, replace, patch and delete.
  • Batch and bulk writes: batch for atomic operations within one partition, and bulk for independent operations across partitions. bulk offers dry runs, concurrency controls and resumable journals.
  • Import and export: JSON or CSV streaming, with offline import validation.
  • Container management: indexing, throughput, TTL and conflict-resolution policies, plus stored procedures, user-defined functions and triggers.
  • Scripting: pipelines, variables, loops and functions.

The same page says the shell also offers a change-feed follower (watch) and OpenTelemetry tracing. I haven't tested any of this. Some of these commands may have appeared during the preview rather than at GA, so don't read the whole list as new in this release.

Installing it​

The Learn overview names three distribution routes:

  1. Visual Studio Code: install the Azure Cosmos DB extension and run Launch Azure Cosmos DB Shell.
  2. .NET global tool: this needs .NET SDK 10.0 or later.
  3. Self-contained binary: this needs no separate .NET install.

It lists Windows, macOS and Linux support, with x64 or ARM64 packages. Authentication options are Microsoft Entra ID, managed identity or an account key.

The documented quick start launches cosmosdbshell from your terminal. Inside it you run connect with your account URL and tenant ID, then info, ls, schema and a bounded query. Microsoft notes that these reads consume request units (RUs). It also says the shell doesn't bypass account firewall or private-network restrictions.

One caution for Windows admins: an install page indexed in search still shows --prerelease on the dotnet tool install command. That page could be stale after GA. Check the current install guide and run cosmosdbshell --version before scripting the command into a build image.

The portal route is the quickest way to try it. On an Azure Cosmos DB for NoSQL account, open Data Explorer and select Open Cosmos DB Shell. Microsoft's October post says the shell opens in a new tab already connected to that account, so there's no connection string to paste. That post also says the same commands work in the standalone shell, so a portal investigation can become a script. Whether the portal surface has left preview is not clearly established by the sources I could inspect.

The MCP angle needs the most care​

MCP lets AI clients call shell commands as tools. In the May preview post, Microsoft said the shell exposes its commands to an AI assistant. These include navigation, queries, and data changes such as create item, update and rm. The post also lists schema-management commands such as mkdb, rmdb, mkcon and rmcon.

The current Learn overview says the optional local MCP server lets trusted clients use tools with the shell's connection and permissions. It adds that MCP needs separate setup and can read or change data under the configured permissions, so you should review tool calls before approving them. It also advises against sharing credentials or sensitive data.

In practice:

  • An agent inherits whatever access your session has. If the shell connects with an account key or a broad role, so does the agent.
  • Use narrow identities for agents. The preview post recommended Entra ID for interactive sessions and managed identity in production, with account keys only for prototyping.
  • Keep the MCP server on localhost. The preview post said it binds to localhost by default. Confirm that against current documentation rather than assuming it.
  • Try read-only first. A third-party ITNext guide describes read-only MCP access. I couldn't confirm that setting in Microsoft's documentation, so verify it yourself.
  • Use can-i and whoami. Microsoft's own tools let you check who the shell thinks you are and whether an operation will be permitted, before anything changes data.

Logging and telemetry​

The shell's GitHub repository says the tool itself collects no telemetry, usage data or crash reports. Requests to your account are still processed and logged by the Azure service like any other client's. Diagnostic logs depend on your account's diagnostic settings. This is repository text, not a formal GA guarantee, so treat it as guidance. Teams with audit requirements should turn on account diagnostic settings if they haven't already, since that is where evidence of scripted or agent-driven changes would appear.

What this changes for you​

  • Developers get one CLI that runs the same way in a terminal, VS Code and the portal.
  • Platform and database admins get scriptable policy inspection and bulk operations with dry runs. That's useful for CI/CD pipelines and migration reviews.
  • Security teams now have a supported, open-source (MIT-licensed) tool that can feed agent workflows. Review how it is permitted to run, not just whether it is permitted.

The sources I inspected don't establish a GA-specific SLA, pricing, regional availability or support lifecycle for the shell. The shell itself is open source, but the RUs consumed by its reads and writes bill against your account as normal. Don't plan around anything beyond what the documentation currently says.

GA is a good moment to test the shell on a non-production account. Run the read-only commands first, then dry-run your bulk operations. Leave MCP switched off until you've decided which identity an agent should use.

 

References

  1. (Launched) Generally Available: Azure Cosmos DB Shell Azure Updates 2026-11-17T20:00:32Z
  2. Azure Cosmos DB Shell Public Preview: AI-Powered CLI devblogs.microsoft.com
  3. github.com github.com