Skip to content

Commit 739831b

Browse files
committed
Update sentinel-service-limits.md
1 parent d539be9 commit 739831b

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

articles/sentinel/sentinel-service-limits.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,16 @@ The following limits apply to incidents in Microsoft Sentinel.
6161
| Number of incidents returned by API to *list* request | 1,000 incidents maximum | None |
6262
| Number of incidents per day (per workspace) | See explanation after table | Database capacity |
6363

64+
## Case management limits
65+
66+
The following limits apply to case management in Microsoft Sentinel.
67+
|
68+
| Description | Limit | Dependency |
69+
|--------------------|-----------------------------------------|------------|
70+
| Number of cases | 100,000 cases per tenant | None |
71+
| Linked incidents | 100 incidents linked to each case | None |
72+
| Attachments | 500 GB of attachments per tenant | None |
73+
6474
**Number of incidents per day:** There isn't a formal, hard limit on the number of incidents that can be created per day. A workspace's actual capacity for incidents depends on the storage capacity of the incident database, so the size of the incidents is as much a factor as their number.
6575

6676
However, a SOC that experiences the creation of more than *around* 3,000 new incidents per day will most likely find itself unable to keep up, and the database capacity will quickly be reached. In this situation, the SOC needs to find and fix any rules that create large numbers of incidents, to get the count of daily new incidents to manageable levels.

0 commit comments

Comments
 (0)