Microsoft Foundry Memory Store – Can the 100 Scope Limit Be Increased or Scaled?

Question

Microsoft Foundry Memory Store – Can the 100 Scope Limit Be Increased or Scaled?

Mohamed, Rihan 60

Title: Can the 100 Scope Limit in Microsoft Foundry Memory Store Be Increased?

Details:

I am evaluating Microsoft Foundry Agent Service Memory and noticed that the documentation lists the following limits:

Maximum scopes per memory store: 100

Maximum memories per scope: 10,000

Reference: Microsoft Learn – What is Memory?

I would like to understand how this limit should be handled when an application needs to support more than 100 users/scopes.

Can the 100 scopes per memory store limit be increased through a quota request or a different service tier?

If the limit cannot be increased, is it supported to create multiple memory stores and distribute users across them?

Can the same agent/application use multiple memory stores?

Is there a recommended Microsoft architecture for supporting more than 100 scopes?

I would appreciate any guidance or documentation on how to scale Foundry Memory beyond the 100-scope limit.Title:

Can the 100 Scope Limit in Microsoft Foundry Memory Store Be Increased?

Details:

I am evaluating Microsoft Foundry Agent Service Memory and noticed that the documentation lists the following limits:

Maximum scopes per memory store: 100

Maximum memories per scope: 10,000

Reference: Microsoft Learn – What is Memory?

I would like to understand how this limit should be handled when an application needs to support more than 100 users/scopes.

Can the 100 scopes per memory store limit be increased through a quota request or a different service tier?

If the limit cannot be increased, is it supported to create multiple memory stores and distribute users across them?

Can the same agent/application use multiple memory stores?

Is there a recommended Microsoft architecture for supporting more than 100 scopes?

I would appreciate any guidance or documentation on how to scale Foundry Memory beyond the 100-scope limit.

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer accepted by question author

Jose Benjamin Solis Nolasco 12,036 Volunteer Moderator

Welcome to Microsoft Q&A!

Hello @Mohamed, Rihan I hope you are doing well,

The documented limit is currently 100 scopes per Memory Store, and Microsoft does not document a quota request or higher service tier to increase this specific limit.

User's image

For applications with more than 100 users, one possible approach is to partition users across multiple Memory Stores, for example:

Users 1–100    → Memory Store A
Users 101–200  → Memory Store B
Users 201–300  → Memory Store C

However, Microsoft does not currently document that a single agent can directly use multiple Memory Stores, so this should be treated as an application-level sharding approach and validated against the API version you're using.

Also note that each scope supports up to 10,000 memories, with documented limits of 1,000 search and 1,000 update requests per minute.

Since Memory is currently in preview, these limits and capabilities may change.

References:

If this answer helped clarify the platform capabilities and save you troubleshooting time, please consider marking it as Accepted. This helps others in the community find similar solutions.

0 comments

2 additional answers

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

Based on the documented limits, the 100 scopes per memory store value is a quota for Memory in Foundry Agent Service, and the available quota guidance does not indicate that this specific limit can be increased.

The documented limit increase guidance distinguishes between:

Model quotas, which can be increased by request
Agent Service limits, where listed service limits can be fixed and can’t be increased

For Memory specifically, the documented quotas include:

Maximum scopes per memory store: 100
Maximum memories per scope: 10,000
Search memories: 1,000 requests per minute
Update memories: 1,000 requests per minute

So, from the available documentation, the supported conclusion is:

No documented path exists to increase the 100-scope-per-store limit through a quota request or service tier.
No documented Microsoft architecture is provided here for scaling beyond 100 scopes.
No documentation in the provided material confirms whether a single agent/application can use multiple memory stores.

What is documented is that memory is implemented through memory stores, and that memory management includes store-level controls and item-level CRUD. That supports the concept that memory is organized around stores, but the provided documentation does not explicitly state multi-store scaling guidance or agent-to-multiple-store support.

References:

Answer 2

Hello @Mohamed, Rihan

Thanks for reaching out to Microsoft Q&A.

Based on the current Microsoft Foundry Agent Service Memory documentation, the following quotas apply to a memory store:

Maximum scopes per memory store: 100

Maximum memories per scope: 10,000

Search memories: 1,000 requests per minute

Update memories: 1,000 requests per minute

These values are documented under the Memory service's Limitations and quotas section.

1. Can the 100-scope limit be increased?

The current Microsoft documentation does not document a quota-request process or a higher service tier for increasing the 100-scopes-per-memory-store limit.

Therefore, based strictly on the published documentation, we should treat 100 scopes per memory store as the currently documented service quota. We would not recommend assuming that a standard quota request can increase this limit.

2. Can multiple memory stores be used to support more than 100 users/scopes?

Microsoft does support creating multiple memory stores. The Memory usage documentation recommends creating a dedicated memory store for each agent to establish clear boundaries for memory access and optimization.

However, the current documentation does not state that multiple memory stores can be combined/sharded for the same agent specifically to bypass the 100-scope-per-store quota.

Therefore, we cannot confirm from the documentation that distributing users across multiple memory stores is a supported scaling mechanism for exceeding the 100-scope limit.

3. Can the same agent/application use multiple memory stores?

The documentation confirms that memory can be attached to a prompt agent and that memory stores can be created and managed. It also describes a memory store as the persistent storage boundary for an agent.

However, the current Microsoft documentation does not explicitly document a configuration in which one agent is simultaneously associated with multiple memory stores.

Therefore, I would not recommend stating that this configuration is supported unless it is confirmed by the Foundry Agent Service product team.

4. How is user-level isolation intended to work?

The documented mechanism for separating users within a memory store is the scope parameter.

Microsoft states that the scope parameter segments memory across users to provide isolated experiences. When using the memory search tool, automatic scope resolution can also be performed using scope = {{$userId}}.

Therefore, the documented model is essentially:

Memory store → scopes → memories

with each user's memories isolated through their scope.

5. What should be done if the application requires more than 100 scopes?

Based strictly on the current Microsoft documentation, there is no documented configuration for extending a single memory store beyond 100 scopes, and there is no documented architecture that uses multiple memory stores as a sharding mechanism to overcome this limit.

For an application requiring more than 100 user scopes, I recommend validating the intended architecture with the Foundry Agent Service product team before implementation rather than assuming that multiple memory stores can be used to bypass the quota.

Also, Memory is currently a public preview capability, so its quotas and supported capabilities may evolve.

Please refer this Microsoft documentation:

Memory in Microsoft Foundry Agent Service (preview)

Create and use memory in Foundry Agent Service (preview)

Foundry Agent Service limits, quotas, and regional support

Microsoft currently documents a maximum of 100 scopes per memory store. There is no documented quota-increase mechanism for this limit, and the documentation does not currently confirm using multiple memory stores or attaching multiple stores to the same agent as a supported way to exceed the 100-scope limit.

I Hope this helps. Do let me know if you have any further queries.

If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

Thank you!

SRILAKSHMI C 19,730 Reputation points Microsoft External Staff Moderator

2026-09-03T16:48:06.0666667+00:00

Hi @Mohamed, Rihan,

Following up to see if the above answer was helpful. If this answers your query, please do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Thank you!