Walz Pulls Minnesota’s National Guard Out of DC Early, Says Trump’s Task Force Broke the Deal

Minnesota Gov. Tim Walz is withdrawing his state’s National Guard troops from Washington, D.C. ahead of schedule after members were seen conducting presence patrols in neighborhoods far from the National Mall, beyond the limited scope he says he authorized. Walz had sent guard members to D.C. ahead of the America 250 celebrations under orders restricting them to assisting with events near the national monuments; the troops had originally been assigned to the city until July 23 [1]. Trump deployed the National Guard to Washington in August 2025 under a federal Joint Task Force framed around fighting crime and “beautifying” the city, even though crime was already trending down at the time. Democratic governors from Kentucky, North Carolina, Michigan, Maryland and Hawaii sent troops to D.C. under similar limited orders in recent weeks — the first time Democratic-led states had joined the deployment — and Michigan Gov. Gretchen Whitmer has threatened to pull her state’s guard if reports continue of troops being used beyond their agreed scope [1]. The deployment now costs upward of $3 million per day, according to a Congressional Budget Office estimate [1].

Why It Sucks:

Trump Administration & Guard Deployment Supporters

• Pulling troops mid-mission undercuts the task force. Supporters argue that Democratic governors agreeing to send Guard members and then yanking them early over a scope dispute disrupts a public safety operation already underway [1].
• This looks like politics, not principle. Backers of the deployment contend the timing — during a high-profile national celebration — makes the withdrawal read as a political statement against Trump rather than a genuine operational concern [1].
• It sets a precedent for other states to bail. With Michigan already threatening to follow Minnesota’s lead, supporters worry the entire multi-state Guard arrangement in the capital could unravel [1].

Governor Walz & Democratic Governors

• The mission scope was violated without warning. Walz says his troops were explicitly ordered to help only with America 250 events near the monuments, not to patrol residential neighborhoods, and pulled them out once that line was crossed [1].
• Guardsmen became tools in someone else’s agenda. Democratic governors argue their troops were sent for a narrow ceremonial purpose and instead got folded into Trump’s broader, indefinite federal policing presence in the city [1].
• Trust in future requests is now damaged. With Whitmer threatening to follow suit, Democratic governors say the episode makes them warier of ever loaning Guard troops to a federal mission they don’t fully control [1].

DC Residents & Local Government

• Neighborhoods became a testing ground without their input. Residents in areas far from the National Mall found out-of-state Guard troops patrolling their streets despite having no say in the deployment’s scope or duration [1].
• The city bears the cost of a fight it didn’t start. At an estimated $3 million a day, D.C. hosts a massive multi-state security operation shaped entirely by disputes between the White House and other states’ governors [1].
• Uncertainty over troop presence keeps shifting. With guard units coming and going based on political disputes among governors and the administration, District residents are left without a stable, predictable picture of who is patrolling their own neighborhoods [1].

Sources & Citations:

[1] NPR: Minnesota is pulling troops early from D.C., as pressure grows on Michigan
[2] ClickOnDetroit: Democratic-led states face backlash over National Guard deployments in Washington