Skip to content

Revise Cosmos DB container requirements for Standard setup #729

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
georgeollis wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Revise Cosmos DB container requirements for Standard setup #729

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions articles/foundry/agents/includes/concepts-standard-agent-setup-content.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,15 +46,26 @@ All data processed by Foundry Agent Service is automatically stored at rest in t

Your Azure Cosmos DB for NoSQL account must have a total throughput limit of at least **3000 RU/s**. Both **Provisioned Throughput** and **Serverless** modes are supported.

Standard setup provisions **three containers** in your Cosmos DB account, **each requiring 1000 RU/s**:
The **Standard setup** provisions **five containers**, each requiring **1000 RU/s**:
Comment thread
georgeollis marked this conversation as resolved.
Comment thread
georgeollis marked this conversation as resolved.

| Container | Purpose |
|-----------|---------|
Comment on lines +49 to 52
Copy link

Copilot AI Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The statement that the Standard setup provisions five containers is hard to reconcile with the later Classic/New split (New runtime uses only agent-definitions-v1 and run-state-v1). Please clarify whether users must provision all five containers in all cases, or whether the required containers (and RU/s totals) depend on which runtime they use.

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Contributor Author

@georgeollis georgeollis Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The service automatically provisions these containers for you

| `thread-message-store` | End-user conversations |
| `system-thread-message-store` | Internal system messages |
| `agent-entity-store` | Agent metadata (instructions, tools, name) |
| `agent-definitions-v1` | Agent metadata (instructions, tools, name, versions) |
| `run-state-v1` | Internal messages and end-user conversations |

For multiple projects under the same Foundry account, multiply by the number of projects. For example, two projects require at least 6000 RU/s (3 containers × 1000 RU/s × 2 projects).
`thread-message-store`, `system-thread-message-store`, and `agent-entity-store` are part of the **Foundry Agent Service (Classic)** Standard Setup.
Comment thread
georgeollis marked this conversation as resolved.

**Foundry Agent Service (New)** uses **`agent-definitions-v1`** and **`run-state-v1`**.
The older containers belong to the **Classic** experience and are not used by the new runtime.

---

## Information Warning

The **Classic** and **New** Foundry Agent Service runtimes use **different Cosmos DB containers**.
Comment thread
georgeollis marked this conversation as resolved.

## Project-level data isolation

Expand Down
Loading