Panzura Express and Panzura Nexus Give Small and Mid-Sized Firms Something Copilot Can’t See on Its Own: AI File Intelligence

Mid-Market Firms Are Paying for Microsoft 365 Copilot and Getting Thin Answers, because their Competitive Knowledge Sits in Files Copilot Can’t See. Panzura Express Bundles CloudFS and Nexus Into One License That Gives a Lean Team Enterprise-Class AI File Intelligence

Key Takeaways:

• Mid-market firms are paying for Microsoft 365 Copilot and getting partial reach. Copilot reads Outlook, Teams, SharePoint, and OneDrive, but the files that represent what a project-based firm actually knows how to do sit on file systems Copilot was never given a way to reach. This isn't a permissions setting anyone forgot to flip. That data isn't in Microsoft 365 at all.
• The blind spot compounds fastest at the firms least able to absorb it. Per-seat licenses cost the same whether Copilot can reach the valuable data or not, and thin answers drive the adoption collapse. Meanwhile the senior engineer still spends hours hunting for a precedent, the proposal team rewrites what a past bid said better, and a single retirement takes judgment out the door.
• Panzura Nexus solves the problem without moving a file, and Panzura Express puts it within reach of a three-person IT team. It makes CloudFS file content answerable inside Copilot with existing file-system permissions enforced in real time, answers citing the files they came from, no migration, no parallel copy, no permissions rebuild. It comes included in Panzura Express rather than gated to a higher tier.

This is Part 3 of a 3-part series on Panzura Express. Read Part 1 and Part 2.

Here’s a scene playing out in a lot of mid-market project-based and AEC firms right now. Microsoft 365 Copilot licenses are bought, the rollout is complete, and someone decides to test it on something that matters. They ask about a project from three years ago. The one with the tricky foundation detail, or the client with the unusual change-order history. They want the specifics from the project files.

Copilot gives them a shrug. A polite, well-worded shrug, but a shrug. It can summarize an email thread and draft a meeting agenda, but it can’t find or see the accumulated record of years of real work.

This is the disappointment settling over a lot of Copilot rollouts, and it hits hardest at the firms that can least afford a tool that doesn’t earn its keep. That often means a 200-person (or less) engineering or architecture firm doesn’t have an innovation budget to write off. When the firm invests in AI, it needs a tangible return on investment, but right now Copilot is tapping into a fraction of what the firm knows, and often the least valuable fraction at that.

Competitive knowledge isn’t in Microsoft 365

Here’s the mismatch at the root of it. Copilot reads what is inside Microsoft 365, which means your Outlook mail, Teams conversations, and the documents in SharePoint and OneDrive. For the born-in-Microsoft-365 part of your work, Copilot is genuinely useful.

But that’s not where a project-based firm keeps the most valuable information. The drawings, specifications, CAD and CAM files, proposals, and decades of past jobs are the material that represents what your firm knows how to do. Those files are on network shares, a NAS, or in the file storage that’s been accumulating project history since before anyone bought a Copilot license. Analysts have long estimated that the vast majority of enterprise data is unstructured, with IDC’s widely cited projection putting it at around 80%. For an engineering or architecture firm, where the work includes drawings and models, the proportion of unstructured data is likely even higher.

And Copilot can’t see any of it. Not due to a permissions setting you forgot to flip, but because that data isn’t in Microsoft 365 at all. It’s in a different place, in a form Copilot was never given a way to reach. You can ask Copilot anything you like about the work in those files, but it simply cannot see them.

Industry analysts who track enterprise data and AI have begun examining what this means for organizations trying to get real value out of Copilot. Among them is Henry Baltazar of 451 Research by S&P Global, who has published coverage of Panzura Nexus in his recent report, Panzura targets Copilot gap with file-to-AI retrieval layer Nexus¹. 451 Research by S&P Global subscribers can access the full report here,

Panzura Nexus is a permission-preserving retrieval layer that surfaces CloudFS file content into Copilot, with no migration, no data lakes, and no copies to secure. It answers the question organizations have been asking with growing frustration. They want to know why Microsoft 365 Copilot doesn’t know what their files know.

That gap is crucial for a small or mid-sized firm because knowledge is how those organizations compete. You may not have enterprise-scale headcount, but the reason a client hires you is the judgment sitting in your past and present work. When that knowledge is trapped in folders, you’re competing without your biggest advantage. When it’s answerable in seconds, a 30-person team can move like a much larger one.

The cost of the AI blind spot

This has a price, too, and for a lean firm the price compounds fast.

The first cost is the license itself. Microsoft 365 Copilot is a per-seat expense that costs you whether it can reach the data that matters or not. If it’s answering only from email and chat, you’re paying full price for partial reach. That is the AI equivalent of buying a research library and getting only the front desk. A large enterprise can absorb that. A firm running a tight software budget notices every seat that isn’t paying its way.

The second cost is the adoption death spiral. When people test a new tool on a real question and get a thin answer, they stop trusting it, and then they stop using it. The usage data bears this out. Microsoft reported roughly 15 million paid Copilot seats as of its early-2026 earnings, which equates to about 3.3% of its commercial Microsoft 365 base.

Independent surveys by Recon Analytics put active use among licensed users at a median of around 36%. Companies are buying licenses. Getting people to keep using them is the part that keeps failing. The tool failed because it was providing answers with one hand tied, and the users had no way to know that. They just knew it couldn’t help with what they cared about – their unstructured AEC application data, not just their Microsoft data.

There’s a broader version of the same gap. McKinsey’s 2025 State of AI research found that while 88% of organizations report using AI in at least one business function, only 39% attribute any measurable impact to it. Nearly everyone has the tools running. Far fewer can point to what they’ve earned from them. When AI is fed only a fraction of what a firm knows, near-universal adoption and thin business results are exactly the two numbers you’d expect to see.

The third cost is the one that doesn’t show up on an invoice, and it’s the one a small or mid-market firm feels most. Every day the blind spot persists, the knowledge that makes your firm competitive stays locked up:

• The senior engineer spends two hours combing folders for a precedent instead of billing that time. On a small team, there’s no bench to absorb the hours.
• The proposal team rewrites from scratch what a past bid already said better, because nobody can find the past bid.
• Institutional memory walks out the door when a veteran retires. In a firm of 200, one retirement can take a whole discipline’s worth of hard-won judgment with it.

Table 1. Microsoft 365 Copilot alone vs. Copilot with Panzura Nexus

The tribal knowledge problem, solved

Every firm runs on knowledge that was never written down in a way that was meant to be shared. In a smaller firm, this tribal knowledge is concentrated in a handful of people, and it leaves when they leave. That includes when they go for a long weekend, a new job, or retirement.

The frustrating part is that most of it is recorded. It’s in the markups, RFI responses, closeout documents, email that got saved to the project folder. It exists but it’s just not findable by anyone who doesn’t already know it’s there. That knowledge is simply unreachable.

This is the problem Panzura Nexus is built to solve, and especially for a small or mid-sized firm. Panzura Nexus comes included in Panzura Express, so it isn’t a separate product to evaluate and buy. For a smaller organization, when your project files become answerable through Copilot, the questions people used to walk down the hall to ask — and couldn’t ask at all once that person left — get answered by the work that person already documented. A new hire in their first week can query decades of precedent instead of interrupting the people who remember it. The firm’s memory stops depending on who’s in the building today.

For a lean team, that’s resilience. A large organization has depth to help overcome the loss of a key person and keep moving. A 200-person firm often doesn’t, which is exactly why making knowledge findable is worth more to it, not less.

Enterprise capability, without the enterprise

The ability to point AI at your file estate and get governed and sourced answers used to be an enterprise-only capability. It took a data team, systems integrator, and a budget to match. That’s precisely the kind of advantage that separates a firm with a hundred locations from a firm with one office.

Panzura Nexus gives a single-site firm with a three-person IT team the same file-intelligence capability of a global enterprise, without the data team or the integration project. It doesn’t require moving or rebuilding anything.

The obvious-sounding alternative is to copy everything into Microsoft 365 so Copilot can see it. That means a migration, parallel set of data to keep in sync, permissions structure to rebuild, and a duplicate of your entire file estate to secure and manage. That’s an enterprise-sized project, and it’s exactly the kind of thing a small or mid-market firm has no capacity to take on. You’d trade a visibility problem for a governance problem.

Panzura Nexus leaves the data exactly where it is and gives Copilot a way to reach it. It makes your file system’s contents discoverable and answerable through Copilot without relocating a single file. The files stay in place and Copilot gains the ability to look at them. Two things make that safe as well as useful.:

• Permissions are preserved, exactly. The moment Copilot can reach your files, the question that decides whether this is an asset or a liability is whether it respects who’s allowed to see what. This is especially important for AEC and project-based organizations.
• Answers cite their sources. An AI answer you can’t trace is a liability, especially in a field where the specifics are the whole point. Copilot answers via Panzura Nexus cite the files they came from, so a person can verify the source rather than take the AI’s word for it.

Panzura Nexus enforces your file system’s existing permissions inside Copilot, in real time. If a person can’t open a file directly, they can’t find it, see it, or reach its contents or its meaning through Copilot. The access rules you already set are the access rules the AI obeys, changing as they change. There is no permission project to run first.

Do both, and the disappointment inverts. The same Copilot that shrugged at a three-year-old project now provides meaningful answers, in plain language, citing the drawing it pulled the detail from. The tool your team already has, pays for, and knows how to use finally reaches the knowledge that makes the firm competitive.

How a mid-market firm actually gets this

Panzura Nexus reads and answers from a file system — and for that to be safe and reliable, the file system underneath it has to be one that knows its own permissions, keeps an authoritative copy of the data, and doesn’t fall over when a single site is all you run. That file system is Panzura CloudFS.

For a smaller firm, the two come together in one purchase. Panzura Express is a single-site edition of the CloudFS platform, licensed for one office and delivered through a certified Panzura partner, and Panzura Nexus is included in it. Panzura Nexus is not a separate product, an add-on you buy alongside, and not a feature gated to a higher tier. The file system that holds your project data and the intelligence layer that makes it answerable, delivered in a single package sized for a firm your size rather than a global enterprise.

That is why this is finally within reach. A large organization can often afford to build this in parts with a file platform, a data team, and an integration project to connect all of it. A small or mid-sized firm gets it as one solution that a third-party stands up: CloudFS holding the data, Panzura Nexus making it answerable in Copilot, permissions carried through from one to the other because they were designed to work together. And because Panzura Express runs the same code as multi-site CloudFS, a firm that grows into a second or more offices keeps the same file intelligence across all of them. That flexibility makes it ideal for growing organizations.

Table 2. Making files answerable – copy everything vs. retrieval layer

What it comes down to is simple. Microsoft 365 Copilot offers powerful AI. It isn’t performing the way you need because it’s been shown a fraction of what your firm knows, and the wrong fraction.

The value was never going to come from the model alone. It comes from what the model can reach. Get your project files into Copilot’s line of sight with Panzura CloudFS holding them and Panzura Nexus making them answerable, permissions intact and sources attached.

That makes Copilot what its license promised. For a small or mid-market firm, that’s a game you can with Panzura Express. The knowledge you already own, finally working as hard as you do and putting you on level ground with firms many times your size.

See what Microsoft 365 Copilot can do when it can see your files

A Panzura partner or expert can show you Panzura Express in action. Panzura CloudFS holds your project data, and Panzura Nexus answers real questions against it inside the Copilot interface your team already uses, with your permissions intact. See what it looks like when the knowledge that makes your small- or mid-sized firm competitive is finally one question away.

1. 451 Research by S&P Global: Panzura targets Copilot gap with file-to-AI retrieval layer Nexus, Henry Baltazar, 15 May 2026

451 Research by S&P Global is a trademark or registered trademark of 451 Research by S&P Global. All other product and company names are trademarks or registered trademarks of their respective holders. Use of those names does not imply any affiliation with or endorsement by their owners. The opinions expressed above are solely those of Panzura LLC.

Frequently Asked Questions (FAQs)

• How does Panzura Nexus make file data visible to Microsoft 365 Copilot without a migration?

  Panzura Nexus is a permission-preserving retrieval layer that surfaces Panzura CloudFS file content into Copilot while leaving every file where it is. There is no migration, no data lake, and no duplicate estate to secure or keep in sync. Panzura Nexus enforces the file system's existing permissions inside Copilot in real time, and answers cite the files they came from. Copilot gains reach into project drawings, specifications, and proposals without any change to where that data lives.

• Is Panzura Nexus included in Panzura Express or sold separately?

  Panzura Nexus is included in Panzura Express. It is not an add-on, a separate purchase, or a capability gated to a higher capacity tier. Panzura Express is a single-site edition of the Panzura CloudFS platform, licensed for one office and delivered through a certified Panzura partner, with Panzura Nexus in the package. For a firm evaluating AI access to its file data, the file system holding that data and the layer making it answerable arrive as one purchase.

• Why does Panzura Nexus need Panzura CloudFS underneath it?

  Panzura Nexus answers from a file system, so that file system has to know its own permissions and hold an authoritative copy of the data. Panzura CloudFS provides both, which is why Panzura Express pairs them. Permissions carry through from Panzura CloudFS into Copilot because the two were designed together rather than integrated afterward. A retrieval layer sitting on a file system that cannot enforce its own access rules would surface documents to people who should not see them.

• Does Panzura Express still work if a firm adds offices later?

  Yes. Panzura Express runs the same code as multi-site Panzura CloudFS, so expansion is applied as a license change rather than a migration or re-platforming. A firm that opens a second or third office keeps the same file intelligence across all of them, and administrators keep the interface, policies, and skills they already have. There is no forklift hardware upgrade and no separate product line to move onto, which makes Express a starting point rather than a ceiling.

• Will making file data answerable in Copilot expose documents employees shouldn't see?

  Not if the retrieval layer enforces the permissions already defined on the file system. Panzura Nexus applies existing file-system permissions inside Copilot in real time. If someone cannot open a file directly, they cannot find it, see it, or reach its contents through Copilot, and access shifts as the underlying rules shift. There is no separate permissions project to run first, and no second permission model to keep reconciled with the original.

• Should we copy our project files into Microsoft 365 so Copilot can read them?

  Copying works, but it trades a visibility problem for a governance problem. Migration means a parallel data estate to keep in sync, a permissions structure rebuilt from scratch, and a duplicate of the entire file estate to secure and manage — an enterprise-scale project a one-to-three-person IT team has no capacity to run. A retrieval layer such as Panzura Nexus leaves the files in place and gives Copilot a way to reach them instead.

• Why does Microsoft 365 Copilot give thin answers about past projects?

  Because Copilot reads what sits inside Microsoft 365 — Outlook, Teams, SharePoint, and OneDrive — and a project-based firm keeps its most valuable material elsewhere. Drawings, specifications, CAD and CAM files, proposals, and years of closeout documents live on network shares, a NAS, or other file storage. That data is not in Microsoft 365 at all, so no permissions setting will reveal it. The limitation is architectural rather than a configuration mistake.