Tag Archives: Enterprise AI

November 10, 2026 · 10:20 AM

Purview’s Limits Are Your Cost and Risk Problem

By Chas Meier

Last week, John Patzakis explained why Microsoft Purview eDiscovery is getting worse and why the reasons are structural: a multi-tenant architecture that must throttle heavy workloads, a 2 GB per hour indexing ceiling that has not moved since 2024, no service level commitment for search times, and a finite pool of compute that Microsoft has told investors it allocates to its highest-value opportunities, with Copilot first in line.

That post was about the cause. This one is about the consequence, and it is a consequence that reaches well beyond legal operations. When the tool at the front of your eDiscovery workflow cannot filter reliably, the organization’s answer is almost always the same: collect everything and sort it out later. Every gigabyte that leaves your environment that way is a gigabyte you pay to process, host and review, and a gigabyte that now sits somewhere you do not control, at exactly the moment attackers are becoming faster and better equipped than they have ever been.

The argument below is simple. Purview’s limits drive over-collection. Over-collection drives cost. Cost and copies drive risk. And the risk curve is about to steepen.

When Filtering Fails, Over-Collection Becomes the Default
In principle, Purview lets you search before you collect. In practice, the service providers and enterprise teams we speak with tell us that targeted collection in Purview has become something they plan around rather than rely on.

  • Searches stall or time out.
  • Indexing runs at 2 GB per hour, so a 500 GB custodian set takes more than ten days to index before a search can be trusted.
  • Partially indexed items that exceed parsing limits quietly fall outside keyword results.
  • Exports are capped at 2 GB per hour per mailbox with daily tenant-level limits, and anything still running after seven days is cancelled.

Faced with a deadline and a toolset that cannot be trusted to narrow the data defensibly, legal teams do the rational thing: they widen the net. Rather than risk a motion over an under-inclusive search, they pull entire mailboxes, entire OneDrive accounts, entire Teams channels, and push the filtering downstream to a processing platform or a service provider where the tools actually work. One provider described it to us as “collect the custodian, not the matter.”

This is not a failure of judgment by the legal team. It is the predictable response to a collection tool that cannot do its job at enterprise scale. But it means that the single most effective cost and risk control in eDiscovery, culling data before it ever leaves the enterprise, is being abandoned at the very step where it matters most.

Not a Purview User? You Probably Are One Anyway
Many organizations read our Purview posts and conclude they do not apply because the legal team never logs into the Purview portal. They use a service provider, or a collection toolkit from their review platform vendor, or a connector that “just pulls from Microsoft 365.” That conclusion is usually wrong.

Look under the hood of most Microsoft 365 collection workflows and you find Purview. Many third-party connectors and service provider toolkits are built on Microsoft’s eDiscovery search and export APIs, which means they inherit the same index, the same 2 GB per hour ceilings, the same tenant-level export caps and the same throttling. Some tools run a Purview search and export in the background and present the result in their own interface. Others collect whole mailboxes through Graph or EWS precisely because the Purview search path is too slow and unreliable to filter with, which is over-collection by design. Either way, Purview’s limitations are shaping what gets collected from your tenant, even if nobody on your team has ever opened it.

If you are not sure which category your workflow falls into, that is worth finding out. Ask your provider or your platform vendor two questions:

  1. Does your Microsoft 365 collection depend on Purview’s index or Microsoft’s eDiscovery APIs?
  2. What percentage of the data you collect from our tenant is ultimately produced?

If the first answer is yes and the second answer is in the low single digits, you are an indirect Purview user, and you are paying for it.

The Volume Does Not Disappear. It Moves Downstream.
Data that is not filtered at collection does not go away; it flows into the next stage of the workflow. Whole-custodian collections land on a service provider’s processing infrastructure or in a hosted review platform, where the filtering that should have happened inside the enterprise is finally performed, at a per-gigabyte price. The industry has become very good at absorbing that volume, which is part of why the problem is so easy to ignore. Processing gets faster, hosting gets cheaper per unit, and analytics get better at culling. But none of that changes the fact that the data has already left.

The numbers compound quickly:
• A matter with 20 custodians and an average of 30 GB per custodian across email, OneDrive and Teams produces 600 GB of exfiltrated data before a single document has been reviewed.
• A targeted in-place search would have narrowed that to 5%; the other 570 GB is pure overhead: ingested, processed, deduplicated, and hosted for the life of the matter, and then for years afterward.
• Multiply that across every matter, investigation and regulatory request in a year and the over-collection tax on a mid-size enterprise runs into the hundreds of thousands of dollars, and for a large one, well into the millions.

Service providers see the other side of this. Their platforms are filling with data that nobody needed, and their clients are increasingly asking why the processing and hosting line items keep growing when case counts are flat. The honest answer: the collection tool upstream stopped doing its job.

Every Exfiltrated Gigabyte Is Both a Cost and a Risk
The cost side is visible on the invoice. Processing, hosting, review, productions and long-tail storage all scale with volume, and over-collection inflates every one of them. What is harder to see is that the same volume is also the organization’s single largest self-inflicted security exposure.

Consider what an eDiscovery collection actually is: a curated copy of your most sensitive communications, deliberately assembled, stripped of the access controls that protected it in the source system, and shipped to a third party. Executive email. Board materials. Privileged legal advice. Customer data, employee data, trade secrets, M&A deliberations. A whole-custodian collection does not just include the documents relevant to the matter; it includes everything that custodian ever touched. And it is now sitting on a service provider’s processing server, in a hosted review platform, in a law firm’s document management system, on an export drive, and in whatever backups each of those parties keeps.

Each copy is a new attack surface governed by someone else’s security program, someone else’s patch cycle and someone else’s employees. Law firms and eDiscovery vendors are high-value targets precisely because they aggregate the crown jewels of many clients in one place, and the breach record of the last several years bears that out. When one of those copies is compromised, the breach notification obligations, regulatory exposure and reputational damage belong to you, not to the vendor, and they attach to all of the data that was collected, not just the small fraction that was ever relevant.

Over-collection, in other words, turns a legal cost problem into an enterprise security problem. The 95% of the collection that was never responsive was never worth that risk.

The Next 12 to 24 Months: AI on the Other Side of the Wall
If the risk calculus above were static, over-collection might be a tolerable inefficiency. It is not static. The same generative AI wave that is consuming Microsoft’s compute capacity is also arming the people who want your data.

AI has collapsed the cost and skill required to run a sophisticated attack. Phishing campaigns are now fluent, personalized and generated at scale. Vulnerability discovery and exploit development that once took skilled teams weeks can be accelerated by models that reason over code. Reconnaissance against a target’s vendors, employees and infrastructure is automated. Agentic tooling allows a single operator to run many intrusion attempts in parallel and adapt to defenses in real time. Security researchers and government agencies have been warning for the past year that AI-enabled intrusion is moving from proof of concept to routine practice, and the trend lines for breach frequency, ransomware payouts and time-to-exploit all point the same way.

Over the next 12 to 24 months, we expect frequent, aggressive and automated attacks to become the baseline rather than the exception, and we expect the organizations that aggregate other companies’ sensitive data, including eDiscovery service providers, review platforms and law firms, to remain among the most attractive targets. Vendors will keep investing in defenses. But a defender has to be right every time, and AI has made the attacker’s job dramatically cheaper.

The only exposure you fully control is the amount of data you send out in the first place. Every copy you do not create is a copy that cannot be breached.

Now Is the Time to Be Proactive
The organizations that will be in the strongest position two years from now are the ones that treat eDiscovery collection as a data governance and security decision, not just a legal workflow step. That means three things.

  • Limit exfiltration. Search, cull and validate inside your own environment, and collect only what is potentially responsive. The goal is to move the filtering step back to where it belongs, before the data leaves, so that what reaches a provider or a review platform is the matter, not the custodian.
  • Limit unnecessary cost. Every gigabyte you keep inside the enterprise is a gigabyte you do not pay to process, host, review and store. Targeted in-place collection is the single largest lever available to reduce eDiscovery spend, and it is a lever that most Microsoft 365 organizations are not currently pulling because their tooling does not let them.
  • Remain in control of your data. Run eDiscovery and governance on infrastructure you control, with search methodology you can test and document, indexes you own, and no dependence on a shared tenant’s throttling policies or a cloud provider’s capacity priorities. Control means being able to answer a court, a regulator or a board with confidence about what you searched, what you collected and where it went.

Waiting for Purview to improve is not a strategy. Last week’s post explained why its limitations are architectural and why Microsoft’s own capacity constraints make relief unlikely. Meanwhile the cost of over-collection accrues on every matter, and the risk of each unnecessary copy grows with every advance in offensive AI. The time to change the workflow is before the next large matter, not after the next breach.

How X1 Enterprise Is Different
X1 Enterprise was built for exactly this problem: search and collect in place, so that only what matters ever leaves. The differences from a Purview-dependent workflow are architectural, not cosmetic.

In-place indexing you own. X1’s patented distributed micro-indexing technology indexes Microsoft 365 data where it lives, across Exchange, OneDrive, SharePoint and Teams, alongside endpoints, file shares and other cloud sources. X1 does not use Purview’s index or Microsoft’s eDiscovery search APIs, so there is no 2 GB per hour ceiling, no tenant-level export cap, no seven-day cancellation and no throttling inherited from every other tenant on the platform.

Compute you control. X1 runs on infrastructure the customer controls, on premises or in the customer’s own cloud. Your eDiscovery and governance jobs are never queued behind Copilot or anyone else’s workload, and performance is predictable because it is yours.

Search that meets the courts’ standard. Full Boolean, proximity, wildcard and stemming queries execute consistently across email, files and Teams chat, with the ability to iteratively test, refine, validate and document search methodology before anything is collected. That is the “advanced and thoughtful” search the Kim v. Cushman & Wakefield court said Teams data requires, and the validation Special Master Favro found missing in native Microsoft 365 tools.

Targeted collection, not whole-custodian export. Because the search runs in place and can be trusted, only potentially responsive data is collected. Filtering moves back to the front of the workflow, where it cuts downstream volume, cost and exposure at the source. Collected data can be uploaded directly into Relativity for review.

Defensibility by design. Preservation, search and collection are logged and reportable, so you can show a court or a regulator exactly what was searched, when, with what criteria, and what was collected.

AI where the data lives. The same in-place architecture powers X1 AI In-Place, allowing organizations to apply AI classification directly to data in its source location for early case assessment, privilege and sensitivity identification, and information governance, again without exporting the data to do it.

Talk With X1
If your Microsoft 365 collections are coming back as whole custodians, if your processing and hosting invoices keep growing while your case count does not, or if you have never asked how much of the data you send out is actually responsive, we would like to talk.

Contact X1 to schedule a live demonstration of X1 Enterprise against a Microsoft 365 environment. Better still, bring us a recent matter. We will run a targeted in-place search on your own data and show you how much volume, cost and risk you could have kept inside the enterprise.

The next large matter is coming, and so is the next wave of attacks. Collect less, spend less and keep control of your data.

Leave a comment

Filed under AI In-Place, Best Practices, Cloud Data, Corporations, Cybersecurity, Data Governance, ECA, eDiscovery, eDiscovery & Compliance, Enterprise AI, Enterprise eDiscovery, ESI, GDPR, Information Governance, Information Management, m365, MS Teams, OneDrive

Tagged as , , , , , , , , , , ,

November 3, 2026 · 2:04 PM

Microsoft Purview eDiscovery Problems Are Structural—and Growing

By John Patzakis

For organizations that rely on Microsoft Purview for eDiscovery, compliance and investigations, the gap between what the tool delivers and what the job demands is widening. Stalled searches, timed-out exports and a 2 GB per hour indexing cap slow investigations, drive up costs and leave legal teams with results they can’t fully defend.

Over the past several months, we have been speaking with a number of eDiscovery service providers, channel partners, and enterprise customers about their experiences with Microsoft Purview eDiscovery. The feedback has been remarkably consistent. The same challenges we began writing about several years ago are still there, and by most accounts they have gotten worse. One service provider that handles a high volume of Microsoft 365 matters told us that Purview performance has deteriorated noticeably in recent months, describing searches and exports that stall or time out and processing delays that have put counsel in a difficult position with opposing parties and the court.

When X1 first raised these issues, the common reaction in the market was that Purview was a maturing product that Microsoft would eventually fix. With Microsoft’s engineering resources, many assumed that eDiscovery inside Microsoft 365 would steadily improve. That was a reasonable expectation at the time. It has not happened. In our view, the reason is that Purview’s limitations stem from the architecture of Microsoft 365 itself, which makes it very difficult to engineer away. And there is now an additional factor worth considering: the intense competition for computing resources driven by Microsoft’s AI strategy.

The Architecture Has Not Changed
As we explained in our post on Microsoft 365 eDiscovery throttling, Microsoft 365 is a massive multi-tenant SaaS environment. Every customer shares pooled infrastructure, and eDiscovery is exactly the kind of heavy, bursty workload that a multi-tenant system must restrain to protect everyone else on the platform. Throttling, timeouts, and hard caps are how Microsoft manages that “noisy neighbor” problem, and they are built into the design of the system. We made the same point more broadly last December in our analysis of why most SaaS architectures fall short for enterprise-grade AI: shared capacity introduces contention and performance variability that no configuration setting can resolve.

Microsoft’s own documentation bears this out. The current Microsoft Learn page on eDiscovery limits, last updated in June 2026, shows:

  • 2 GB per hour for advanced indexing in Purview eDiscovery Premium. That is the same cap we cited in 2024. At that rate, indexing a single terabyte requires roughly three weeks of continuous processing.
  • 2 GB per hour per mailbox limit for exports, with daily exports capped at the tenant level.
  • Automatic cancellation of any process or export still running after seven days.
  • No service level agreement for search terms. Microsoft also states plainly that it “doesn’t provide a service level agreement for search times.”

Microsoft even maintains a service advisory to notify administrators when their tenant has been “throttled due to number of Search and Export jobs exceeding the limit set by Microsoft.”

For organizations with significant information governance requirements, these constraints are even more limiting. As we discussed in our post on information governance challenges in Microsoft 365, a defensible governance program depends on automated enforcement across the full data estate, and a 2 GB per hour ceiling makes that impractical at enterprise scale.

Special Master Favro’s Findings Still Hold
In July 2023, Special Master Philip Favro issued a report in Deal Genius, LLC v. O2COOL, LLC, No. 21 C 2046 (N.D. Ill.), raising serious concerns about whether reliance on Microsoft 365’s native search tools satisfies the reasonable inquiry requirement of Federal Rule of Civil Procedure 26(g). As we reported at the time, the Special Master found that M365 has “technological limitations that may not allow a responding party to generate reliable search results,” that it “generally does not fully index the data” in an organization’s environment, and that it does not allow users to validate their search and production results.

More than three years later, nothing in Microsoft’s documentation indicates those problems have been resolved. The indexing ceiling is unchanged, items that exceed parsing limits are still marked as partially indexed, and there is still no service level commitment. Meanwhile, the courts have raised the bar. In Kim v. Cushman & Wakefield U.S., Inc., 2026 WL 1353455 (C.D. Cal. Apr. 24, 2026), the court held that “[k]eyword searches alone, without more advanced and thoughtful search techniques, will be inadequate for Teams data.” That is a difficult standard to meet with a native toolset built around basic keyword and condition searching.

Recent Developments Reinforce the Concerns
Several developments over the past year add to the picture.

A systemic Purview hold failure. In Oakley v. MSG Networks, Inc., 792 F. Supp. 3d 394 (S.D.N.Y. 2025), Madison Square Garden placed a legal hold through Purview that was intended to ensure emails were “retained no matter what the user does.” Emails from eleven custodians were lost anyway. MSG’s forensic expert concluded that a technical glitch in its Microsoft environment had occurred “beyond a shadow of a doubt,” and the court noted that “the software malfunction affected seventy-nine matters other than the Oakley case.” MSG avoided sanctions because the court found its use of Purview to be a reasonable preservation step. But the emails were gone, and MSG had to fund a forensic investigation and litigate the issue to establish it was not at fault. Reasonableness under Rule 37(e) turns on what a party knew or should have known, and as the record of Purview failures grows, I would not count on that defense being available indefinitely.

Sanctions for delay even when reliance was reasonable. In FTC v. Match Group, Inc., 2025 WL 46024 (N.D. Tex. Jan. 7, 2025), an archiving system used with Office 365 failed to capture certain custodians and time periods. Match produced nearly 500 additional documents after the discovery deadline, most of them after the FTC had moved for summary judgment. The court found Match’s reliance on the archive reasonable, yet still imposed sanctions under Rule 16(f) for the late production, allowing the FTC additional depositions at Match’s expense. The lesson for Purview users is clear: courts can and will sanction delays caused by collection tools, regardless of how reasonable the choice of tool may have been.

Reduced functionality. In 2025 Microsoft moved all customers to its new Purview eDiscovery experience, retiring classic Content Search and eDiscovery (Standard) in May and classic eDiscovery (Premium) in August. In the process, Microsoft retired its legacy legal hold communications tools for custodian notices and acknowledgments. And as Casepoint has noted, the new interface no longer shows that a custodian was ever on hold once that custodian is released, making it harder to document a preservation timeline. The visibility problem is significant enough that a new third-party reporting product launched this spring because, as LawNext reported, legal teams have “no direct visibility into what is happening inside Microsoft Purview eDiscovery.”

More data, more complexity, new fees. Copilot is generating entirely new categories of data that Purview must preserve, search, and produce. Microsoft recently had to add an option to convert Loop and Copilot Pages files to HTML because those formats cannot be opened by standard review tools. Microsoft now also bills pay-as-you-go storage for certain AI interaction data in eDiscovery cases and requires E3 customers to activate pay-as-you-go billing to use its eDiscovery export APIs.

Service disruptions. On January 22, 2026, an infrastructure failure in North America blocked administrator access to the Purview portal, along with Exchange, Teams, and SharePoint search, for several hours.

The AI Factor
This brings us to a question several of our partners have raised with us. Microsoft has been unusually candid with investors that it does not have enough computing capacity to meet demand, and that it is making deliberate choices about where that capacity goes.

On Microsoft’s January 28, 2026 earnings call, CFO Amy Hood described the order of priority directly: “the first thing we’re doing is solving for the increased usage in sales and the accelerating pace of M365 Copilot. Then we make sure we’re investing in the long-term nature of R&D and product innovation,” with “the remainder going towards serving the Azure capacity that continues to grow in terms of demand.” She added that if the GPUs that came online in the prior two quarters had been allocated entirely to Azure, Azure’s growth metric “would have been over 40” percent.

On the October 28, 2026 call, Ms. Hood reported that “[c]ustomer demand continues to exceed available supply.” CEO Satya Nadella said Microsoft will “dynamically allocate capacity to the highest-value opportunities across compute, data, Foundry, and Copilot,” explaining that “we have one pool, and we want to get the pool to be as efficient and fungible” as possible. Microsoft is now projecting capital spending on the order of $170 billion to try to catch up.

Microsoft has not said where Purview eDiscovery falls in that order of priority, and we have no inside view into how Microsoft allocates resources within its data centers. But consider what Microsoft has told us. It operates “one pool” of capacity. That pool is constrained. Capacity is allocated to the “highest-value opportunities,” and Copilot is first in line. eDiscovery is a compliance function that generates little incremental revenue, carries no service level commitment for search times, and has seen its documented throughput limits stay frozen while its feature set has been trimmed. At the same time, Copilot is adding new volumes and types of data that Purview is expected to handle.

When capacity is scarce and allocated by value, it is fair to ask how high a priority eDiscovery search and export jobs receive. The service providers and customers telling us that Purview has gotten worse may be seeing the practical result of that ordering. Organizations planning their discovery and governance obligations around Purview should at least account for that possibility.

A Different Architecture
X1 takes a fundamentally different approach. The X1 Enterprise Platform uses our patented distributed micro-indexing technology to index Microsoft 365 data in place, across Exchange, OneDrive, SharePoint, and Teams, along with endpoints, file shares, and other cloud sources.

For legal and compliance teams, that means:

  • Predictable timelines. X1 does not depend on Purview’s search index or Microsoft’s eDiscovery search APIs, so it is not subject to Purview’s indexing ceiling, export caps or the throttling that comes with sharing those resources with every other Microsoft tenant.
  • No competing with Copilot for capacity. The compute runs on infrastructure our customers control, which means eDiscovery and governance jobs are not competing with Copilot for priority.
  • The search methodology courts now expect. Full Boolean, proximity, wildcard, and stemming queries that execute consistently across email and Teams chat, with the ability to iteratively test, validate and document search methodology before anything is collected.
  • Lower cost and less risk. Only potentially responsive data is collected, and it can be uploaded directly into Relativity for review.
  • AI where your data lives. The same in-place architecture powers X1 AI In-Place, allowing organizations to apply AI classification directly where their data lives without the cost, delay, and exposure of moving it.

X1 works alongside your Microsoft 365 investment. Your data stays in M365, and X1 gives you the defensible, scalable discovery layer Purview wasn’t built to provide.

If your organization or your clients are running into these issues with Purview, we would like to hear from you. Contact X1 to schedule a live demonstration of X1 Enterprise in a Microsoft 365 environment, or to discuss a proof of concept on your own data.

Leave a comment

Filed under AI In-Place, Best Practices, Cloud Data, Corporations, Data Governance, eDiscovery, eDiscovery & Compliance, Enterprise AI, Enterprise eDiscovery, ESI, Information Access, Information Governance, Information Management, m365, MS Teams

Tagged as , , , , , , , , ,

July 7, 2026 · 10:13 AM

Kim v. Cushman & Wakefield: A Federal Court Confirms That Email Search Terms Don’t Work for Microsoft Teams

By John Patzakis

Blog header about the Kim v. Cushman & Wakefield case, discussing a federal court ruling on email search terms and their ineffectiveness for Microsoft Teams. Includes graphics of a gavel, documents, and message bubbles.

A recent decision out of the Central District of California should be required reading for any legal team that includes Microsoft Teams as data source in their discovery plan. In Kim v. Cushman & Wakefield U.S., Inc., 2026 WL 1353455 (C.D. Cal. Apr. 24, 2026), the court held that search terms that may be appropriate for email may not be sufficient for shorter, less formal communications on a collaboration platform like Teams.

The plaintiff, Ms. Kim, alleged pregnancy discrimination after being terminated upon her return from maternity leave. The defendant asserted the termination was part of a reduction in force; Ms. Kim alleged that rationale was pretextual. The discovery dispute arose when it emerged that the defendant had not searched Microsoft Teams at all—even though, as one of the defendant’s own witnesses testified, Teams was one of the primary communication methods used at the company. To its credit, upon discovering the gap, defense counsel immediately ran the existing email search terms against Teams and produced 47 pages of messages, two of which proved relevant to the pretext analysis.

That partial cure satisfied no one. The plaintiff demanded a nearly indiscriminate search of “all reasonably likely repositories,” while the defendant maintained it had already run the terms against Teams and “there’s nothing left.” The court’s response: “Neither position is quite right.”

The Teams Ruling: Keyword Searches Alone Are Not Enough
The heart of the opinion is the court’s recognition that rerunning email-oriented search terms against Teams data is structurally flawed. The defendant’s terms all required “Connie Kim” as an anchor—e.g., “Connie Kim” NEAR “terminat!”. As the court explained:

“It is arguable whether that may work well enough even for emails, but it cannot work for MS Teams chats about transition planning among managers who might say ‘the Smartsheet’ or ‘Brooke’s workload’ without mentioning Plaintiff by name. Keyword searches alone, without more advanced and thoughtful search techniques, will be inadequate for Teams data—a medium where conversations are shorter, more informal, and less likely to include full names than email.”

The court also underscored the certification obligation that attaches once a party elects to search: “An objecting party that elects to search and produce—rather than move for a protective order—undertakes an obligation to search reasonably. See Fed. R. Civ. P. 26(g)(1)(B).” And the Rule 26(b)(1) proportionality analysis weighed in the plaintiff’s favor as to Teams, since the messages already produced confirmed that relevant communications existed in that repository.

Notably, the court declined to dictate methodology, holding that how the defendant fulfills its supplemental search obligation— “whether through custodian-based collection, refined keyword queries, or technology-assisted review—is Defendant’s choice, so long as the search is reasonable and the production is complete.” The court also traced the root cause to a pro forma Rule 26(f) conference: had the parties conducted a substantive ESI conference identifying repositories, custodians, and communication platforms at the outset, the Teams gap would have been caught months earlier.

In his excellent writeup of this case, Michael Berman of E-Discovery LLC consulted eDiscovery expert Tom O’Connor of the Gulf Coast Legal Technology Center, who raised a critical practical question: what tool was actually used for the search? O’Connor explained that while keyword searches inside Teams work, Teams supports only basic keyword matching and a few command-style filters. Per O’Connor, the native “Teams search indexes chat differently than email,” in that it:

• “Prioritizes exact word matches;
• Does not index message metadata as richly as Outlook;
• Often misses partial-word matches; and
• Returns fewer results when the term is too specific.”

In other words, even well-crafted Boolean terms can silently underperform when run against Microsoft’s native Teams index.

Why Kim Illustrates the Case for X1 Enterprise
The Kim decision validates what we have long argued at X1: when addressing MS 365 data for eDiscovery, the search methodology applied to it must be purpose-built. As we detailed when we launched our advanced MS Teams support, X1 Enterprise enables a targeted, iterative search and collection of Teams data in-place, with the ability to target individual custodians and specific messaging threads—displacing any need to mass download channels—plus unified search across Teams, OneDrive, SharePoint, Mail, laptops, and file shares, and one-click upload into Relativity for review.

Critically, X1 does not rely on the limited native Microsoft Teams index that O’Connor describes. X1’s patented technology builds its own full-featured index of Teams data, enabling precisely the “more advanced and thoughtful search techniques” the Kim court demanded. That includes detailed Boolean queries with nested operators, proximity, and wildcard/stemming support that execute consistently across both email and chat data—so counsel is not forced to choose between Outlook precision and Teams looseness. X1 also includes the ability to search on emojis, which is critical for Teams and other chat platforms, where a reaction emoji may be the entire substance of a manager’s response to a message about a “transition plan.”

X1’s patented in-place search and classification capabilities extend this further. Through the X1 API, organizations can programmatically execute searches and apply AI-driven classification models directly where the data lives—before anything is collected. Applied to the Kim fact pattern, that means counsel can iteratively test and refine looser, Teams-appropriate search terms against live data, measure the results, and classify what comes back—building a defensible, documented search methodology of exactly the kind the court invited when it referenced “refined keyword queries” and “technology-assisted review.” And because it all happens in place, the proportionality benefits are built in as only potentially responsive data is collected.

The lesson of Kim is straightforward. Courts now expect parties to identify collaboration platforms like Teams at the Rule 26(f) stage, to search them with techniques suited to informal chat data, and to do so reasonably and completely. Meeting that expectation requires solutions designed for the job.

Learn more about the X1 Enterprise Platform, or contact our sales team to schedule a live demo.

Leave a comment

Filed under Best Practices, compliance, Corporations, Data Audit, Data Governance, ECA, eDiscovery & Compliance, Enterprise eDiscovery, Enterprise Search, ESI, Information Access, Information Governance, Information Management, law firm, m365, MS Teams

Tagged as , , , , , , , , , ,

June 16, 2026 · 10:11 AM

Why X1’s AI In-Place Architecture Is a Genuine Departure from Legal AI’s Status Quo

By John Patzakis

X1 AI In-Place Architecture — AI hub connecting to distributed enterprise data sources including Microsoft 365, email, cloud, and endpoints

The legal technology market has a buzzword problem. Terms like “AI-powered,” “intelligent review,” and “automated analysis” have been applied so broadly—and so inconsistently—that they have largely lost their ability to signal anything meaningful about how a product actually works. Against that backdrop, X1’s announcement last week of AI In-Place for X1 Enterprise represents a genuinely different approach to applying AI within enterprise legal and compliance workflows. The reason for this basis is X1’s unique architecture.

To understand why, it helps to start with the dominant model that most legal AI tools share. The overwhelming majority of AI-enabled eDiscovery and governance platforms are built on a collect-first assumption: data must be moved out of its native environment—copied, ingested, centralized in a vendor-controlled repository—before any AI model can be applied to it. This is not an incidental design choice; it reflects the fundamental architecture of how most of these platforms were built, long before AI became part of the product story. The result is what practitioners have come to call the “prompt wrapper” problem: an AI interface sits in front of a conventional data pipeline, and the underlying mechanics—the cost, the risk, the latency—remain largely unchanged. A large language model with a “middleware” workflow does not solve the structural problem of what happens to sensitive data before the AI touches it.

X1’s AI In-Place architecture inverts that assumption. Rather than requiring data to travel to an AI system, X1’s patented distributed micro-indexing technology deploys AI models directly into lightweight micro-indexes at the data source itself—across Microsoft 365 environments, file shares, cloud repositories, and endpoints. The AI executes where the data lives, and the data does not move. The implications run across multiple dimensions: data never leaves the enterprise perimeter, security policies and endpoint controls remain intact throughout the process, and the computational overhead and massive AI token costs associated with large-scale data ingestion is avoided entirely. For matters involving a terabyte of data or more—where centralized collection is not merely expensive but operationally infeasible—this architectural distinction is not incremental. It changes what is actually possible.

The workflow mechanics reinforce the point. AI models are deployed into X1’s distributed micro-indexes behind the firewall, execute against enterprise data in place, and surface AI-enriched insights—tags, classifications, risk scores—into a central console without the underlying data ever being collected or copied. That means targeted collection decisions, early case assessment, and information governance actions can be driven by AI-informed analysis conducted across the full enterprise data landscape, not just against a subset of data that has already been moved. The distinction matters because the scope of analysis in the collect-first model is constrained by collection costs; in the in-place model, analysis scope is no longer tethered to collection volume. Investigations and governance programs can, in principle, cast a much wider net analytically while actually reducing the volume of data that requires review.

Mandi Ross, CEO of Insight Optix, offered a perspective that cuts to the core of what makes this architecture commercially significant: “Enabling AI directly where the clients’ data resides fundamentally changes the economics, speed, and risk profile of enterprise data discovery, investigations and compliance workflows. With X1 Enterprise AI In-Place, we can deploy AI models, pre-trained or customized for specific matters, data queries, or compliance requirements—securely within client environments, dramatically accelerating time to insight without sensitive information being collected, duplicated, or centralized outside their control.”

Ross identifies three dimensions the in-place approach changes: economics, speed, and risk. On economics, a significant lever is the reduction in review population size—AI-informed pre-collection filtering means fewer documents proceed to human review. Additionally, costs associated with collection and processing, including expensive AI token utilization, are all but eliminated. On speed, running analysis in situ, without waiting for collection and ingestion cycles, compresses time to first insight—critical in time-sensitive investigations and regulatory responses. On risk, data that does not move cannot be breached in transit, does not reside in vendor infrastructure outside the client’s control, and does not generate the compliance exposure of large-scale cross-boundary transfers. Her comment reflects what experienced practitioners understand but marketing language tends to obscure: the most consequential question about any legal AI tool is not what the AI does, but what happens to the data before and during its operation.

The enterprise deployment model reflects design discipline that distinguishes AI In-Place from retrofitted solutions. Organizations retain centralized governance over AI usage while processing remains local under existing security policies and endpoint controls. AI capabilities are fully optional and configurable at the data source level—important for organizations operating across multiple jurisdictions with differing regulatory requirements—and customer data is never used to train, fine-tune, or enrich underlying AI models, addressing a standard due diligence concern in enterprise AI procurement.

The practical use case implications are significant across several domains. In legal and eDiscovery contexts, in-place TAR and pre-collection analytics allow AI-informed decisions about what to collect before collection begins, directly reducing review volumes and costs. In information governance, AI-driven classification and policy enforcement can operate continuously across the full enterprise data estate rather than against periodic snapshots, enabling more responsive and defensible governance programs. In security and investigations, real-time insider risk detection at petabyte scale—across endpoint and cloud environments simultaneously—becomes feasible where centralized architectures make it impractical. In each case, analytical scope is no longer constrained by collection logistics.

Most legal AI products apply AI to data after it has already moved through the conventional collection pipeline. AI In-Place asks a more fundamental question: whether the pipeline itself should be reconceived. We will demonstrate it live on Wednesday, June 24—for those evaluating enterprise AI in legal, compliance, or governance contexts, it is worth seeing what a genuinely different architecture looks like in practice.

Register for the June 24 AI In-Place™ Product Tour →

Leave a comment

Filed under Best Practices, Cloud Data, Corporations, Cybersecurity, Data Audit, Data Governance, ECA, eDiscovery & Compliance, Enterprise AI, Enterprise eDiscovery, Enterprise Search, ESI, GDPR, Information Access, Information Governance, Information Management, m365, MS Teams, OneDrive, SharePoint

Tagged as , , , , , , , , , , , , , ,

April 8, 2026 · 9:49 AM

Bringing AI to the Data: How X1 Search v11 Redefines Secure Enterprise Search

By John Patzakis

At X1, we believe the future of enterprise AI depends on a simple but often overlooked principle: data should not have to move in order to become intelligent. With the launch of X1 Search v11, we are introducing a fundamentally different approach—one that embeds AI directly into our index-in-place architecture. Rather than forcing organizations to centralize and copy their data into external platforms, we enable AI to operate exactly where that data already lives. You can read the full press release here: https://www.x1.com/x1-introduces-ai-powered-x1-search-delivering-secure-ai-in-place-for-individual-and-enterprise-users/

This release represents an important milestone for us and for our customers. As Chas Meier noted, “X1 Search v11 marks an important milestone in how organizations can safely apply AI…without compromising the security controls enterprise environments demand.” That statement reflects our core design philosophy: AI must adapt to enterprise security, compliance, and governance requirements—not the other way around.

With X1 Search v11, we are delivering AI capabilities directly within our micro-index. That means organizations can apply advanced intelligence—classification, categorization, and contextual analysis—across emails, files, and collaboration data without ever relocating that information. Everything happens in place, within existing security boundaries, whether on endpoints or across enterprise systems.

For large enterprises, this architecture unlocks an even more powerful capability: the ability to deploy their own trained and curated large language models directly into the X1 index. Instead of relying solely on generic, hosted AI services, organizations can operationalize models tailored to their data that reflect their internal policies, regulatory requirements, and business workflows. These models run directly against their data, in place, delivering highly relevant and controlled outcomes.

This approach stands in sharp contrast to traditional hosted AI platforms. In those models, organizations must copy and transfer massive amounts of sensitive data into third-party hosted AI platforms before any meaningful analysis can occur. That process introduces serious risks. Moving data to outside providers complicates compliance, potentially compromises IP, and creates new attack surfaces that most enterprises simply cannot accept.

Beyond security concerns, the traditional model also breaks down operationally at scale. Enterprises are not dealing with small data sets; they are managing dozens of terabytes of distributed, unstructured data. Attempting to duplicate and transfer that volume is not just costly; it is infeasible. The result is delays, fragmentation, and incomplete analysis—undermining the very promise of AI.

We have taken a different path. By bringing AI to the data through our distributed micro-indexing technology, we eliminate the need for data movement entirely. Models can be deployed directly to where data resides, enabling real-time analysis while preserving security, reducing infrastructure overhead, and scaling seamlessly across the enterprise.

We see X1 Search v11 as more than a product release—it is a shift in how enterprise AI is deployed. Organizations no longer have to choose between innovation and control. With AI in place, they can achieve both.

To see this in action, we invite you to join our upcoming live product tour on Thursday, April 23, providing a guided walkthrough of the new AI-enriched capabilities and flexible model deployment features.

Leave a comment

Filed under Best Practices, Business Productivity Search, Desktop Search, Enterprise AI, Enterprise eDiscovery, Enterprise Search, ESI, Google Workspace, Information Access, Information Management, m365, MS Teams, X1 Search 11

Tagged as , , , , , , , , , , , , , ,