No ETL between fresh application data and semantic retrieval.
Agentic development with Azure Cosmos DB
Why Cosmos DB fits AI applications, and how its developer experience is becoming agentic-first.
DevGlobeAn open-source talent graph where humans and AI agents discover developers through public contribution evidence.
Sajeetharan SinnathuraiPrincipal Product Manager · Azure Cosmos DB
Developer Experience and AI

An open-source talent graph
Humans and AI agents discover developers through public contribution evidence—not popularity alone.
What is hardest about AI + data?
The hard part is turning an AI demo into a reliable, safe system.
No votes yet.
Ground LLM responses on governed, continuously changing data.
Persist context, feedback, audit trails, and user state.
Reuse meaningfully similar responses to reduce latency and tokens.
Store durable state, checkpoints, transactions, and telemetry.
The audience for our guidance has changed.
“Agentic-first” means the correct path is discoverable, executable, and verifiable by an agent.
Cosmos DB expertise, available when agents code
What we learned building a production skill
Review this Azure Cosmos DB design. Workload: - Point-read a developer by login - Rank developers by country and language - Update stars and followers daily Proposal: one container, partition key /country. Use Cosmos DB Agent Kit guidance. Identify risks, ask for missing scale details, then recommend the model, partition key, indexes, queries, and SDK pattern. State assumptions and do not edit files yet.
Access patterns, cardinality, traffic distribution, growth, and consistency.
Explain why /country can create skew and why ranking queries may fan out.
Produce alternatives with tradeoffs, targeted projections, index needs, and SDK practices.
A command-line workspace for Cosmos DB
An interactive shell for navigating Cosmos DB resources, inspecting data, and running NoSQL queries from a concise command surface.
Navigate databases and containers
Inspect items and approximate schema
Run and iterate on queries quickly
Use the same tool vocabulary in demos and agent workflows
$ connect $ cd /devglobe/developers $ info $ query -m 5 'SELECT TOP 5 c.login, c.name, c.location, c.topLanguage FROM c'
MCP turns database operations into agent tools
The command line becomes an agent tool surface
Natural-language intent
Agent plans
MCP invokes shell tools
Cosmos DB executes
Agent explains + cites result
$ connect $ cd /devglobe/developers $ query -m 5 'SELECT TOP 5 c.login, c.name, c.location, c.topLanguage FROM c' 5 live developer profiles returned $ query 'SELECT VALUE COUNT(1) FROM c' Live container count returned Copilot › Show five developer profiles and summarize which fields are available.
NL2Query converts intent into a reviewable query
Describe the result
Ground on schema
Generate NoSQL query
Review, run, refine
Natural language in. Reviewable query out.
“Show the top 10 Python developers in Brazil with more than 1,000 followers.”
SELECT TOP 10 c.login, c.name, c.followers, c.totalStars FROM c WHERE IS_DEFINED(c.location) AND CONTAINS(c.location, "Brazil", true) AND c.topLanguage = "Python" AND c.followers > 1000 ORDER BY c.totalStars DESC
Relational source
developers countries languages repositories developer_repositories
Candidate document
{
"id": "octocat",
"location": "San Francisco, CA, USA",
"topLanguage": "TypeScript",
"followers": 18400,
"topRepos": [ ... ]
}
Give the agent a fast, disposable feedback loop
Launch the emulator and connect the extension.
Create database, container, partition key, and index policy.
Load synthetic OSS profiles and exercise real queries.
Review failures, query metrics, RU patterns, and generated code.
Intent + access patterns
Agent Kit plans
VS Code / Shell acts
Emulator verifies
Evidence drives revision