The Defense Department canceled its long-delayed Joint Enterprise Defense Infrastructure cloud contract Tuesday, ending an up-to-$10 billion single-vendor award to Microsoft and replacing it with a new multi-cloud procurement that the Pentagon expects will initially involve both Microsoft and Amazon Web Services.

In its July 6 announcement, the department said JEDI no longer meets its requirements because military cloud needs, industry capabilities and the department’s own experience with commercial cloud computing have changed since the original solicitation. Acting Chief Information Officer John Sherman pointed specifically to Joint All-Domain Command and Control and the department’s Artificial Intelligence and Data Acceleration initiative as examples of requirements that now demand a different approach.

The cancellation closes one chapter in one of the technology industry’s most contentious federal procurements. Microsoft won JEDI in October 2019, surprising many observers who had viewed AWS as the front-runner. Amazon challenged the award in federal court, alleging errors in the evaluation and improper political influence. The litigation prevented the Pentagon from moving ahead with the modernization program while cloud technology and military requirements continued to evolve.

From one cloud provider to several

JEDI was designed as a single-award contract capable of spanning unclassified, secret and top-secret workloads and extending commercial cloud services to the tactical edge. The new Joint Warfighter Cloud Capability program will instead be structured as a multi-cloud, multi-vendor indefinite-delivery, indefinite-quantity contract.

The Pentagon’s July 6 procurement notice says market research indicates that AWS and Microsoft are currently the only U.S. hyperscale cloud providers capable of satisfying all of the department’s requirements. Defense officials say they will continue market research and consider additional providers if other companies can demonstrate the necessary capabilities.

That architecture reflects a larger shift in enterprise computing. Corporations and government agencies increasingly spread workloads across multiple providers to gain flexibility, avoid dependence on a single vendor and match different applications with different cloud services. The Pentagon is now adopting that model for a procurement originally built around the opposite premise.

Litigation helped outlive the original contract design

The 2019 award immediately became entangled in legal challenge. Amazon argued that the procurement was flawed and that then-President Donald Trump’s public hostility toward Amazon founder Jeff Bezos improperly influenced the outcome. The Defense Department defended the integrity of the process.

A comprehensive April 2020 review by the Defense Department inspector general examined the single-award strategy, requirements, source selection and allegations of outside pressure and ethical misconduct. The review documented the scale of the procurement and confirmed that Microsoft’s contract could run as long as 10 years with total orders capped at $10 billion.

The inspector general’s underlying report also described the award process and the protests that followed. Whatever the merits of the competing legal arguments, the result was a contract that remained largely unusable while the dispute continued.

Microsoft accepts the reset but criticizes the protest process

Microsoft said it understands the Pentagon’s decision and remains committed to competing for defense cloud work. In a July 6 statement, Toni Townes-Whitley, president of U.S. regulated industries, said the department faced a choice between continued litigation and a new path for delivering urgently needed technology.

Microsoft also used the moment to criticize a protest system that can delay large technology programs for years. The company said that the security needs of the country are more important than any one contract but argued that policymakers should examine whether procurement challenges can indefinitely postpone modernization after an award has been reviewed and reaffirmed.

AWS took the opposite lesson from the cancellation. In a statement reported by technology and defense publications, the company supported the move to a multi-cloud approach while maintaining that the original JEDI award had been affected by outside influence. The disagreement will now move from litigation back toward competition for actual cloud workloads.

The next contest may matter more than JEDI

The new procurement will not simply recreate the canceled contract under a different name. Defense officials say they need cloud services capable of operating at all classification levels, reaching tactical users and supporting rapidly growing data and artificial-intelligence programs.

A July 8 analysis from the Center for Strategic and International Studies noted that the reset reflects both legal delay and a substantive change in how the Pentagon views enterprise cloud architecture. A multi-cloud approach can provide access to different commercial capabilities and reduce the risk that a single vendor becomes a technological bottleneck.

Contemporaneous Reuters reporting also emphasized the strategic value of the contract beyond its dollar amount. Winning highly classified Pentagon workloads can serve as a powerful endorsement of a provider’s security and technical capabilities in the broader government and corporate cloud markets.

The immediate winner is therefore not Microsoft or Amazon but the multi-cloud model itself. JEDI was conceived when the Pentagon believed one enterprise provider could give the department a common cloud foundation. Three years of litigation and rapid technological change have produced the opposite conclusion: the department now wants multiple commercial clouds, multiple vendors and a procurement that can evolve faster than the contract it is replacing.

The cancellation does not solve the Pentagon’s cloud gap. It makes that gap more explicit. Military leaders still need a secure, globally available computing environment that can move data from headquarters to operational forces. The next competition will determine whether the department can acquire that capability before the new procurement becomes as protracted as the one it has just abandoned.