Virtamove v. Microsoft (AKS): Stipulated Dismissal After 83 Days
Virtamove, Corp. filed a patent infringement action against Microsoft in the Western District of Texas, asserting US7774762B2 against Azure Kubernetes Service. The case closed in just 83 days via a joint stipulation of dismissal under Rule 41(a)(1)(A)(ii), leaving the terms of resolution undisclosed on the public record.
Container virtualisation patent closes fast in Waco via joint stipulation
On 30 May 2025, Virtamove, Corp. filed a patent infringement action against Microsoft, Co. in the Western District of Texas (Case No. 7:25-cv-00254), presided over by Judge Alan D. Albright. Virtamove asserted US7774762B2 — a patent covering container virtualisation and application portability — against Microsoft’s Azure Kubernetes Service (AKS), one of the dominant managed container orchestration platforms in the enterprise cloud market.
The case closed on 21 August 2025, just 83 days after filing, when both parties filed a stipulation of dismissal under Federal Rule of Civil Procedure 41(a)(1)(A)(ii). Judge Albright directed the Clerk of Court to close the case. The public record does not specify whether the dismissal was with or without prejudice, which is a legally significant distinction governing whether Virtamove may refile the same claims against Microsoft.
An 83-day resolution is notably compressed for a patent case in the Western District of Texas, suggesting the parties likely reached a private resolution — potentially a licence, covenant not to sue, or commercial agreement — before substantive litigation commenced. No claim construction, discovery schedule, or merits briefing appears in the docket at this stage. The absence of a prejudice designation and financial terms means the strategic outcome for both parties remains opaque from the public record alone.
Filing to Case Dismissed in 83 days
83 days — well below the multi-year median for patent cases in W.D. Texas
Stipulated dismissal: what the Rule 41 closure means for both parties
Rule 41(a)(1)(A)(ii) — joint stipulation, no court merits ruling
A dismissal under FRCP 41(a)(1)(A)(ii) requires signatures from all parties who have appeared and takes effect without a court order on the merits. The court’s role is purely administrative — instructing the clerk to close the case. Critically, the public record here is silent on whether dismissal is with or without prejudice, meaning the legal finality of the resolution is not publicly determinable.
No merits adjudicationWith or without prejudice? The public record is silent
Whether a voluntary stipulated dismissal is with or without prejudice determines whether the plaintiff can refile the same patent claims against the same defendant. ‘Without prejudice’ preserves that right; ‘with prejudice’ extinguishes it. The court’s order here does not specify either. Practitioners should not assume either designation applies — the distinction may be contained in a private agreement between the parties that is not publicly filed.
Prejudice terms undisclosedVirtamove exits without a public win — but terms may favour licensor
Virtamove obtained no public judgment or damages award. However, the rapid 83-day closure before any substantive litigation — no claim construction, no discovery — suggests a private commercial resolution was likely reached. Patent licensing entities in this posture often secure licences or covenants in lieu of protracted litigation, particularly when asserting foundational infrastructure patents against large enterprise cloud operators.
Likely private resolutionMicrosoft avoids public merits ruling on AKS container technology
Microsoft, represented by DLA Piper, avoided any court finding on infringement or validity of US7774762B2 with respect to Azure Kubernetes Service. An early resolution of this nature is consistent with Microsoft’s documented preference for resolving patent disputes before extensive litigation costs accrue. Without a prejudice designation or invalidity ruling, the patent’s enforceability against AKS remains unresolved in the public record.
No invalidity ruling securedFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Virtamove, Corp. | Company | Container virtualisation IP licensor — holder of US7774762B2Search in Eureka ↗ |
| Defendant | Microsoft, Co. | Company | Microsoft, Co. — developer and operator of Azure Kubernetes ServiceSearch in Eureka ↗ |
| Plaintiff counsel | Christian W. Conkle | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Daniel B. Kolko | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jacob R. Buczko | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | James Milkey | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | James S. Tsuei | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jefferson Cummings | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jonathan Ma | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Linjun Xu | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Mackenzie Paladino | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Marc A. Fenster | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Neil A. Rubin | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Qi (Peter) Tong | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Reza Mirzaie | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Russ August Kabat LLP | Law Firm | Representing Virtamove, Corp.Search in Eureka ↗ |
| Defendant counsel | John M. Guaragna | Attorney | Counsel for Microsoft, Co.Search in Eureka ↗ |
| Defendant law firm | DLA Piper US LLP | Law Firm | Representing Microsoft, Co.Search in Eureka ↗ |
| Presiding judge | Judge Alan D Albright | Judge | Texas Western District CourtSearch in Eureka ↗ |
Official order — verbatim text
The court’s closing instruction recites the parties’ stipulation under Rule 41(a)(1)(A)(ii) verbatim and contains no merits analysis, claim construction findings, or damages assessment. The absence of a prejudice qualifier in the court’s order is notable — it leaves the door open to legal ambiguity about refiling rights, though parties to the stipulation may have specified terms privately. No finding on infringement or validity of US7774762B2 was made.
US7774762B2 — container virtualisation and application portability
US7774762B2 (application no. US11/380285) covers container virtualisation and application portability technology — specifically methods and systems enabling applications to run in isolated container environments across heterogeneous server infrastructure without modification. The patent addresses the technical challenge of application isolation and portability that underpins modern container orchestration platforms including managed Kubernetes services. Its filing predates the mainstream containerisation era, giving it foundational claim scope that may read broadly on current implementations.
In the context of Azure Kubernetes Service, the patent’s relevance lies in the architecture of container runtime isolation, workload scheduling, and application encapsulation — core functions of any managed Kubernetes offering. For the broader sector, a foundational container virtualisation patent that survives assertion against a hyperscaler’s managed service without an invalidity ruling represents a live risk for any vendor operating in the container, Kubernetes, or PaaS space. Competitors, ISVs building on managed Kubernetes, and enterprise Kubernetes distribution vendors should treat this patent as an active enforcement risk.
Should your container platform team run an FTO against US7774762B2?
Any organisation developing, deploying, or commercialising container orchestration platforms, managed Kubernetes services, container runtimes, or application virtualisation layers should assess exposure to US7774762B2. The patent’s assertion against Azure Kubernetes Service — one of the world’s largest managed container platforms — signals that Virtamove is actively monitoring hyperscaler and enterprise container implementations. The absence of an invalidity ruling means the patent cannot be dismissed on prior art grounds based on this case alone.
PatSnap Eureka’s FTO Search Agent enables R&D and IP teams to rapidly map US7774762B2’s independent claims against their specific container isolation and orchestration architectures. Eureka surfaces prosecution history, claim differentiation, and prior art landscapes to help you assess whether design-arounds or licensing negotiations are warranted — before a demand letter arrives. Start with a targeted claim chart for your container runtime or Kubernetes distribution implementation.
Run a freedom-to-operate analysis on US7774762B2 to assess your product’s exposure
Run FTO in Eureka →Similar container virtualisation patent cases in W.D. Texas
Related infringement actions involving container virtualisation and managed Kubernetes patents litigated in the Western District of Texas before Judge Albright.
What this case signals for the container virtualisation IP landscape
A fast stipulated dismissal in a W.D. Texas AKS case is a signal worth unpacking for cloud infrastructure IP strategy.
Rapid closure in W.D. Texas suggests pre-litigation leverage was effective
Cases that close within 83 days in Judge Albright’s court — before claim construction or scheduling orders — typically indicate either a swift licence agreement or a strong early commercial incentive to resolve. Container infrastructure patents asserted against hyperscaler managed services are increasingly being resolved through licensing rather than full litigation cycles.
US7774762B2 remains valid and enforceable: no invalidity finding on record
Because the case was dismissed without a merits ruling, US7774762B2 retains its presumption of validity. Any container orchestration or application portability vendor that overlaps with the patent’s claims should assess exposure — this dismissal provides no safe harbour for third parties. An FTO analysis referencing this patent is advisable for AKS-adjacent products.
Virtamove v Microsoft — key questions answered
Virtamove, Corp. filed a patent infringement action against Microsoft, Co. in the Western District of Texas on 30 May 2025, asserting US7774762B2 against Azure Kubernetes Service. The case was closed on 21 August 2025 — 83 days later — via a joint stipulation of dismissal under Rule 41(a)(1)(A)(ii). No merits ruling was issued and the prejudice designation is not specified in the public record.
US7774762B2 covers container virtualisation and application portability technology — methods enabling applications to run in isolated container environments across server infrastructure. It was asserted against Azure Kubernetes Service because AKS’s container isolation, orchestration, and runtime architecture may overlap with the patent’s claims covering virtualised application execution environments. The patent’s foundational filing date gives its claims potentially broad scope over modern container platforms.
The public record does not specify whether the dismissal is with or without prejudice. The court’s order simply instructs the clerk to close the case following the parties’ Rule 41(a)(1)(A)(ii) stipulation. Any prejudice terms may be contained in a private settlement or licence agreement not publicly filed. This distinction is legally significant: without prejudice would allow Virtamove to refile; with prejudice would bar further claims on the same patents.
An 83-day resolution before any claim construction, discovery, or merits briefing is consistent with a private commercial resolution — typically a patent licence, covenant not to sue, or other commercial agreement. In the Western District of Texas, where patent cases can run 2-3 years to trial, early stipulated dismissals of this kind typically signal that litigation was a negotiating lever rather than an end in itself. The specific terms are not part of the public record.
No. Because the case was dismissed without any merits adjudication, there is no court finding on infringement or invalidity of US7774762B2. The patent retains its statutory presumption of validity under 35 U.S.C. § 282. Third parties — including other cloud and container platform operators — cannot rely on this dismissal as a safe harbour. An independent FTO analysis or IPR petition would be required to challenge the patent’s validity.
PatSnap Eureka searches patents and litigation data to answer instantly.