Original reporting via SDxCentral. Published October 2019.
What Is the JEDI Contract?
The Joint Enterprise Defense Infrastructure (JEDI) contract is a single-award cloud computing agreement issued by the U.S. Department of Defense (DoD). Its purpose is to modernize the Pentagon’s IT infrastructure by migrating workloads to a single enterprise cloud provider capable of operating at all three classification levels — unclassified, secret, and top secret — including at the tactical edge in operational environments.
The DoD described the contract as addressing “critical and urgent unmet warfighter requirements for modern cloud infrastructure at all three classification levels delivered out to the tactical edge.”
Structured as an initial two-year ordering period with a potential 10-year ceiling, the contract carries a maximum value of $10 billion. The DoD noted a guaranteed minimum of $1 million, with anticipated spending of approximately $210 million during the initial period based on expected project adoption.
Microsoft vs. AWS: A Surprise Outcome
When the DoD announced in October 2019 that Microsoft had won the JEDI award, it caught much of the industry off guard. For the better part of two years, Amazon Web Services (AWS) had been widely regarded as the frontrunner, given its dominant position in the government cloud market and its existing high-side certifications, including work with the intelligence community.
Several factors had, however, complicated AWS’s path to the award in the months leading up to the decision:
- Inspector General investigation: The Pentagon’s inspector general launched an inquiry into potential misconduct in the contract evaluation process, raising procedural questions about how requirements had been defined.
- Political friction: A widely reported feud between President Donald Trump and Amazon CEO Jeff Bezos created speculation about whether political considerations might influence the outcome.
- Microsoft’s quiet preparation: While attention was focused elsewhere, Microsoft steadily built its government cloud credentials, including announced plans to construct new Azure Government Secret data centers designed to handle classified workloads.
Patrick Moorhead, president and principal analyst at Moor Insights and Strategy, told SDxCentral: “From the looks of it, the DoD process looked unstructured and was full of fits and starts … almost political.”
The contract award process had also survived legal challenge, clearing reviews by both the Government Accountability Office (GAO) and the U.S. Court of Federal Claims before the final announcement.
Google’s Decision to Step Back
Google had been considered a potential bidder but ultimately withdrew from the competition. The company cited concerns that a JEDI contract might conflict with its internal AI ethics principles. Google also acknowledged that portions of the contract’s requirements fell outside the scope of its existing government security certifications. Internal employee opposition at both Google and Microsoft over work on military contracts had become a visible industry issue during this period.
At Microsoft, a group of employees published an open letter protesting the company’s pursuit of the contract. Microsoft responded by offering those employees the option to transfer to roles not connected to the JEDI work.
What the Win Means for Microsoft
Moorhead characterized the JEDI award as a “big” win for Microsoft, particularly because the contract is heavily weighted toward infrastructure-as-a-service (IaaS) workloads — an area where Microsoft’s Azure had historically trailed AWS. Much of Microsoft’s cloud revenue at the time derived from software-as-a-service (SaaS) products such as Office 365 and Dynamics 365 rather than raw compute and storage infrastructure.
Beyond the direct contract value, Moorhead noted the potential halo effect: a high-profile DoD win could strengthen Microsoft’s credibility with other government agencies and in regulated industries where security and compliance requirements are stringent.
What the Loss Means for AWS
In purely financial terms, Moorhead argued the loss was manageable for AWS. At the time of the award, AWS was running at roughly $36 billion in annualized cloud revenue. The roughly $1 billion per year average value of the JEDI contract represented a small fraction of that run rate.
“Other than a very public loss, financially it means nothing,” Moorhead wrote to SDxCentral. The more significant risk, he suggested, was reputational — the possibility that other government agencies or enterprise customers might reconsider AWS as a default choice and evaluate alternatives more seriously. Moorhead maintained that AWS remained larger in IaaS than its next ten competitors combined, a position of strength that one contract loss would not quickly erode.
Cloud Market Context
At the time of the JEDI award, both AWS and Microsoft had just reported quarterly financial results that came in below some analyst expectations for their respective cloud businesses. Despite that, market research firm Synergy Research Group projected that both vendors would increase their market share following the quarter. Chief analyst John Dinsdale forecast Amazon moving to approximately 33.5% of the global cloud infrastructure market and Microsoft to approximately 16.5%.
The JEDI decision illustrated how government procurement had become a meaningful competitive battleground for hyperscale cloud providers — not just for the contract revenue itself, but for the technical capabilities, certifications, and credibility that pursuing large government deals requires vendors to develop.
What Happened Next
AWS subsequently filed a legal challenge disputing the award, alleging that political interference had improperly influenced the evaluation. The resulting litigation placed the JEDI contract under court injunction, delaying implementation. The DoD eventually cancelled the JEDI contract in 2021 and launched a replacement multi-vendor procurement called the Joint Warfighter Cloud Capability (JWCC), awarding contracts to both Microsoft and AWS along with other providers. Readers should refer to current sources for the latest status of U.S. Defense Department cloud procurement.