Qumulo is deepening its Microsoft Azure partnership with a suite of new data services under the Azure Native Qumulo umbrella, the company announced on June 3, 2026, at an event in Seattle. The expansion aims to let enterprises shift large-scale NAS workloads into Azure while preserving their existing file structures, permissions, and application logic—no rewrites, no architecture overhauls.

For IT teams managing petabytes of unstructured data on aging on-premises filers, the pitch is simple: lift your file data into the cloud as-is, then access it through standard NFS and SMB protocols. Azure Native Qumulo has been available since 2023, but this latest wave of services adds real-time replication, automated tiering, and AI-driven performance analytics that turn a lift-and-shift migration into a native cloud operating model.

What is Azure Native Qumulo?

Azure Native Qumulo is a fully managed file data service built jointly by Microsoft and Qumulo. It runs natively inside the Azure fabric—not as a third-party appliance—and appears in the Azure portal alongside services like Azure NetApp Files and Azure Files. Under the hood, it runs Qumulo’s distributed file system software on Azure infrastructure, giving customers a scale-out file platform that handles billions of files with consistent low latency.

Unlike generic cloud file storage, Qumulo’s software is purpose-built for high-performance unstructured data workloads: media rendering, genomic sequencing, geospatial analysis, financial modeling, and electronic design automation. Its architecture treats every node equally, so capacity and performance scale linearly as you add more vCPUs and disks. The Azure Native integration means Microsoft handles the underlying VM provisioning, patching, and monitoring, while Qumulo delivers the file system logic and management experience.

With this announcement, Qumulo isn’t just offering a managed file server in the cloud. It’s introducing tools that make the Azure deployment behave like a first-class extension of an existing on-premises Qumulo cluster—or a destination for non-Qumulo NAS systems.

Moving NAS Workloads Without Replatforming: Why It Matters

Enterprise NAS migrations often stall because the target platform doesn’t support the same security model, protocol nuances, or application behaviors. A typical Windows file server with complex ACLs, deeply nested directories, and millions of small files can break backup tools or indexing services when moved to object storage. Qumulo’s approach sidesteps that pain by presenting a POSIX-compliant file system that applications consume through the same NFSv3/v4.1 and SMB3.x protocols they use today.

No replatforming means the file path stays the same. The permission model stays the same. DNS aliases can redirect from on-premises IPs to Azure endpoints without altering client configurations. Robocopy, rsync, and other bulk copy tools behave identically. For organizations with thousands of client machines, that’s the difference between a weekend cutover and a multi-year rewrite.

The new data services take that promise further. Real-time replication with configurable RPOs lets teams keep an on-premises cluster and an Azure instance in sync, enabling disaster recovery or active-active configurations. When a Datacenter outage hits, failover is as simple as updating a DNS record—users and applications reconnect automatically. And because both sides run the same Qumulo file system, there’s no translation layer to corrupt metadata or slow IO.

New Data Services: Deepening Azure Integration

Qumulo’s June 2026 update centers on three capabilities that push Azure Native Qumulo beyond storage into the data management layer.

1. Cross-Region and Hybrid Replication
The service now includes one-to-many and bidirectional replication policies managed through the Azure portal. Administrators set a replication schedule—as low as five minutes—and choose between asynchronous modes optimized for bandwidth efficiency or near-sync modes for zero-RPO requirements. The replication engine understands Qumulo’s snapshot format, so only changed blocks travel across the wire, keeping egress costs predictable. This makes it feasible to replicate a 2-petabyte file share from a U.S. East region to a Western Europe region without choking a corporate WAN.

2. Intelligent Tiering with Azure Blob
Qumulo has long offered real-time analytics that show which files are hot, warm, or cold. The new service automates the process: a policy-based engine moves cold data to Azure Blob (hot or cool tiers) while leaving stubs on the Qumulo volume. When an application or user accesses a stubbed file, Qumulo recalls it from Blob in seconds. Unlike legacy HSM solutions, the recall process preserves all file metadata and NTFS permissions, and the latency penalty is minimal because Qumulo caches the first block aggressively. This cuts capacity costs by up to 70 percent for datasets where only 10–15 percent of files are accessed regularly.

3. AI-Driven Performance Analytics
The service surfaces per-client, per-path IOPS and throughput metrics in Azure Monitor. A new anomaly detection model, trained on billions of file operations, flags unusual patterns—like a rogue process scanning every directory—and suggests mitigation steps through Azure Advisor. For capacity planning, the system projects growth rates and recommends instance sizes, blending Qumulo’s understanding of file system behavior with Azure’s visibility into VM resource consumption.

How the Migration Works in Practice

Qumulo offers two migration paths. For existing Qumulo clusters, a replication job mirrors the source to Azure Native Qumulo with a few clicks in the Qumulo UI or Azure portal. Delta syncs keep the target fresh until cutover. For third-party NAS—Isilon, NetApp FAS, Pure Storage FlashBlade—Qumulo provides a migration toolkit that scans the source, maps identities to Azure Active Directory, and orchestrates a parallel copy using the source’s native protocols. Large environments can saturate a 100 Gbps ExpressRoute circuit, completing migrations at tens of terabytes per hour.

Once in Azure, the file system inherits Azure’s security fabric. Qumulo integrates with Azure AD for identity (Kerberos, NTLMv2) and with Azure Private Link to keep traffic off the public internet. Encryption at rest uses Azure-managed keys by default, with customer-managed keys available for regulated industries. All management plane operations are audited via Azure Activity Log and can be locked down with Azure Policy.

Pricing follows a consumption model: customers pay for provisioned capacity plus transaction fees for Blob tiering. Qumulo says a 500-TB deployment with 20 percent active data and moderate replication will cost about 40 percent less than an equivalent on-premises refresh when factoring out hardware maintenance, data center power, and staffing overhead.

Real-World Use Cases

Early adopters of Azure Native Qumulo have already shown the value in three areas.

Media and Entertainment
A major visual effects studio moved 3 petabytes of project data into Azure West US 2 to handle render bursts. During peak production, Qumulo auto-scaled to 60 GB/s throughput without manual intervention. The studio projects saved $1.2 million in on-premises hardware avoided, and artists in London and Mumbai accessed the same file share through local Azure regions via replication.

Life Sciences
A genomics company processes 20,000 whole-human genomes per week, each consuming 300 GB of storage during alignment. Azure Native Qumulo’s linear scaling let them grow from 200 TB to 1.5 PB in six months, all while keeping analysis pipelines running unchanged from their on-premises HPC environment. The AI analytics flagged a CPU throttling issue that had been silently reducing throughput by 17 percent for three months.

Financial Services
A quantitative hedge fund runs Monte Carlo simulations that read historical tick data from Qumulo. By moving to Azure and enabling cross-region replication, they cut recovery time from four hours to under two minutes. During a recent Azure availability zone incident, their models failed over to a secondary region seamlessly, losing no trade signals.

The Competitive Landscape

Azure’s file storage portfolio now looks crowded, but each option serves a distinct need. Azure Files is the go-to for general-purpose SMB shares; Azure NetApp Files targets enterprise apps requiring high IOPS and low latency; and Azure Native Qumulo addresses the gap for massive, scale-out unstructured data environments where traditional NAS architecture hits walls. Qumulo’s differentiator is the combination of real-time visibility into file usage and the ability to run at exabyte scale without hot spots.

Competition comes from Weka’s parallel file system on Azure and Pure Storage’s cloud block storage, but those require more architecture changes to applications. NetApp’s ONTAP in Azure via Azure NetApp Files is a strong alternative, yet Qumulo’s replication and tiering are more tightly coupled to Azure Blob and Azure AD. The new services position Qumulo not just as a storage target, but as an active data management layer that informs cost, performance, and security decisions.

What It Means for Windows Environments

While Qumulo’s core market has been Linux-dominant HPC, the company has invested heavily in SMB protocol support and Active Directory integration. The new Azure Native Qumulo services support Windows ACLs natively, including inheritance and deny ACEs. SMB multichannel boosts throughput for Windows clients, and the analytics dashboard shows per-Share and per-User activity.

For Windows shops considering cloud migration, this means that departmental shares, user home directories, and application data stores can move to Azure without losing the security model they rely on. Administrators can continue managing permissions through Active Directory Users and Computers, and third-party backup tools like Veeam and Commvault work through the same SMB interface. Qumulo’s snapshot engine delivers near-instantaneous file-level recovery, a feature often missing in object-based archives.

Challenges and Considerations

No migration is without friction. egress bandwidth costs remain a concern for organizations that need to pull data back frequently. Qumulo’s tiering to Azure Blob helps with cold data, but hot data accessed from outside Azure incurs standard data transfer fees. Teams must also adjust monitoring paradigms: Qumulo’s real-time analytics are granular, but they generate a high volume of log data that can strain SIEM systems not configured for file metadata streaming.

Contract terms for Azure Native Qumulo are negotiated through Azure Marketplace, so enterprises must review whether their Enterprise Agreements cover the service’s hourly metered rate. There’s also a learning curve for the Azure portal integration; while Qumulo’s own management UI is familiar to its base, some settings must be configured through Azure Resource Manager templates, which requires infrastructure-as-code skills.

Despite these hurdles, Qumulo claims that 85 percent of its installed base running version 6.3 or later can replicate to Azure Native Qumulo without a product upgrade. That statistic alone suggests the company’s push toward hybrid cloud is grounded in its existing customer footprint rather than a blue-sky vision.

Industry Implications

The broader trend Qumulo taps into is the undying relevance of file data. Object storage was supposed to eat the world, but workflows built around file systems—from MRI image archives to CAD libraries—remain stubbornly resistant to object interfaces. Azure Native Qumulo’s expanded services acknowledge that reality and offer a bridge: cloud economics with file semantics.

Analysts have noted that unstructured data growth is outpacing IT budgets, forcing organizations to either archive aggressively or abandon data. Qumulo’s tiering makes archiving an automatic, background process, which could shift the conversation from “what do we delete?” to “what do we keep online?” If enough enterprises adopt the model, it may pressure other cloud providers to improve their native file offerings.

Looking Ahead

Qumulo’s roadmap, as shared in technical briefings, hints at deeper AI integrations. Expect the performance anomaly engine to generate remediation playbooks that can be executed with a single approval. The company is also testing a “zero trust” file access model that issues per-session tokens through Azure AD Conditional Access, a feature that would appeal to security-conscious Windows environments.

For now, the June 2026 release solidifies Azure Native Qumulo as a credible option for organizations that have delayed cloud adoption because their file data seemed too complex to move. By removing the replatforming barrier, Qumulo and Microsoft have turned a migration liability into a managed service with immediate business value. The question for IT leaders is no longer “Can we move?” but “How fast can we get there?”