Skip to content

SPE: Update Container Type limit per tenant #10277

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.

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

Merged
merged 3 commits into from
May 21, 2025
Merged
Changes from all commits
Commits
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
12 changes: 6 additions & 6 deletions docs/embedded/development/limits-calling.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Limits and Calling Patterns
description: This article explains the limits of SharePoint Embedded.
ms.date: 11/16/2024
ms.date: 05/21/2024
ms.localizationpriority: high
---

Expand All @@ -10,15 +10,15 @@ ms.localizationpriority: high
This document explains the limits of SharePoint Embedded during public preview.

> [!NOTE]
> These are preview limits which are subject to change.
> These are preview limits that are subject to change.

## Size limits

The following table defines the size limits of containers"
The following table defines the size limits of containers:

| Resource | Limit |
| --------------------------------------------------------- | ------------------------------------------------------ |
| Container types that a partner tenant can create | 5* |
| Container types that a partner tenant can create | 25* |
| Container types that an app can own | 1 |
| Containers of a container type per consuming tenant | 100k* |
| Storage per container type per consuming tenant | 100 TB* |
Expand All @@ -44,7 +44,7 @@ In general, the following are the best practices to handle throttling:
- Avoid request spikes.
- Honor the `Retry-After` HTTP header.

In both cases, a `Retry-After` header is included in the response indicating how long the calling application should wait before retrying or making a new request. Throttled requests count towards usage limits, so failure to honor `Retry-After` might result in more throttling.
In both cases, a `Retry-After` header is included in the response, indicating how long the calling application should wait before retrying or making a new request. Throttled requests count towards usage limits, so failure to honor `Retry-After` might result in more throttling.

## API rate limits

Expand All @@ -53,7 +53,7 @@ SharePoint Embedded provides various APIs. Different APIs have different costs d
| Resource units per request | Operations |
| -------------------------- | -------------------------------------------------------------------------- |
| 1 | Single item query, such as get item |
| 2 | Multi-item query, such as list children Create, update, delete, and upload |
| 2 | Multi-item query, such as list children, create, update, delete, and upload |
| 5 | All permission resource operations, including $expand=permissions |

> [!NOTE]
Expand Down