The House of Representatives passed the fiscal year 2027 National Defense Authorization Act on a narrow 216–212 vote Wednesday, advancing a $1.15 trillion defense bill that includes a provision critics from both parties warned could compromise American sovereignty and permanently entangle U.S. military technology with that of a foreign nation. The provision in question, Section 219, would establish a permanent United States–Israel Defense Technology Cooperation Initiative—and despite a bipartisan push to strip it from the bill, lawmakers were denied a separate vote to do so.

What Section 219 Actually Does

Section 219 of the FY2027 NDAA directs the Secretary of Defense to create a formal, institutionalized initiative aimed at synchronizing, expanding, and accelerating defense cooperation between the United States and Israel. According to the bill’s language, the initiative would identify “jointly developed or Israeli-origin technologies with operational utility” for potential integration into U.S. systems and programs of record, facilitate the transition of those technologies into U.S. procurement and acquisition pathways, and establish frameworks for joint ventures, licensing agreements, and U.S.-based coproduction or manufacturing partnerships with Israeli industry.

The provision also calls for the Secretary of Defense to designate a permanent Pentagon executive agent responsible for coordinating bilateral defense research, development, testing, evaluation, and industrial cooperation. Identified areas of collaboration include counter-unmanned aerial systems, subterranean warfare, air and missile defense systems such as Iron Dome, David’s Sling, and Arrow 3, as well as emerging domains like artificial intelligence and directed energy weapons.

Annual congressional reporting requirements are included in the measure, framed as a transparency mechanism to track implementation of the program.

Massie’s Warning: Sovereignty, Flexibility, and Long-Term Risk

Rep. Thomas Massie, R-Ky., was among the most vocal opponents of the provision. One of seven Republicans to break with party lines and vote against the NDAA, Massie argued that embedding this kind of bilateral arrangement into statute carries risks that extend beyond any single administration.

“Codifying the integration of our military technology and supply chains with those of any other country is dangerous,” Massie said, according to reporting by The Intercept. He told the outlet ahead of the vote that institutionalizing the relationship would create long-term national security risks and that doing so with Israel would produce “a lopsided arrangement” in which American national security is unnecessarily compromised.

Massie also raised a structural concern about executive power and future flexibility: “Enshrining this broad agreement and the permanent position it creates in legislation removes the flexibility of future Presidents to withdraw from such an arrangement,” he said. By codifying the initiative in statute rather than leaving it as an executive arrangement, Congress would be binding future administrations to a partnership that could prove difficult to exit.

Massie sought to remove the provision alongside Rep. Ro Khanna, D-Calif., in a rare bipartisan alliance on a national security question. Rep. Alexandria Ocasio-Cortez, D-N.Y., described the provision as “an existential threat to American sovereignty and democracy” in a statement on social media.

A Narrow, Party-Line Vote—With Exceptions

The final vote breakdown illustrated how charged the issue had become. The NDAA passed 216–212, largely along party lines. Seven Republicans voted against it: Massie, along with Reps. Josh Brecheen of Oklahoma, Tim Burchett of Tennessee, Eli Crane of Arizona, Harriet Hageman of Wyoming, Anna Paulina Luna of Florida, and Chip Roy of Texas. Six Democrats broke from their caucus to vote in favor: Reps. Henry Cuellar of Texas, Don Davis of North Carolina, Jared Golden of Maine, Vicente Gonzalez of Texas, Adam Gray of California, and Marie Gluesenkamp Perez of Washington.

The narrow margin underscores that the legislation—the largest defense authorization bill in the nation’s history at $1.15 trillion—was not a foregone conclusion, and that the Israel technology provision generated genuine friction even within the majority party.

Proponents Frame It as Strategic Necessity

Supporters of Section 219 have pushed back firmly against the sovereignty arguments. The Jewish Institute for National Security of America published an analysis arguing that the initiative “presents great potential to bolster the already robust military relationship between both nations,” pointing to years of successful collaboration on missile defense and counter-drone technologies.

The JINSA analysis noted the 2026 joint U.S.-Israeli military operations against Iran, designated Epic Fury and Roaring Lion, as evidence of how effective the two nations can be when operating together. Proponents argue the initiative would allow the U.S. to more systematically access Israeli defense innovations—particularly lessons learned since the October 7, 2023 attacks—rather than leaving potential advantages on the table.

The analysis also pushed back on characterizations of the provision as a full military “integration,” arguing that no specific cooperation on any individual capability is mandated and that the initiative is structured to protect sensitive U.S. technology and national security interests.

The Structural Question Lawmakers Left Unanswered

What the floor debate ultimately failed to resolve is the question Massie placed at the center of his opposition: not whether U.S.-Israel cooperation is beneficial in a given moment, but whether that cooperation should be permanently enshrined in statute in a way that constrains future administrations and deepens supply chain interdependencies with a foreign nation.

Defense alliances and technology-sharing arrangements between the U.S. and its partners are not new. What critics argue is qualitatively different here is the permanence of the executive agent position being created, the breadth of the initiative’s mandate across research, development, procurement, acquisition, joint ventures, and industrial partnerships, and the statutory nature of the commitment itself.

The bill now moves forward with Section 219 intact. Whether the Senate’s companion provision, designated Section 1217 in its version of the NDAA, survives conference negotiations will determine the final shape of the initiative. The Senate version similarly directs the Defense Secretary to create the cooperation initiative but does not specify the same executive agent leadership structure as the House bill.

What Comes Next

The FY2027 NDAA still faces a Senate vote and a conference process to reconcile differences between the two chambers’ versions before it can reach the President’s desk. The fate of Section 219—whether it survives in its House form, is modified to reflect the Senate’s approach, or faces further opposition—remains an open question.

What Wednesday’s vote confirmed is that a bipartisan coalition of lawmakers raised substantive objections to permanently institutionalizing this arrangement, and that those objections were procedurally sidelined rather than debated and voted on as a standalone question. For those watching how the architecture of U.S. foreign military relationships gets quietly built into law, that procedural move may be as significant as the provision itself.

This article draws on reporting from The Intercept and analysis published by the Jewish Institute for National Security of America (JINSA).