Microsoft Purview is notorious for being almost good enough. Purview is Microsoft 365’s native collection tool, yet its functionality, especially for Freedom of Information Act (FOIA) and Public Records Act (PRA) requests, often leaves something to be desired.

What is Microsoft Purview?

Purview is built directly into Microsoft 365 as its native eDiscovery function. It boasts the capability to search, hold, and export content across Exchange, SharePoint, OneDrive, and Teams. It ships as part of Microsoft 365 compliance licensing, with Premium features gated behind an E5 plan or add-on. Yet the platform also poses serious challenges that leave records officers in the weeds, struggling to meet deadlines.

Why should you care about Purview’s limitations?

If you belong to either of these groups, Purview’s limitations can directly affect your day-to-day.

• As records officers and FOIA/PRA coordinators, you need response time and cost predictability. You need to be able to communicate a deadline and a fee structure to your constituents that you can keep to. With Purview, it’s all too common to discover a licensing or capacity ceiling mid-request, one that unravels into a missed statutory deadline. Beyond that, Purview’s review environment cannot extend to the request intake, tracking, and delivery parts of your workflow. Which leaves you with a fragmented process that frankly involves too many clicks.
• As IT and records-department staff, you can collect directly from Purview, but that only covers one piece of your tech stack. Everything else, Slack, Dropbox, Google Drive, and the rest, still means logging into each tool’s backend separately to pull data out by hand. What you actually want is one centralized portal that every collection runs through.

None of this is a knock on the product. It’s a licensing and compliance tool doing what it was built to do, and Microsoft’s own published limits describe where that scope ends. A few examples: the indexing service caps text extraction from a single parsed item at 2 million characters, so a large record in production may only be partially searchable. A targeted search is recommended to cover no more than 1,000 mailboxes or sites at a time, though a tenant-wide search can reach further. And a review set displays a maximum of 1,000 items per page, which means filters do a lot of the navigation work once a request gets large.

Individually, none of these are dramatic, but together they create real roadblocks for PRA or FOIA response.

How should public records offices account for these limitations?

For most agencies, this doesn’t mean replacing Microsoft 365 eDiscovery. It means recognizing the point where a request’s size, complexity, or audience outgrows what a compliance-focused tool was built for. It means adding a layer that picks up from there instead of asking Purview to do a job it wasn’t designed for. It means finding a solution that doesn’t leave you with a pounding headache and your constituents with responses of subpar quality.

Signs it’s time to add a purpose-built public records layer:

• Multiple concurrent PRA or FOIA requests are bumping into per-case document or review-set ceilings. That usually means you need a system built to run many requests at once without hitting per-case limits.
• Records need to securely go out to a citizen requester, reporter, or oversight body outside your Microsoft tenant. Purview’s review environment wasn’t built for releasing data to people outside the tenant.
• Reviewers keep running into partially indexed or unsearchable large files in production. Those files may be exceeding indexing limits and are only partially searchable.
• Records staff have to route every search or export through IT because of tenant-wide permission requirements. The records office loses the self-service speed a dedicated review layer is built to give back.

What this looks like in practice

There are two main ways public records teams can add a dedicated public records layer:

1. Drag-and-drop a Purview export. Your team can drag and drop every Purview export straight into Logikcull, where processing takes over: indexing, deduplication, and the Inclusive Email feature, which collapses repetitive email threads down to their unique content. What comes out the other side is data set up for review, rather than a tangled raw export. From there, purpose-built review features speed up the work itself, and the same intake portal that took in the request carries it through response, so nothing splits across two disconnected systems. This is exactly the play they run at Fairfax County, which has allowed them to keep up with a 200% surge in FOIA requests regarding email records.
2. Direct Microsoft 365 integration. The second path skips Purview’s collection step entirely. Rather than exporting from Purview and dragging that export into a second system, agencies connect directly to Microsoft 365 for collection, so records arrive already organized and ready for the same search, redaction, and production work. One less export to manage, and the same purpose-built review and intake layer either way.

Common questions about Microsoft 365 eDiscovery for public records

What is Microsoft 365 eDiscovery?

It’s the eDiscovery (Standard) and eDiscovery (Premium) capability built into Microsoft Purview, used to search, hold, and export content from Exchange, SharePoint, OneDrive, and Teams.

Is Microsoft Purview enough for FOIA and public records requests?

As request volume, document complexity, or the need to release records outside the Microsoft tenant grows, many agencies find that Microsoft Purview alone isn’t enough and add a dedicated layer to keep up.

What are the indexing and search limits in Microsoft Purview?

Per Microsoft’s own documentation, the indexing service caps text extraction at 2 million characters per item, targeted searches are recommended to cover up to 1,000 locations, and review sets display up to 1,000 items per page.

Can a dedicated eDiscovery platform work alongside Microsoft 365’s Purview for public records response instead of replacing it?

Yes. Many agencies take advantage of Purview’s collection capabilities, but because of its limited processing capabilities, they connect a dedicated platform to organize, validate, and produce that data, rather than replacing the Microsoft tools outright.

Whether a records office keeps collecting through Microsoft 365 or adds a dedicated layer on top of it, the goal is the same: get records out the door without missing a deadline. Logikcull is the AI-powered eDiscovery and public records response platform built for the high-frequency requests agencies face every day. Essential to 1,500+ organizations including the largest state and local government agencies, higher education institutions, and school districts, Logikcull lets customers kick off responses in seconds, find critical documents in minutes, and predict spend to the penny, all with drag-and-drop ease. That means you never miss another FOIA or PRA deadline.