Introducing Panzura Nexus: Copilot, Meet Your Files

Panzura Nexus Connects Your CloudFS File Data to Microsoft 365 Copilot Without Migrating Files, Rebuilding Permissions, or Writing Custom Connector Code

Key Takeaways:

• Microsoft 365 Copilot cannot see enterprise file data by default — the project files, drawings, and contracts your teams work with remain invisible to the AI your organization is already paying for.
• Panzura Nexus closes that gap without migrating files or changing access controls. It reads CloudFS content, enforces your existing Active Directory permissions, and makes the data searchable through Copilot.
• Event-driven updates keeps the Copilot semantic index current within seconds of any file change. Permissions are enforced at query time against your existing NTFS ACLs translated to Entra ID. Deployments advance from kickoff to active ingestion in under a week.

If you run Panzura CloudFS, you already know where your most important data lives — and it isn't in SharePoint. Enterprises have bet on Microsoft 365 Copilot. Licenses are procured, users are onboarded, and the pressure to show ROI is starting to land. But most of those users are discovering the same uncomfortable thing: the data that actually runs the business — project files, engineering drawings, contracts, design history — isn’t visible to Copilot. In short, their artificial intelligence (AI) is not working on their most valuable data.

According to IDC research, 90% of the data organizations generate is unstructured. For CloudFS customers, that ratio is not abstract — it’s the reason your global namespace exists. The files your teams collaborate on across sites, the engineering history your AEC practice depends on, the matter files your legal team searches, the design records your manufacturing lines reference: all of it lives on CloudFS precisely because SharePoint was never the right home for it.

This isn’t a training or prompt problem. The real problem is coverage. Microsoft 365 Copilot sees SharePoint, OneDrive, Teams, and Exchange. That's the boundary of its default world. Every file that sits outside that boundary — on a network share, in an archive, on a global file system like Panzura CloudFS — is invisible.

Table 1: What Microsoft 365 Copilot Sees by Default

The industry’s first-order answer has been to migrate to SharePoint. It’s a simple plan on paper, however, in practice it can break access control patterns your teams rely on, triggers compliance conversations nobody wants to have, and turns a productivity initiative into a months-long, expensive IT project. For most organizations — particularly in AEC, legal, manufacturing, and life sciences — it just isn’t a viable option.

The second-order answer has been to build a custom Microsoft Graph connector. Technically, this works. It also typically requires an extensive services engagement, custom identity mapping code, and ongoing maintenance forever. This is the path that many Panzura competitors have pursued, and the limits are real. Every Microsoft API update is an engineering ticket. Every file system upgrade is regression testing. The people who do this successfully are rare, and technologists tire of keeping up-to-date with the latest changes to the underlying ecosystems.

The third answer is to do nothing and accept the status quo. In this case, Copilot cannot see the most valuable data an organization owns, producing no discernable value add. Copilot licenses sit underutilized, and ROI conversations stall. Unfortunately, this is the most common path given the significant headwinds posed by the first two options.

Panzura Nexus: A Purpose-Built Bridge to AI Intelligence

Panzura Nexus is a better option, purpose-built for the file system you already run. The initial file system integration is for Panzura CloudFS. It’s a set-and-forget software platform that reads file content and metadata from your CloudFS nodes, enforces your existing Active Directory permissions, and makes that data searchable through Microsoft 365 Copilot. Files don’t move and access controls don’t change. Copilot gets a governed, real-time window into enterprise file data at a massive scale.

The architecture has three pieces.

• Storage Plugin: This connects to your CloudFS master node, reads content via SMB, and subscribes to audit events so that change detection is continuous rather than scheduled.
• AI System Plugin: This connects to Copilot through the Graph Connector API — the Microsoft-supported mechanism for bringing external content into the Copilot index.
• Identity Plugin: This connects to on-premises Active Directory via LDAP, maps CloudFS ACLs to Entra ID identities, and enforces those mappings on every query Copilot makes.

Administrators define policies that control what gets ingested, for instance, by file type, path, size, date, and even regular expressions. Policies can be run in dry mode to preview their effect before activation. Once live, Panzura Nexus quietly handles ingestion, change tracking, and access enforcement with no ongoing administrator effort.

Table 2: Panzura Nexus Core Capabilities

Why Architecture Matters

Two architectural choices separate Nexus from crawl-based alternatives and both will feel familiar if you know CloudFS.

The first is event-driven ingestion. Most Microsoft Graph connectors are scheduled crawlers. They scan the file system on an interval — nightly, hourly, whatever the schedule says — and push changes to Microsoft 365 Copilot. This produces a Copilot index that’s always out of date. For non-regulated applications, that’s a minor annoyance. For example, in regulated industries, where a departing employee’s AI access needs to terminate the moment they’re disabled in Active Directory and not the next morning when the scheduled crawl runs, it’s unacceptable.

Panzura Nexus subscribes to CloudFS audit events — the same event stream you already rely on for CloudFS’s own consistency and data services. When a file is created, modified, moved, renamed, or has its permissions changed, Panzura Nexus knows within seconds. The Copilot index updates in response. The practical result is an AI layer that reflects the current state of the file system not a stale snapshot.

The second is permission enforcement at query time. Panzura Nexus doesn't rebuild your access control model in a new system. It reads your existing NTFS ACLs, translates them to Entra ID identities, and enforces them on every Microsoft 365 Copilot request. If a user doesn’t have access to a file on CloudFS, they won't see it — or its contents, or even its existence — through Copilot. The security model you've built on CloudFS stays on CloudFS. Panzura Nexus is the translator, not the gatekeeper.

• For the end user: Answers become more useful because Copilot can now see the data users work with. A project manager asking about past engineering benchmarks gets a real answer. A lawyer searching for precedent language in old matter files gets a real answer. A finance analyst pulling cost variances from three years of closed project files gets a real answer. The gap between “my AI works great on my meeting notes” and “my AI is useful for my actual job” closes.
• For the IT leader: The ROI case for Copilot investment stops being aspirational. The licensed AI is doing work on the licensed data. The per-seat spend has a clearer justification. Adoption metrics improve because the tool finally does what users want.
• For the security and compliance team: Panzura Nexus doesn't invent a new permission model. It honors the one a firm already has. Every file access, whether by a user or by Copilot on that user's behalf, is governed by the NTFS ACLs, Active Directory group memberships, and CloudFS permissions already in place. If a user can’t open a file today, Copilot can’t see it through Panzura Nexus tomorrow.

Moreover, consider shadow permissions. With Panzura Nexus, there is no re-permissioning project. No parallel access model to audit. The conversation shifts from “can we trust AI with our files” to “does Panzura Nexus correctly implement the access control model we already trust." That’s a much easier conversation, and a much more auditable one.

Forrester’s Total Economic Impact study projects a 116% ROI over three years and $19.7M in net present value for a representative enterprise deploying Copilot, but those returns materialize only when the AI can reach the documents employees use to do their work. Coverage is the condition the business case rests on.

The Copilot investment your organization already made was priced against the productivity your workforce could gain. That return materializes only when the AI can reach the documents your employees use every day. For CloudFS customers, Panzura Nexus is how coverage becomes the reason the business case wins — rather than the reason it falls short.

Getting Started with Panzura Nexus

Panzura Nexus is generally available now to Panzura CloudFS customers. If you have active Copilot licenses and CloudFS in production, you already have everything you need to evaluate it. Deployment is typically days to full infrastructure provisioning, a five-step setup wizard, plugin configuration with a Panzura Solutions Engineer, and a dry-run of your first policy. Customers are typically in active ingestion within a week of kickoff.

The data gap that has been stalling your Copilot value is solvable with the file system you already run, and the Panzura Nexus platform.

To get started, contact your Panzura Customer Success Manager (CSM) to schedule a Panzura Nexus readiness review.

We can walk you through policy scoping for your CloudFS footprint, confirm your Microsoft 365 Copilot licensing is in the right state, and book time with a Solutions Engineer for deployment. If you’d prefer a product walkthrough before looping in your CSM visit panzura.com/demo.

Microsoft, Microsoft 365, Microsoft 365 Copilot, Microsoft Copilot Studio, Microsoft Azure, and Microsoft Graph are trademarks of the Microsoft group of companies. All 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 as of April 29, 2026, and Panzura LLC makes no commitment to update these opinions after such date.

Frequently Asked Questions

• What is Panzura Nexus?

  Panzura Nexus is an AI platform that connects file data to Microsoft 365 Copilot without migrating files or changing access controls. For example, it reads content and metadata from Panzura CloudFS, maps existing Active Directory permissions to Microsoft Entra ID, and makes enterprise file data searchable through Copilot in near real time. Panzura Nexus uses three integrated components (a storage plugin, an AI system plugin, and an identity plugin) to bridge on-premises and hybrid cloud files into Microsoft’s AI experience.

• How is Panzura Nexus different from a custom Microsoft Graph Connector?

  Panzura Nexus is a purpose-built, supported product, while custom Microsoft Graph Connectors are services engagements that typically require 12-18 months to build and ongoing engineering to maintain. Panzura Nexus uses event-driven ingestion, so file changes reach Microsoft 365 Copilot within seconds. Most custom connectors rely on scheduled crawls that leave the index out of date. Panzura Nexus also includes native Active Directory to Entra ID permission mapping, which custom connectors require engineers to build manually. 

• Does Panzura Nexus require moving files to SharePoint?

  No. Panzura Nexus makes file data visible to Microsoft 365 Copilot without migrating files to SharePoint or OneDrive. For example, files remain on CloudFS, access controls stay on existing Active Directory, and Copilot reaches the data through the Microsoft Graph Connector API. This avoids the months-long migration projects, compliance reviews, and broken access patterns that SharePoint migration typically creates a serious issue in regulated industries like AEC, legal, manufacturing, and life sciences.  
  

• How does Panzura Nexus enforce file permissions in Microsoft 365 Copilot?

  Panzura Nexus enforces existing file system NTFS permissions, such as those with Panzura CloudFS, on every Microsoft 365 Copilot query. It connects to on-premises Active Directory via LDAP, maps file system access control lists to Microsoft Entra ID identities, and applies those mappings at query time. Users only see data in Copilot they are already authorized to access on their file system or other data platform. When user Active Directory access is revoked, their Copilot access to those files is revoked within seconds.

• How does Panzura Nexus keep the Microsoft 365 Copilot index current?

  Panzura Nexus uses event-driven ingestion rather than scheduled crawls. It subscribes to CloudFS audit events, so when a file is created, modified, moved, renamed, or has its permissions changed, Panzura Nexus detects the change within seconds and updates the Microsoft 365 Copilot semantic index accordingly. This means Copilot answers reflect the current state of the file system, which is critical in regulated industries where AI access rights must terminate the moment Active Directory is updated, not the next morning.

• How long does Panzura Nexus take to deploy?

  Panzura Nexus typically deploys in days, not months. Initial deployment includes software infrastructure provisioning, a five-step setup wizard, plugin configuration with a Panzura Solutions Engineer, and a dry-run of the first ingestion policy. Customers are generally in active ingestion within a week of kickoff. Administrators then refine policies by file type, path, size, date, or time to control exactly what Microsoft 365 Copilot sees across a global namespace.

• How is Panzura Nexus licensed?

  Panzura Nexus uses capacity-based licensing tied to the file system’s managed storage. Pricing scales with the size of the file system under management rather than with Microsoft 365 Copilot seat count, ingestion volume, or per-query usage. Panzura Nexus is already available to Panzura CloudFS customers with active Microsoft 365 Copilot licenses.