What This Bill Does
This bill would place a hard ceiling of $750 billion on the amount authorized to be appropriated for the national defense budget for fiscal year 2027. In practical terms, it would limit how much Congress can approve for defense activities, including the Pentagon, military operations, procurement, and related national security programs. The measure would affect the Department of Defense, defense contractors, service members, and taxpayers through the size of the federal defense budget.
- Sets a $750,000,000,000 cap on authorized defense spending for fiscal year 2027.
- Applies to the national defense budget, including Pentagon-related funding.
- Would limit how much Congress can authorize for military programs and operations.
- Could affect defense procurement, personnel costs, and readiness priorities.
- Would shape the annual appropriations process for the armed forces.
Who This Bill Affects
For a typical American, this bill would mainly affect you indirectly through the federal budget and the scope of national defense spending. If enacted, it would hold FY2027 defense authorization to $750 billion, which could slow growth in Pentagon programs and potentially reduce pressure on future deficits, but it could also tighten funding for military pay, equipment, and operations. Most people would not see an immediate personal change, though defense workers, service members, and communities dependent on military spending could feel the effects more directly.
See how this bill affects you — sign in for a personalized analysisWho Supports & Opposes This
- Fiscal conservatives and deficit hawks They would argue that a spending cap is necessary to slow the growth of federal deficits and force the Pentagon to justify its largest programs. A firm ceiling can encourage reallocation away from low-priority spending and toward more disciplined budgeting.
- Taxpayers concerned about federal spending They would see the cap as a way to prevent automatic growth in defense spending without clear accountability. In their view, large Pentagon budgets should face the same scrutiny as domestic programs.
- Some anti-war or non-interventionist voters They would argue that capping defense authorization helps limit military overextension and reduces incentives for new weapons programs or foreign commitments. A lower cap can signal a shift toward restraint in national security policy.
- Military leaders and readiness advocates They would argue that a rigid cap can make it harder to pay for inflation, troop compensation, maintenance, and modernization needs. If threats rise, a fixed ceiling may leave too little flexibility to respond quickly.
- Defense industry workers and contractors They would worry that a lower ceiling could delay or cancel procurement contracts, research projects, and production lines. That could affect jobs and regional economies tied to defense manufacturing.
- Lawmakers focused on national security They would contend that budgeting should be driven by strategy and threat conditions, not an upfront dollar limit. In their view, underfunding defense could weaken deterrence and readiness.
Key Implications
-
““cap the amount authorized to be appropriated... at $750,000,000,000””
This is the bill’s central limit. It would set a hard ceiling on what Congress could authorize for defense in fiscal year 2027, which would influence all downstream military funding decisions.
-
““national defense budget for fiscal year 2027””
The cap is aimed at one specific budget year, so it would shape the upcoming annual defense funding cycle rather than permanently changing defense law.
-
““authorized to be appropriated””
This affects the authorization ceiling Congress can approve, which helps determine the upper bound for later appropriations and signals how much defense spending is politically acceptable.
Latest Status
June 16, 2026
Read twice and referred to the Committee on Armed Services.
Related Bills
Take Action
Get more from BillBoard
Free tools to understand, respond to, and track this bill.
Ask AI about this billData sourced from api.congress.gov.