Full Opinion

In the United States Court of Federal Claims No. 26-861 Filed: November 17, 2026∗ ) MINBURN TECHNOLOGY GROUP LLC, ) ) Plaintiff, ) ) v. ) ) UNITED STATES, ) ) Defendant, ) ) ) DELL FEDERAL SYSTEMS L.P., ) ) Defendant-Intervenor ) ) Alexander B. Ginsberg, Fried, Frank, Harris, Shriver & Jacobson LLP, Washington, D.C., for plaintiff. With him on the briefs were Robert C. Starling and Noah B. Curtiss. Tayna B. Koenig, Senior Trial Counsel, United States Department of Justice, Civil Division, Commercial Litigation Branch, Washington, D.C., for defendant. With her on the briefs were Ana F. Smith, Department of the Navy, Naval Information Warfare Center Pacific, and J. Eric Anderson, Associate Counsel Office of Intellectual Property, 36000, Naval Information Warfare Center Pacific. Craig Alan Holman, Arnold & Porter Kaye Scholer LLP, Washington D.C., for defendant- intervenor. With him on the briefs were Thomas A. Pettit, Roee Talmor, Adrienne Jackson, and Kristina Lorch. OPINION AND ORDER SMITH, Senior Judge In this post-award bid protest, the Court considers whether the government’s failure to disclose a policy mandating exclusive use of a contract vehicle undermined competition. Plaintiff Minburn Technology Group LLC (“Minburn”) challenges the United States Navy’s (“the Navy”) award of a blanket purchase agreement (“BPA”) issued under the Federal Supply Schedule ∗ An unredacted version of this Opinion was issued under seal on September 25, 2026. See ECF No. 62. The Court provided the parties with the opportunity to submit proposed redactions. The Court accepts all proposed redactions. 1 Program (“FSS”) to Intervenor Dell Federal Systems L.P. (“Dell Federal”). That Enterprise Services Agreement (“ESA”) concerns the procurement of Microsoft products and services for the Navy and the United States Department of War (“DoW”) at large. 1 Minburn alleges that the Navy did not disclose its actual requirement that DoW would require mandatory, exclusive use of the ESA moving forward. Along those lines, Minburn also claims that the Navy’s policy constitutes a cardinal change which drastically changed the nature of competition. Minburn further argues that the government failed to complete an unbalanced pricing analysis when Dell Federal proposed an anomalous discount to a single line item in its proposal. In opposition, the Navy and Dell Federal contend that the solicitation contemplates exclusive use and that an unbalanced pricing analysis was unnecessary due to changes in the Federal Acquisition Regulations (“FAR”). Before the Court are the parties’ cross-motions for judgment on the administrative record. See Pl.’s Am. Mot. for J. on the Administrative R., ECF No. 42; Def.’s Cross-Mot. for J. on the Administrative R., ECF No. 46; Intervenor’s Cross-Mot. for J. on the Administrative R., ECF No. 48. For the following reasons, the Court GRANTS Minburn’s motion, ECF No. 42, and DENIES the Navy and Dell Federal’s motions, ECF Nos. 46, 48. I. BACKGROUND A. The Enterprise Software Initiative Seeks to Consolidate and Streamline DoW’s Commercial Software Acquisition Purchases. In 1998, DoW established the Enterprise Software Initiative (“ESI”) to streamline its acquisition of commercial software. See Def.’s Ex. 1, ECF No. 46-2 at 10. Since its inception, DoW’s ESI has promoted ESA agreements to procure information technology (“IT”) software products and services across its enterprise. Starting in 2010, the Navy began procuring Microsoft products and services through Enterprise Software Licensing Agreements. Admin. R. (“AR”) Tab 1 at 2. From 2012 to 2018, the agency awarded several agreements to resellers of Microsoft products. Id. Those resellers also held Multiple Award Schedule contracts (“MAS”) issued by the General Services Administration (“GSA”). Id. 2 The agreements consolidated Microsoft procurements across the Navy, “providing improved visibility, control, and pricing compared to the previous decentralized approach.” Id. The Navy continued its efforts to implement and manage IT agreements across DoW through “consolidating, centralizing, and streamlining IT acquisition.” Id. As a result, the Navy awarded multiple vendors, including Minburn and Dell, 10-year ESI BPAs in connection with their GSA MAS contracts in 2018. Id. That same year, DoW designated the Navy as Executive Agent for Core Enterprise Technology Agreements (“CETA”) for the entire department. AR Tab 37 at 2192 (citing DoD 1 For purposes of this Opinion, the United States Department of Defense (“DoD”) is synonymous with DoW and will be used interchangeably. 2 “The Federal Supply Schedule program is also known as the GSA Schedules Program or the Multiple Award Schedule Program.” See 48 C.F.R. § 8.402(a). GSA manages and directs the FSS program to simplify “obtaining commercial supplies and commercial services at prices associated with volume buying.” Id. 2 Directive 8470.01E). CETAs aim “to consolidate and streamline software acquisition across the entire DoW enterprise” through favorable terms and pricing. AR Tab 29 at 1635. Agreements designated as a CETA also ensure efficient supplier management and strategic technology alignment. AR Tab 4 at 22. Regulations provide that an ESI agreement with a CETA designation becomes “mandatory for use when a procurement requirement is within the scope of the CETA contract.” AR Tab 37 at 2192. B. Minburn’s DEOS BPA and the Predecessor to ESA II Cover DoW’s Enterprise Needs for Microsoft Products and Services. DoW “requires a robust and adaptable suite of office productivity, collaboration, security and compliance products” across its diverse environments. AR Tab 1 at 1. Evaluations of other vendors determined that Microsoft provides superior functionality and adaptable solutions to satisfy DoW’s requirements. Id. at 3. Thus, “Microsoft products are foundational to the DoD’s IT infrastructure” by “enabling secure mission execution, maintaining network operability, mitigating vulnerabilities, and driving cost efficiencies.” AR Tab 1 at 3, Tab 3 at 10. Microsoft conducts business through resellers but only utilizes seven License Solutions Partners (“LSPs”) to enter into agreements with the government. AR Tab 3 at 15, 17. LSPs, which include Minburn and Dell Federal, are partners authorized by Microsoft to engage in enterprise licensing. AR Tab 4 at 32. In 2020, the Navy awarded Minburn with the Defense Enterprise Office Solution (“DEOS”) BPA No. 47GTCA21A0003. See generally AR Tab 40. Under DEOS, Minburn resells cloud-based Microsoft products and services. See id. Those products and services would aid classified and non-classified operations in the United States and abroad. Id. at 2228. Offerings classified as “Secret” are designated “Impact Level 6” (“IL6”) and products that qualify as “Top Secret” are denoted as “Impact Level 7” (“IL7”). Id. at 2294. Minburn processes all orders of IL6 and IL7 products and services which accounted for percent of its gross revenue in 2025. See Am. Dec. of , ECF No. ECF No. 19-1 at ¶¶ 13–14. 3 To carry out DEOS, Minburn also partnered with General Dynamics Information Technology Inc. and Dell Marketing L.P. under a Contractor Team Arrangement. AR Tab 40 at 2226. DEOS contemplated an initial 10-year ordering period through 2030. Id. at 2228. The Navy further described DEOS as “a brand agnostic competition where Microsoft was the chosen technology.” AR Tab 1 at 2–3. At the same time, DoW awarded Dell Marketing with DoD Enterprise Services Agreement I (“ESA I”) in June 2021. See AR Tab 4 at 24, Tab 36f at 2165. The Navy would begin using this single-award BPA “with other Services joining as their Enterprise Agreements [] naturally expire.” AR Tab 36b at 2105. Dell Federal joined its corporate affiliate as a teaming partner for the five- year BPA which expired on May 31, 2026. AR Tab 36f at 2165. While initially valued at $2.5 billion, ESA I ballooned to accommodate $4.5 billion due to high demand for Microsoft licensing. AR Tab 1 at 2. DoW noted that ESA I “replaced earlier BPAs and is now the acquisition vehicle used for Microsoft licensing across the DoW.” AR Tab 3 at 10. 3 Minburn attached this declaration to its motion for a temporary restraining order and preliminary injunction, ECF No. 19. The Court adopts testimony for background purposes and to this Court’s record to address the non-merits factors for injunctive relief. See AshBritt, Inc. v. United States, 87 Fed. Cl. 344, 366–67 (2009). 3 In August 2021, the Navy issued a memorandum stating that it would designate DEOS and ESA I as CETAs. AR Tab 37 at 2192. “Once finalized, these purchasing vehicles will be mandatory for all DOD components and agencies and will use decentralized component-level funding.” Id. The 2021 memorandum directed DoW components to use DEOS for cloud-based licenses and ESA I for on-premises licenses. Id. 4 Components were ordered to transition “at the earliest convenience or as existing contracts expire.” Id. Any agency opting out of either agreement would require “a request and justification for that decision.” Id. But in 2025, the DoW prepared another memorandum stating its “strategy to streamline software acquisition and optimize software management, resulting in significant cost savings and improved operational efficiency.” AR Tab 38 at 2193. DoW’s plan emphasized “accelerating [CETAs and ESAs], developing a software licensing governance strategy, and establishing DoD- wide software agreement policies.” Id. at 2196. That led to another internal memorandum that was circulated in December 2025 in anticipation of what became ESA II. AR Tab 39 at 2225. In its memo, DoW stated that all “Components are hereby directed to align their current and future Microsoft agreements to the greatest extent practicable” starting in June 2026. Id. The memorandum also provided that Components “are expected to procure Microsoft products exclusively through the ESI-provided catalog.” Id. C. The Navy Issues the Solicitation and Awards Dell Federal ESA II. In May 2026, the Navy issued Solicitation No. N6600126Q00510002 and amended it twice. See generally AR Tabs 10, 11. DoW sought “a new, comprehensive” BPA against GSA MAS for Microsoft products and services. AR Tab 11 at 573. ESA II would “build upon the successes and lessons learned from” ESA I, “which demonstrated substantial cost avoidance and improved license management.” AR Tab 3 at 24. The follow-along to ESA I would continue to offer licensing models and product capabilities that meet the evolving operation, cybersecurity, and mission requirement of both [Department of the Navy] stakeholders and the greater DOW.” AR Tab 3 at 11. 5 ESA II would feature five annual ordering periods beginning in June 2026 and ending on April 30, 2031. AR Tab 11 at 549. The Navy estimated ESA II’s maximum value at $9.668 billion. Id. ESA II was “contingent upon the Contractor maintaining products/services of the BPA on the applicable GSA Schedule.” Id. Accordingly, the Navy issued the Solicitation to pre-existing GSA MAS contract holders, which again included Minburn and Dell Federal. The Solicitation also included Attachment 2 which listed all Microsoft products and services offered under ESA II. See generally AR Tab 11b. Within Attachment 2, each Contract Line Item Number (“CLIN”) contained a corresponding Microsoft product and Stock Keeping Unit (“SKU”) code. Id. DoW set the deadline for proposals for May 12, 2026. 4 DoW announced an “interim exception” to the 2021 memorandum to allow DoW components to purchase cloud-based licenses from either DEOS or ESA I. AR Tab 34 at 1948. 5 Like ESA I, customers under ESA II would include the Navy, the Department of the Air Force, the Defense Information Systems Agency, and the Fourth Estate, a collection of “defense agencies and field activities that are organizationally separate from the military services.” AR Tab 3 at 11. 4 Elsewhere, the Solicitation required that all “products offered must be on your GSA MAS” and that Resellers must complete Attachment 2. AR Tab 11 at 573. To evidence product inclusion on their GSA MAS, Resellers would submit a copy of their GSA Approved Price List.” Id. Offerors would further certify that “all products listed in Attachment 2 are currently included on” their FSS contract. Id. at 570; see also id. at 574 (reiterating these requirements as eligibility criterion for award). Solicitation Attachment 2 contained fields for offerors to insert their pricing and the Navy provided estimated quantities for each product and service. See AR Tab 11b. Aside from a contractor’s proposed prices, “Ordering Officers will still be able to negotiate for spot discounts at the call or order level.” AR Tab 4 at 38. The Solicitation mandated that offerors provide discounts at least two percent below their GSA FSS contract. AR Tab 11 at 573. Other eligibility criteria required a “Letter of Authorization” signed by a Microsoft representative and Top-Secret Level Facility Clearance. Id. at 574. As for ESA II’s scope, the BPA contemplated that licenses would encompass all Microsoft software used on all DoD networks. Id. at 549. In addition, government entities “may transition into the Agreement at any time following the expiration of their own Agreement.” Id. at 549. The Solicitation also noted that if customers under DEOS “at any time during the duration of this agreement, decide to transition its Enterprise Products to the DoW ESA II Agreement, then Microsoft and the Contractor shall ensure the transition is made with no penalty to the Government.” Id. at 560. To realize ESI’s goals, the Solicitation encouraged contractors to enforce “the policy that [ESA II] is mandatory for consideration in accordance with DFARS Subpart 208.74.” Id. The Navy would evaluate all eligible offerors “based on the total overall price (of all the products and services found in Attachment 2 at the estimated quantities stated).” Thus, “the responsive reseller whose quote conforms to all RFQ requirements, meets all eligibility criteria . . . and offers the lowest” price would receive ESA II. Id. at 577. The Navy received offers from Minburn, Dell Federal, and Carahsoft Technology Corp. AR Tab 28 at 1629–30. Between each proposal, Dell Federal offered the lowest price. In comparison, Dell Federal offered a price of $11,406,845,996.85, or 4.45 percent lower than Minburn’s offer at $11,914,188,605.35. See AR Tab 29 at 1643. In a pricing analysis, the Navy not only compared prices between Minburn and Dell Federal but also compared prices to historical prices paid under DEOS. Id. at 1644. The price analysis concluded that “ESA II offers substantial cost savings for most of the products analyzed, resulting in a total cost avoidance of approximately over five years.” Id. Navy evaluators determined that “most products cost less under [DoW] ESA II, with discounts from DEOS pricing reaching for some items.” Id. Discounts on also make ESA II more cost-effective and “underscores a strategic financial advantage in leveraging” ESA II over DEOS. Id. The Navy further compared each offeror’s proposed BPA unit prices to their GSA prices as well. Id. at 1645. As part of its bid, Dell Federal submitted its FSS Authorized Price List. See AR Tab 15f. Notably, its Cloud-Based Services and Third-Party Product price lists did not list any items. See id. at 705, 712. Instead, Dell Federal would provide those lists “upon request.” Id. Dell Federal also attached a spreadsheet that contained 6,150 Microsoft products from its GSA Schedule and an associated “mapping” tool. AR Tabs 15g, 15h. The company further certified that all products appearing in Solicitation Attachment 2 are on Dell Federal’s GSA MAS contract. AR Tab 11 at 753. 5 On May 14, 2026, or two days after the submission of offers, the Navy awarded ESA II to Dell Federal. AR Tab 30 at 1648. Thereafter, the Navy published an ESA II BPA Ordering Guide. See generally AR Tab 34. The Ordering Guide contains language that states DoW “has officially transitioned to a centralized acquisition approach. All DoW Components are now required to procure Microsoft products and services exclusively through the ESI-provided catalog . . .” Id. at 1948. DoW Components then began informing Minburn that they received instructions to discontinue their orders on DEOS and to order from ESA II exclusively. In an email exchange with one customer, Minburn then learned about DoW’s December 2025 Memorandum that directed DoW’s policy change. Pl.’s Ex. J, ECF No. 1-1 at 1–2. II. PROCEDURAL HISTORY On June 11, 2026, or 10 days after DoW published its Ordering Guide, Minburn filed suit in this Court. See Compl., ECF No. 1. A day later, Dell Federal moved to intervene which the Court granted. See Order Granting Mot. to Intervene, ECF No. 16. Minburn then sought a temporary restraining order and preliminary injunction to enjoin defendant from placing orders under ESA II during this protest. See Pl.’s Mot. for TRO and Prelim. Inj., ECF No. 19. During a June 16, 2026, status conference, the parties represented “that they had reached an agreement in principle for a partial stay which would moot [Minburn’s] motion.” Scheduling Order, ECF No. 25. On June 22, 2026, the parties finalized their voluntary stay, in which the Navy agreed that it would not permit any classified orders under ESA II. Joint Status Report, ECF No. 26 at 1–2. 6 Defendant requested a decision from this Court by September 24, 2026 “because several additional classified orders may require renewal at the end of” that month. Id. at 2. In addition, the parties proposed a schedule of proceedings to resolve this matter on the administrative record which the Court adopted. See id. at 2–3; Scheduling Order, ECF No. 28. Under that schedule, defendant shared the administrative record on July 8, 2026. See Notice of File Sharing, ECF No. 30. Later that month, Minburn filed its first amended complaint and its motion for judgment on the administrative record. First Am. Compl., ECF No. 31; Pl.’s Mot. for J. on the Administrative R., ECF No. 32. The same day, Minburn also moved to supplement the administrative record and for the Court to take judicial notice. Pl.’s Mot. to Supp. the Administrative R. and for Judicial Notice, ECF No. 33. There, Minburn requested that the Court order defendant to produce Standard Form Modifications of Dell Federal’s GSA MAS contract that “reflect[ed] the addition of the Microsoft products specified in” Attachment 2 of the Solicitation.” Id. at 2. Minburn also requested that the Court take judicial notice of the fact that Dell Federal’s Price List on GSAAdvantage.com featured “only 11 of the hundreds of items listed in Solicitation Attachment 2.” Id. Under an expedited briefing schedule, the Navy and Dell Federal filed responsive briefing to Minburn’s evidentiary motion. See Def.’s Resp. to Mot. to Supp. the Administrative R., ECF No. 43; Intervenor’s Resp. to Mot. to Supp. the Administrative R., ECF No. 44. In its response brief, Dell Federal also moved to dismiss Counts II and III of Minburn’s complaint for failure to state a claim. See ECF No. 44 at 9–14. The Court also adjusted the merits briefing schedule to accommodate Minburn’s motion. See Scheduling Order, ECF No. 37. In a separate opinion, the Court granted-in-part and denied-in-part Minburn’s motion and 6 At the same time, the Navy and other DoW components could still place orders for non-classified products and services under ESA II. ECF No. 26 at 2. 6 denied Dell Federal’s motion to dismiss. See Minburn Tech. Grp. LLC v. United States, No. 26- 861, 2026 WL 2564252 (Fed. Cl. Aug. 17, 2026). In early August 2026, Minburn sought this Court’s leave to file a second amended complaint and amended motion for judgment on the administrative record. Pl.’s Mot. for Leave to File Am. Docs., ECF No. 38. The Court granted Minburn’s request, which filed its amended papers thereafter. See Second Am. Compl., ECF No. 41; Pl.’s Am. Mot. for J. on the Administrative R., ECF No. 42. 7 The Navy and Dell Federal filed their responses and cross- motions for judgment on the administrative record on August 17, 2026. 8 Def.’s Cross-Mot. for J. on the Administrative R., ECF No. 46; Intervenor’s Cross-Mot. for J. on the Administrative R., ECF No. 48. 9 Because the Navy could not produce Dell Federal’s Standard Form Modifications by Minburn’s next deadline, Minburn moved for a four-day enlargement of time which the Court granted. See Order Granting Mot. for Enlargement of Time, ECF No. 50. On August 27, 2026, defendant supplemented the administrative record. See Supp. to the AR, ECF No. 51. In early September, Minburn submitted its response and reply brief in support of its motion. Pl.’s Resp. & Reply Br., ECF No. 54. In its latest submission, Minburn withdrew Counts II and III to its complaint due to insufficient evidence. Id. at 26. Briefing concluded when defendant and Dell Federal filed their reply briefs. See Def.’s Reply Br., ECF No. 55; Intervenors Reply Br., ECF No. 56. The Court then held oral argument on September 16, 2026, for the parties to elaborate on their positions asserted in their briefs. See Oral Arg. Tr., ECF No. 59. III. LEGAL STANDARDS A. Scope of Review Under Bid Protest Actions. The Tucker Act confers jurisdiction on this Court “to render judgment on an action by an interested party objecting to . . . the award of a contract or any alleged violation of statute or regulation in connection with [a] procurement . . . ” 28 U.S.C. § 1491(b)(1). Interested parties are “actual or prospective bidders or offerors whose direct economic interest would be affected by the award of the contract or by failure to award the contract.” CS 321 East 2nd Investors, LLC v. United States, 178 Fed. Cl. 471, 483 (2025) (citing Percipient.AI v. United States, 153 F.4th 1226, 1235 (Fed. Cir. 2025)). This Court may award “any relief that [it] considers proper, including declaratory and injunctive relief.” 28 U.S.C. § 1491(b)(2). 7 All subsequent references to Minburn’s briefing will come from its amended motion for judgment on the administrative record, ECF No. 42. 8 The Navy and Dell Federal’s cross-motions were originally due on August 14, 2026. See ECF No. 37. However, the parties agreed to a three-day enlargement of time for their briefing due to Minburn’s motion for leave to file its amended documents. See ECF No. 38 at 1. The Court granted this three-day enlargement in its order granting Minburn’s motion. See Order Granting Mot. for Leave to File, ECF No. 39. 9 Dell Federal also attached a Memorandum of Law to support its motion. See Intervenor’s Mem. of L. in Support of Cross-Mot. for J. on the Administrative R., ECF No. 48-1. All subsequent references to Dell Federal’s arguments and positions will come from its Memorandum of Law. 7 Bid protests are reviewed under the Administrative Procedure Act (“APA”), 5 U.S.C. § 706. See 28 U.S.C. § 1491(b)(4). Under the APA, a court will set aside a federal agency’s decision that is “arbitrary and capricious, an abuse of discretion, or otherwise not in accordance with law.” 5 U.S.C. § 706(2)(A); see Bannum, Inc. v. United States, 404 F.3d 1346, 1351 (Fed. Cir. 2005); Galen Med. Assocs., Inc. v. United States, 369 F.3d 1324, 1329 (Fed. Cir. 2004). Agency action is arbitrary and capricious when “(1) the procurement official’s decision lacked a rational basis; or (2) the procurement procedure involved a violation of regulation or procedure.” Banknote Corp. of Am., Inc. v. United States, 365 F.3d 1345, 1351 (Fed. Cir. 2004). Such conduct lacks a rational basis when an agency failed to provide a “coherent and reasonable explanation of its exercise of discretion.” Id. When challenging an award on the second ground, a plaintiff must show “a clear and prejudicial violation of applicable statutes or regulations.” Id. Examples of arbitrary and capricious conduct include when a federal agency “entirely failed to consider an important aspect of the problem, offered an explanation for its decision that runs counter to the evidence before the agency, or [the decision] is so implausible that it could not be ascribed to a difference in view or the product of agency expertise.” Ala. Aircraft Indus., Inc.-Birmingham v. United States, 586 F.3d 1372, 1375 (Fed. Cir. 2009) (alteration in original) (quoting Motor Vehicle Mfrs. Ass’n v. State Farm Mut. Auto. Ins. Co., 463 U.S. 29, 43 (1983)). Courts must also find that the challenged agency action was prejudicial to the contractor to set aside agency action. Bannum, 404 F.3d at 1351. “The second step is always required before setting aside a bid award, regardless of whether the error identified at the first step was arbitrary and capricious action or, instead, a violation of law.” Sys. Stud. & Simulation, Inc. v. United States, 22 F.4th 994, 997 (Fed. Cir. 2021). A protester suffers prejudice upon a showing “that there was a substantial chance it would have received the contract award but for that error.” Alfa Laval Separation, Inc. v. United States, 175 F.3d 1365, 1367 (Fed. Cir. 1999) (citation omitted). This Court will “interfere with the government procurement process only in extremely limited circumstances.” CACI, Inc.-Fed. v. United States, 719 F.2d 1567, 1581 (Fed. Cir. 1981). In application, the “arbitrary and capricious standard . . . is highly deferential.” Advanced Data Concepts, Inc. v. United States, 216 F.3d 1054, 1058 (Fed. Cir. 2000); see Grumman Data Sys. Corp. v. Dalton, 88 F.3d 990, 1000 (Fed. Cir. 1996) (requiring more than de minimis errors to obtain relief). Disappointed bidders bear “a heavy burden of showing that the award decision had no rational basis.” Centech Grp., Inc. v. United States, 554 F.3d 1029, 1037 (Fed. Cir. 2009) (quoting Impresa Construzioni Geom. Domenico Garufi v. United States, 238 F.3d 1324, 1332 (Fed. Cir. 2001)). If there is “a reasonable basis for the agency’s action, the court should stay its hand even though it might, as an original proposition, have reached a different conclusion. . . .” Honeywell, Inc. v. United States, 870 F.2d 644, 648 (Fed. Cir. 1989). In sum, a court will not substitute its judgment for that of the agency. Bowman Transp., Inc. v. Ark.-Best Freight Sys., Inc., 419 U.S. 281, 285–86 (1974) (citing Citizens to Preserve Overton Park v. Volpe, 401 U.S. 402, 416 (1971)). B. Motion for Judgment on the Administrative Record. Under Rule 52.1 of the Court of Federal Claims (“RCFC”), “a motion for judgment on the administrative record examines whether the administrative body, given all the disputed and undisputed facts appearing in the record, acted in a manner that complied with the legal standards 8 governing the decision under review.” Supreme Foodservice GmbH v. United States, 109 Fed. Cl. 369, 382 (2013). Courts are required “to make factual findings from the record evidence as if it were conducting a trial on the record.” Bannum, 404 F.3d at 1356. Unlike a motion for summary judgment, genuine issues of material fact do not preclude the Court from entering judgment. Id. at 1355–56; see id. at 1356 (noting that unlike a motion under RCFC 56, “proceeding under RCFC [52.1] merely restricts the evidence to the agency record. . . .”). Thus, courts must determine whether a party satisfied its burden of proof based on the record. Palantir USG, Inc. v. United States, 904 F.3d 980, 989 (Fed Cir. 2018). C. Permanent Injunctions. Courts may grant injunctive relief upon a showing that “(1) the plaintiff has succeeded on the merits; (2) the plaintiff will suffer irreparable harm if the court withholds injunctive relief; (3) the balance of hardships to the respective parties favor[] the grant of injunctive relief; and (4) the public interest is served by a grant of injunctive relief.” Centech Grp., 554 F.3d at 1037 (citing PGBA, LLC v. United States, 389 F.3d 1219, 1228–29 (Fed. Cir. 2004)). While injunctive relief “is based on [the] four-factor test, a plaintiff’s failure to achieve success on the merits is dispositive.” Kingfisher Sys., Inc. v. United States, 145 Fed. Cl. 22, 34 (2019) (citing PGBA, 389 F.3d at 1228–29; Career Training Concepts, Inc. v. United States, 83 Fed. Cl. 215, 219 (2008)). IV. DISCUSSION A. The Navy’s Failure to Disclose Its Departmental-Wide Requirement for Exclusive, Mandatory Use of ESA II Violates CICA. Minburn alleges that the Navy violated the Competition in Contracting Act (“CICA”) by two related means. See ECF No. 42 at 18–24. First, the Navy failed to disclose its actual requirement that ESA II would serve as an exclusive vehicle for all DoW purchases of Microsoft products and services. Id. at 18–19. Next, Minburn claims that DoW’s undisclosed policy reflects a cardinal change which undermines fair competition. Id. at 19. The Navy argues that DFARS and language found in the Solicitation informed Minburn of ESA II’s mandatory nature. ECF No. 46 at 14–16. Moreover, Minburn did not identify a material change to ESA II and knew of its increased scope. Id. at 17–19. Dell Federal adds that Minburn failed to show that the Navy acted beyond its “sweeping scope” as provided by the Solicitation as well. ECF No. 48-1 at 14. CICA provides that agencies must “specify its needs and solicit bids or proposals in a manner designed to achieve full and open competition for procurement.” 41 U.S.C. § 3306(a)(1)(A). The statute also requires the government to “develop specifications in the manner necessary to obtain full and open competition with due regard to the nature of the property or services to be acquired.” 41 U.S.C. § 3306(a)(1)(C). Aligned with these principles, FSS BPAs must include “[s]ufficient detail about the need, such as scope of work.” 48 C.F.R. § 538.7104- 1(a)(1). However, CICA “does not prevent every modification of a contract by requiring a new bid procedure for every change.” AT&T Commc’ns, Inc. v. Wiltel, Inc., 1 F.3d 1201, 1205 (Fed. Cir. 1993). Instead, only modifications falling outside “the scope of the original competed contract” thwarts competition. Id. 9 Under the cardinal change doctrine, courts answer “whether modifications to a government contract were severe enough to constitute a breach of contract by the government.” Golden Mfg. Co. v. United States, 107 Fed. Cl. 264, 274 (2012) (citing Allied Materials & Equip. Co. v. United States, 569 F.2d 562, 563–64 (Ct. Cl. 1978)). Such changes occur when an agency “effects an alternation in the work so drastic that it effectively requires the contractor to perform duties materially different from those originally bargained for.” Id. (citation omitted). This Circuit recognizes the cardinal change doctrine in bid protests as well. Id. (citing AT&T Commc’ns, 1 F.3d at 1205). Courts consider in that context “whether Government modifications changed the contract enough to circumvent the statutory requirement of competition.” AT&T Commc’ns, 1 F.3d at 1205. Making this determination turns on “the scope of the entire original procurement in comparison to the scope of the contract as modified.” Id. “Because every situation in which parties enter into a contractual relationship is unique, there is no definitive test for determining whether a change is beyond the scope of a particular contract.” Ian, Evan & Alexander Corp. v. United States, 136 Fed. Cl. 390, 416 (2018) (quoting Keeter Trading Co. v. United States, 79 Fed. Cl. 243, 260 (2007)). Courts consider the “changes in the type of work, performance period, and” cost difference between the original and modified contracts. CCL, Inc. v. United States, 39 Fed. Cl. 780, 792 (1997) (citation omitted). Another “important factor in determining the scope of the original competition” includes if the solicitation “adequately advised offerors of the potential” types of changes that could occur. AT&T Commc’ns, 1 F.3d at 1207. Courts should also evaluate “whether the modification is of a nature which potential offerors would reasonably have anticipated.” Id. “Thus, a broad original competition may validate a broader range of later modifications without further bid procedures.” Id. Minburn’s protest does not challenge the substantive aspects of ESA II, but how DoW Components may purchase their products and services. See ECF No. 42 at 21–22 (citing AR Tab 11 at 560). The Navy and Dell Federal interpret Minburn’s alleged “status quo” as what occurred before ESA II. See ECF No. 46 at 17; ECF No. 48-1 at 17–18. There, DoW instructed its Components to use ESA I for on-premises licenses and DEOS for cloud-based licenses. See AR Tab 34 at 1948, Tab 39 at 2192. Acting together, both contract vehicles satisfied DoW’s enterprise requirements. AR Tab 39 at 2192. The Court agrees that DoW’s 2021 memorandum, which created this dynamic, did not grant department Components with unbridled discretion. Rather, it directed Components to place orders under specific vehicles with certain exceptions. See id. Nonetheless, Minburn “challenges DoW’s mandate of exclusive use” that the Navy otherwise failed to disclose. ECF No. 54 at 8 (emphasis in original). At the outset, the Solicitation lacks a clear and unambiguous statement of the Navy’s policy for exclusive use. Nowhere does the Navy state in plain English that ESA II mandates exclusive participation with no exceptions. When addressing Minburn’s claim, the parties selected language from different materials to support their theories. These statements contradict each other at times and include imprecise wording. In this case, a review of these materials is necessary before proceeding to Minburn’s two theories of relief. To start, ESA II describes itself as a “comprehensive” BPA that “will enable customers across the DoW to procure Microsoft software licenses.” AR Tab 11 at 573. Licenses under ESA II would “include all Microsoft software used on all DoD networks.” Id. at 549. As contemplated 10 by the Scope of Use provision, government entities “may transition into the Agreement at any time following the expiration of their own Agreement.” Id. (emphasis added). The Solicitation also recognizes in a BPA Transition section a scenario in which DEOS customers would “decide” to transition to ESA II. See id. at 559–60. In that situation, “the Contractor shall ensure the transition is made with no penalty to the government.” Id. at 560. The Solicitation further dictates that DoW’s “ESI goals can only be realized if the Government and the Contractor direct appropriate sales through this BPA.” Id. (emphasis added). To prevent “sales leakage,” the contractor must “enforce the policy that this BPA is mandatory for consideration in accordance with DFARS Subpart 208.74 for the products within it.” Id. Under DFARS, agencies shall “fulfill requirements for commercial software and commercial software services” through the ESI Initiative. 48 C.F.R. § 208.7402(a). “ESI promotes the use” of ESAs to “allow DoD to obtain favorable terms and pricing for commercial software and commercial software services.” Id. Acquisition procedures further dictate that agencies should determine if their ordering needs are within the DoD’s inventory. DFARS Procedures, Guidance, and Information (“PGI”) 208.7403(1). If not, officials must check if “the commercial software or related services are on an ESA.” DFARS PGI 208.7403(3). Contracting officials must then determine if products and services under an ESA offer the best value to the government. Id. “If existing ESAs do not represent the best value to the Government,” then a software product manager “shall be given an opportunity to provide the same or a better value to the Government under the ESAs before the contracting officer . . . may continue with alternate acquisition methods.” DFARS PGI 208.7403(5). DFARS further allows contracting officers to purchase from other contracting vehicles if a product does not appear in DoD’s inventory or an ESA. DFARS PGI 208.7403(2). In its December 2025 memorandum, which was not available to the public or offerors, DoW ordered its components to “align their current and future Microsoft agreements to the greatest extent practicable” to the forthcoming ESA II. AR Tab 39 at 2225. DoW also wrote that all Components “are expected to procure Microsoft products exclusively through the ESI-provided catalog.” Id. In its catalog, DoW represented that on June 1, 2026, “the Department has officially transitioned to a centralized acquisition approach. All DoW Components are now required to procure Microsoft products and services exclusively” through ESA II. AR Tab 34 at 1948. And “[w]hen an Enterprise Software Initiative [] is in place, this is a mandatory source of supply for the DoW.” Id. at 1947. After careful consideration, the Court finds that DoW’s 2025 Memorandum and ESA II Ordering Guide do not constitute cardinal changes. Many cases raising the doctrine addressed formal modifications regarding the nature of the work to be performed. See AT&T Commc’ns, 1 F.3d at 1204 (entering into bilateral modification by adding new type of dedicated transmission service); Golden Mfg., 107 Fed. Cl. at 276 (analyzing whether Amendment 15 to procurement qualified as a cardinal change); Am. Apparel, Inc. v. United States, 108 Fed. Cl. 11, 34 (2012) (concerning additional products added to solicitation); IgniteAction JV, LLC v. United States, 174 Fed. Cl. 62, 66 (2024); Celerapro, LLC v. United States, 168 Fed. Cl. 408, 433 (2023); CCL, Inc, 39 Fed. Cl. at 792. 10 Those situations do not include which customers could potentially place 10 Dell Federal and the Navy claim that no differences exist between the Solicitation and award. ECF No. 46 at 15–16; ECF No. 48-1 at 18 (“No change (much less a substantial change) has occurred.”). Indeed, 11 orders under a contract vehicle. As another court commented, “if the function or nature of work, as changed, remains generally the same, the change or changes will be held to fall wi