Last updated on November 6, 2026
Microsoft Purview service limits are documented thresholds that affect how eDiscovery work is licensed, indexed, preserved, divided, exported, and validated. They may have little practical effect on a focused matter, but larger populations can require several policies, searches, processes, or export packages. Each additional operation creates another point where the eDiscovery function has to confirm scope, identify exceptions, and reconcile results before review or production decisions rely on them.
Microsoft provides important native preservation, search, audit, collection, review, and export capabilities across Microsoft 365. Cloudficient helps legal teams connect those capabilities to matter-driven identification, preservation, and collection decisions. CaseFusion® carries identity, activity, repository, content, and matter context across the discovery lifecycle so separate operations can remain connected to the scope counsel approved.
Purview licensing and configuration determine which eDiscovery functions and capacity are available to a matter.
Partially indexed items may be returned even when their contents were not fully available to keyword search.
Broad preservation scope may require several hold policies that represent one matter-level obligation.
Large exports can create several packages, shared-capacity constraints, and additional reconciliation work.
Limit management begins when one authorized population has to be divided, rerun, supplemented, or handled through a separate path.
Microsoft controls Purview's documented thresholds; Cloudficient adds matter context and workflow coordination around the resulting discovery operations.
Microsoft Purview service limits are documented thresholds and operating conditions that govern features, indexing, searches, holds, review activity, exports, and related processes. The current Purview experience brings eDiscovery workflows into one portal, while licensing, billing configuration, indexing thresholds, hold capacity, and export capacity continue to shape how a matter is executed.
The practical effect depends on scope. A focused inquiry may fit comfortably inside one hold, search, process, and export. Greater scale can divide the same logical population across several operations. The legal decision remains one decision, even when the technology has to implement it through several jobs or policies.
Cloudficient treats those divisions as matter-level coordination points. Completion of an individual Purview operation is one part of validation. The combined operations also need to represent the sources, period, content, and document states counsel intended to preserve or collect.
A service limit does not necessarily prevent the work. It changes the execution design and the documentation needed to connect separate operations to one matter scope.
Licensing affects Purview eDiscovery by determining which features, workflows, and capacity are available to the case, users, and data involved. The organization's subscriptions, add-ons, case settings, user and data licensing, permissions, and billing configuration can affect preservation, search, export, review sets, analytics, advanced indexing, OCR, and API use.
A unified portal can make these functions appear to belong to one consistent experience, but availability still depends on the prerequisites in place. Confirming those prerequisites at intake helps avoid designing a workflow around a function, capacity, or billing model that is not available to the matter.
CaseFusion complements the native Microsoft 365 workflow by connecting the people, sources, activity, and matter decisions that shape what the process needs to accomplish. Licensing confirmation remains a tenant and matter-planning responsibility.
Indexing limits can affect search coverage when an item matches through indexed properties even though some of its content was not fully available to keyword search, sampling, OCR, or native viewing. The parent item may appear in results while content inside an attachment, nested file, image, spreadsheet, or oversized item follows a different treatment.
The following limits were source-checked against Microsoft documentation in October 2026:
|
Documented limit |
Operational effect |
|
150 MB maximum email attachment parsed for indexing |
A larger attachment is not parsed, and the message is marked partially indexed. |
|
30 seconds maximum parsing time per item |
An item that exceeds the limit is marked partially indexed. |
|
4 MB maximum Excel file size in the native viewer |
Larger spreadsheets need another inspection path. |
|
24 MB maximum file size for OCR with Premium feature support |
Larger image-based files require another text-extraction or inspection path. |
|
10 MB maximum item size in a search sample |
Larger items may not appear in the sample; the full results, export, or review-set workflow may be required when the result is material. |
Search-time and export-time settings for partially indexed items are separate. The matter plan should state whether these items will be included, exported, advanced-indexed where available, or inspected through another documented process.
CaseFusion's Context-Aware eDiscovery™ approach places that treatment inside the matter decision. An exception population has meaning because it can be connected to the people, sources, periods, and collection rationale that brought it into scope.
A returned parent item does not establish that its attached or embedded content was available to keyword search.
Purview hold limits affect preservation planning when the approved scope exceeds the capacity of one case hold or when tenant-wide policy volume approaches the applicable organizational threshold. One legal matter may then require several technical policies that have to remain aligned as custodians, locations, conditions, and release decisions change.
The following limits were source-checked against Microsoft documentation in October 2026:
|
Documented limit |
Operational effect |
|
10,000 hold policies with eDiscovery feature support; 20,000 with Premium feature support |
High matter volumes require tenant-wide capacity monitoring. |
|
1,000 mailboxes in one case hold; 2,000 with Premium feature support |
Broad custodian populations may require more than one hold policy. |
|
1,000 sites in one case hold; 2,000 with Premium feature support |
Broad SharePoint and OneDrive scope may require more than one hold policy. |
The higher site capacity depends on Premium feature support in the case. The approved source also records Microsoft's recommendation to use separate policies for Exchange mailboxes and for SharePoint and OneDrive sites. Current Microsoft documentation and the organization's configuration should be confirmed before a matter plan depends on these figures.
CaseFusion helps legal teams coordinate notices, preservation actions, status, exceptions, changes, and releases through a documented workflow. When several Purview policies represent one preservation scope, the matter documentation should connect each custodian and location to the policy that implements the decision.
Purview export limits affect execution when an authorized result set exceeds the capacity, throughput, file-size, or completion window of one export. The population may leave Microsoft 365 in several packages or over several days, creating additional reconciliation points among search results, reports, exported files, load files, and the review platform.
The following limits were source-checked against Microsoft documentation in October 2026:
|
Documented limit |
Operational effect |
|
2 TB from one search; 5 TB with Premium feature support |
Larger result sets require more than one export. |
|
2 TB organization-wide per day; 5 TB with Premium feature support |
Concurrent matters draw from shared daily export capacity. |
|
2 GB per hour per mailbox |
Mailbox concentration can increase elapsed time. |
|
10 GB maximum PST size |
Larger results are automatically divided into several PST files. |
|
Automatic cancellation after seven days |
An export that has not completed is cancelled; Microsoft recommends smaller batches. |
A technically successful export confirms what that export package produced under its configured conditions. Matter-level reconciliation connects the packages back to the authorized population, identifies omissions or errors, and records whether a later job supplemented or replaced an earlier one.
CaseFusion carries source and matter context into targeted collection and downstream analysis. That context can help legal teams and their partners understand why a population was collected, how separate packages relate to the scope, and which exceptions shaped the result.
A matter requires limit management when its intended scope cannot be executed as one operation and the resulting divisions need coordinated tracking, validation, and reconciliation. The warning signs are operational rather than theoretical.
Searches are divided by custodian, location, period, or query segment.
Several hold policies represent one preservation scope.
Processes are rerun, supplemented, cancelled, timed out, or replaced.
Partially indexed items follow a separate path.
Exports are divided across packages, days, or shared capacity.
Exceptions and retries have to be reconciled to an authorized population.
Cloudficient's decision-driven approach starts with the scope counsel approved and follows it through the operations used to carry it out. Better identification does not always produce a smaller scope. It produces a scope supported by better information.
Cloudficient helps legal and eDiscovery teams keep matter decisions connected when Microsoft 365 discovery work spans several locations, policies, jobs, or packages. Microsoft provides important native preservation, search, audit, and collection capabilities. CaseFusion connects identity, activity, repositories, content, and matter decisions across the discovery lifecycle.
CaseFusion can support the work around documented limits by helping legal teams:
identify the people and data sources connected to the matter;
coordinatelegal hold notices, preservation actions, status, exceptions, changes, and releases;
apply matter-selected collection and version policies using available context;
carry the rationale and source relationships into analysis and downstream workflows; and
document how separate operations relate to the scope counsel approved.
The value is matter continuity across the workflow. CaseFusion helps connect the surrounding decisions and context so separate Microsoft 365 operations can be understood as part of one matter.
Do Purview service limits prevent large eDiscovery matters?
Not necessarily. A documented limit may require the work to be divided across several policies, searches, jobs, or packages. The operational requirement is to connect those divisions to the approved scope and reconcile the combined result.
Can a returned Purview search result contain content that was not keyword searchable?
Yes. A parent item may be returned even when attached, embedded, oversized, encrypted, nested, or otherwise unsupported content was not fully available to keyword search. Partially indexed and exception populations require a defined treatment.
How many mailboxes or sites can one Purview case hold include?
The uploaded source records 1,000 mailboxes or sites with eDiscovery feature support and 2,000 with Premium feature support, as source-checked in October 2026. Confirm current Microsoft documentation and the case configuration before relying on those figures.
What happens when a Purview export exceeds a limit?
The export may have to be divided into several jobs or packages. Daily capacity, mailbox throughput, PST size, and the completion window can also affect elapsed time and package structure. The resulting packages should be reconciled to the authorized population.
Does CaseFusion increase Microsoft Purview's service limits?
CaseFusion adds matter context and workflow coordination around Microsoft 365 discovery operations. It connects identity, activity, repositories, content, and matter decisions across the lifecycle; Microsoft controls Purview's documented service thresholds.
How often should Purview service-limit content be reviewed?
Microsoft may change licensing, feature availability, terminology, and service limits. Cloudficient recommends confirming current Microsoft documentation and the organization's configuration before a matter plan depends on a specific figure or function.