Navy's $1.4B Microsoft BPA faces bid-protest survival
The Court of Federal Claims kept Minburn's protest alive by distinguishing challenges to an agency's evaluation from claims that a bidder misrepresented its qualifications, a line that matters far beyond this procurement.
TL;DR
The Court of Federal Claims preserved a bid protest over the Navy's $1.4 billion blanket purchase agreement for Microsoft software, awarded to Dell Federal in May 2026. Minburn Technology Group argued the Navy's evaluation was arbitrary and that Dell materially misrepresented its GSA schedule coverage, alleging Dell's price list said full product lists were "available upon request" rather than demonstrating all required Microsoft SKUs were on its schedule contract. The court drew a distinction between challenges to the agency's evaluation and claims of bidder misrepresentation.
The Navy issued the BPA on May 14, 2026, nine days after receiving proposals. The solicitation required offerors to submit their GSA-approved price list as proof they could provide all the Navy's specific Microsoft requirements from their schedule contract. That's where Minburn says the problem lies.
According to Minburn's allegations, Dell Federal's cloud computing and third-party product price list didn't enumerate every required product. Instead, it stated that full lists were available upon request. Dell also submitted a separate GSA Microsoft price list and a mapping tool to show coverage, but Minburn contended those were unofficial documents without proof they were drawn from Dell Federal's actual GSA schedule.
The court's key move was separating two kinds of challenges. One is the familiar argument that an agency evaluated proposals arbitrarily. The other (that a bidder made a material misrepresentation in its proposal) follows different rules. As Zach Prince of Haynes Boone told Federal News Network, the distinction matters because these procurement vehicles are common. The Navy, like most agencies, buys Microsoft licenses through resellers rather than directly from the OEM. It's the standard playbook for commercial software in government.
Dell Federal's not a stranger to this arena, and the complexity may explain the approach. The requirements involved hundreds of separate SKUs, and the Microsoft letter of authorization sat with parent Dell Corporation, not the federal entity. Whether that amounts to a documentation gap or something more consequential is what the case will now resolve.
For contractors watching: the decision underscores that post-award scrutiny doesn't end at evaluation-error claims. A well-pled misrepresentation allegation can reach issues an ordinary evaluation challenge can't, a line contracting officers and disappointed bidders alike will need to track as this case proceeds.
Published ·Deep Fathom