Originally reported by sify.com. Published May 2020.
Background: What Is the JEDI Contract?
The Joint Enterprise Defense Infrastructure (JEDI) contract is a single-award, indefinite-delivery/indefinite-quantity (IDIQ) cloud computing contract issued by the US Department of Defense (DoD). Valued at up to $10 billion over ten years, JEDI was intended to modernize the Pentagon’s IT infrastructure by migrating workloads to a single commercial cloud provider. In October 2019, the DoD awarded the contract to Microsoft Azure — a decision that immediately triggered a formal protest from Amazon Web Services (AWS), which had been widely regarded as the frontrunner.
AWS Files a Formal Bid Protest
AWS did not accept the loss quietly. The company filed a bid protest directly with the Department of Defense, challenging what it described as “ambiguous aspects” of the Pentagon’s revised solicitation. AWS also filed suit in the US Court of Federal Claims contesting the award decision, and separately sought a preliminary injunction to temporarily block Microsoft from beginning work on the JEDI project while the legal challenge was under review.
Central to AWS’s argument was an allegation that the evaluation process had been tainted by political interference. Amazon alleged that President Donald Trump had applied improper pressure on decision-makers — motivated, the company claimed, by personal animosity toward Amazon founder Jeff Bezos, who also owns The Washington Post.
The DoD Inspector General Weighs In
In mid-April 2020, the Department of Defense’s Inspector General released findings stating that Microsoft’s JEDI win was not influenced by President Trump and was completely legal. This report dealt a significant blow to one of AWS’s primary lines of attack, but did not end the company’s broader protest over technical evaluation factors.
The Public Exchange: AWS vs. Microsoft
Following the Inspector General’s report and AWS’s continued legal challenges, both companies escalated the dispute into an unusually public war of words conducted partly through official blog posts.
Microsoft’s Position
Frank X. Shaw, Corporate Vice President of Communications at Microsoft, characterized AWS’s fresh challenge as “disappointing but not surprising.” In a statement, Shaw said:
“The only thing that’s certain about Amazon’s new complaint is that it will force American warfighters to wait even longer for the 21st-century technology they need — perpetuating Amazon’s record of putting its own interests ahead of theirs.”
— Frank X. Shaw, Corporate VP Communications, Microsoft
Microsoft’s broader argument was that continued delays caused by AWS protests were harming US military readiness, framing AWS’s legal strategy as self-interested obstruction.
AWS Fires Back
Drew Herdener, Amazon’s Vice President of Worldwide Communications, responded sharply in an AWS blog post, accusing Microsoft of publishing “multiple self-righteous and pontificating blog posts that amount to nothing more than misleading noise intended to distract those following the protest.”
“We don’t think the JEDI award was adjudicated fairly, we think political interference blatantly impacted the award decision, and we’re committed to ensuring the evaluation receives a fair, objective, and impartial review.”
— Drew Herdener, VP Worldwide Communications, Amazon
Herdener also argued that the initial award was “fatally flawed on all six of the technical evaluation factors” and added a pointed reference to Microsoft’s service reliability:
“Microsoft is doing an awful lot of posturing. We understand why. Nobody knowledgeable and objective believes they have the better offering. And, this has been further underscored by their spotty operational performance during the COVID-19 crisis (and in 2020 YTD).”
— Drew Herdener, VP Worldwide Communications, Amazon
Herdener concluded with a direct warning to Microsoft:
“We won’t back down on this front regardless of whether Microsoft chooses to try to bully its way to an unjust victory. We also won’t allow blatant political interference or inferior technology to become an acceptable standard.”
— Drew Herdener, VP Worldwide Communications, Amazon
Why This Dispute Matters for Cloud Procurement
The JEDI controversy highlights several important issues that go beyond corporate rivalry:
- Single-vendor vs. multi-cloud strategy: The DoD’s decision to award JEDI as a single-vendor contract was itself controversial. Many cloud architects argue that large-scale government infrastructure benefits from a multi-cloud approach to avoid vendor lock-in and improve resilience.
- Procurement integrity: When a contract of this scale is awarded, the evaluation criteria, scoring methodology, and decision-making process face intense scrutiny. AWS’s protest forced DoD to re-evaluate portions of its scoring, which itself resulted in a corrected award — again to Microsoft.
- Political risk in government cloud deals: The allegations of political interference introduced a new variable into cloud vendor selection discussions at the government level, raising questions about how future large-scale federal contracts should be insulated from executive branch influence.
- Cloud reliability as a competitive argument: AWS’s public reference to Microsoft’s outages during the COVID-19 period — when demand on cloud services surged globally — reflects how operational track record is increasingly cited as a differentiator in high-stakes enterprise procurement.
Timeline of Key Events
- October 2019: DoD awards JEDI contract to Microsoft Azure.
- Late 2019: AWS files initial protest with the Court of Federal Claims; seeks preliminary injunction to pause Microsoft’s work.
- Early 2020: AWS files fresh bid protest directly with the DoD, challenging the revised solicitation.
- Mid-April 2020: DoD Inspector General concludes that political interference did not affect the JEDI award.
- May 2020: Public exchange of statements between AWS and Microsoft escalates via blog posts and press releases.
Video: JEDI Contract Overview
What Happened Next
The JEDI legal battle continued well beyond May 2020. The DoD ultimately cancelled the JEDI contract in 2021 and replaced it with a new multi-vendor program called the Joint Warfighter Cloud Capability (JWCC), which invited both AWS and Microsoft — along with other cloud providers — to compete. This outcome partially validated the arguments of those who had questioned the single-vendor approach from the start.
Note: The cancellation and replacement of JEDI with JWCC occurred after this article’s original publication date. The above represents subsequent public reporting on the contract’s outcome.