Minnesota’s Democratic-Farmer-Labor Party is turning the state’s data center boom into a defining political fight, and the message from DFL lawmakers is blunt: the rapid buildout of AI infrastructure has outrun the rules meant to govern it. The framing, echoed this week across outlets including St. Cloud Live, AIP.org and TechRadar, treats data centers the way an earlier generation of state legislators treated strip mining or factory runoff — a powerful economic force that needs guardrails before it reshapes communities on its own terms.
The debate is no longer theoretical. Minnesota’s 2025 Legislature already rewrote the tax and permitting rules that apply to large-scale data centers, and a new round of 2026 DFL resolutions is pushing further, with grassroots party votes showing strong appetite for even tighter controls. For an industry used to courting state governments with jobs and tax-revenue promises, Minnesota is emerging as a test case for what happens when that courtship meets organized political pushback.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Why Data Centers Became a DFL Flashpoint
Data centers used to be a bipartisan economic-development win: tax abatements, construction jobs, a new line item on the local tax base. That calculus has shifted as hyperscale facilities built for AI workloads have grown far larger and far more power-hungry than the server farms of a decade ago. Minnesota DFL lawmakers argue that scale has changed the politics, not just the economics.
State Sen. Jen McEwen, DFL-Duluth, has made the grid math central to her argument for slowing new approvals. “If every currently proposed data center in Minnesota is built, they would collectively use more electricity than every household in the state combined,” she said, according to the Minnesota Women’s Press. That comparison, drawn from legislative testimony, is the kind of figure that turns an abstract infrastructure debate into something a voter can picture: their own electric bill, their own substation, their own water table.
McEwen also pointed to the volume of testimony lawmakers have already fielded. “We have heard testimony about the potential impacts these hyperscale data centers could have on our communities, our energy grid, and our natural resources,” she said, per the same report. That testimony record is now the evidentiary backbone DFL legislators cite when they introduce new oversight bills.
What Minnesota’s 2025 Law Already Changed
Before anyone talks about a moratorium, it helps to understand what state law already does. The 2025 Minnesota Legislature repealed the sales-tax exemption that had applied to electricity used by data centers, a change that strips away one of the financial incentives that made Minnesota attractive to hyperscale developers in the first place. Lawmakers paired that repeal with a new annual fee for large-scale data centers tied to water usage, plus strengthened environmental-permitting requirements that give state agencies more leverage over siting decisions.
Those three moves — tax, fee, permitting — form the baseline that 2026 resolutions are now built on top of. None of them amount to a moratorium. All three signal that the era of data centers getting a blank check from state government is over.
| Policy Area | Status Before 2025 | Change Under 2025 Minnesota Law |
|---|---|---|
| Electricity sales tax | Exemption applied to qualifying data center electricity purchases | Exemption repealed |
| Water usage | No dedicated data center fee | New annual fee tied to water usage for large-scale facilities |
| Environmental permitting | Standard state review process | Strengthened permitting requirements |
| Grid infrastructure | No data-center-specific transmission mandate | DFL resolutions flag major transmission expansions tied to hyperscale buildout |
| Hardware lifecycle | Not addressed in state policy debate | Resolutions note equipment turnover of 2 to 5 years as a planning factor |
The DFL Platform Vote: 64% for a Moratorium, 76% for Tighter Rules
The clearest signal of where rank-and-file DFL sentiment sits came out of a party platform-ballot gathering, where members voted on competing data center resolutions. A resolution calling for a statewide moratorium on new data centers drew support from 64% of those casting ballots. A separate resolution calling for tighter regulation, short of an outright pause, drew support from 76%.
That gap matters. It suggests the DFL base is more unified around the idea that data centers need firmer rules than it is around the more drastic step of freezing new construction outright. For developers and utilities watching Minnesota as a bellwether, the 76% number is arguably the more important one: it shows that tighter regulation, not a moratorium, is the position with the broadest coalition behind it inside the party actually writing the state’s laws.
| Resolution | Core Ask | Platform-Ballot Support |
|---|---|---|
| Statewide data center moratorium | Pause new large-scale data center permitting | 64% |
| Tighter data center regulation | Strengthen environmental review, transparency and siting standards | 76% |
The 2026 Senate District 40 Resolution
Beyond the statewide platform vote, individual DFL Senate districts are drafting their own resolutions, and Senate District 40’s 2026 resolution is one of the more detailed examples. It calls for protecting communities from data centers through environmental review, public transparency, siting standards, and enforceable climate-related requirements, according to the resolution packet published by SD40 DFL.
The resolution also flags two operational realities that rarely make it into corporate press releases: hyperscale data centers can require major electrical-transmission expansions to connect to the grid, and the computing equipment inside them may need replacing every two to five years. Both points reframe data centers as recurring infrastructure obligations rather than one-time capital projects, which changes how a state should think about permitting them in the first place.
Rep. Liebling’s “Law and Order” Framing
No single line captures the DFL’s current posture better than a statement attributed to Rep. Liebling in a Minnesota Senate DFL article: “Our laws need to address growing safety concerns around data centers and AI, and quickly.” It is the kind of urgency usually reserved for public-safety legislation, not zoning disputes, and that is precisely the point DFL lawmakers are trying to make.
Liebling also tied the push for new rules to a trust deficit, arguing that a lack of transparency from “billionaires and corporations” has left community members nervous about what is actually being built near them, how much power and water it will draw, and who gets to ask questions before construction starts. That transparency complaint runs through nearly every DFL data center resolution filed in 2026, whether the specific ask is a moratorium, a fee increase, or a new permitting hurdle.
“Not One Single Resident”: The Transparency Complaint
State Sen. Erin Maye Quade, DFL-Apple Valley, has turned that transparency complaint into one of the sharpest lines of the debate. Describing a proposed Rosemount data center kept out of public discussion through nondisclosure agreements, she said: “Not one single resident had the opportunity to go before the city council and ask questions.”
Maye Quade has been equally direct about where she places blame. “I take issue with Big Tech,” she said, framing her objection around both the tax breaks data center developers have historically received and the speed at which AI itself is being folded into daily life without public input. “The emergence and quick integration of AI against our will into our everyday lives is deeply problematic,” she added, according to the Minnesota Women’s Press report cited above.
Those comments point to something broader than a single Rosemount project. DFL lawmakers are increasingly treating NDA-shielded site-selection deals as a governance problem in their own right, separate from whatever environmental or grid impacts a given facility eventually produces.
Grid Strain and the Transmission Problem
Minnesota’s fight is a local chapter of a national story about AI infrastructure outpacing grid capacity. Utilities across the country have warned that hyperscale demand is forcing transmission buildouts years ahead of schedule, and Minnesota resolutions explicitly cite major electrical-transmission expansions as a consequence of hyperscale data center approvals. That is a different kind of cost than a tax bill or a water fee: it is a multi-year capital commitment that ends up on ratepayers’ bills long after a single facility’s construction is finished.
The equipment-refresh detail in the SD40 resolution adds another layer. If servers and accelerators inside these facilities turn over every two to five years, the state is not just approving a building, it is approving a recurring cycle of industrial activity, trucking, and e-waste that will repeat for as long as the facility operates. DFL lawmakers argue that siting standards should account for that lifecycle, not just the initial construction footprint.
Market Impact: What Tighter Rules Mean for Hyperscalers
For the cloud and AI companies building out capacity in Minnesota, the practical effect of 2025’s law and 2026’s resolutions is a shift in the cost structure of doing business in the state. Losing the electricity sales-tax exemption raises operating costs on power, which is often the single largest recurring expense for a hyperscale facility. A water-usage fee adds a second recurring cost tied directly to cooling-system design choices. Strengthened permitting adds time, which in an industry racing to bring AI capacity online is its own kind of cost.
None of that necessarily stops development, but it does change the math that site-selection teams run when comparing Minnesota against states with friendlier tax treatment. It also sets a template other state legislatures can borrow from: a tax repeal here, a water fee there, a permitting requirement layered on top, each individually modest but collectively a meaningful shift in who bears the cost of AI infrastructure.
Competitive Comparison: How Other States Are Handling the Same Fight
Minnesota is not operating in isolation. Data center siting and energy-cost disputes have become a recurring feature of state legislative sessions nationwide as grid operators and utilities grapple with surging demand from AI buildouts. Louisiana has seen its own moratorium push gain traction as power fights between utilities, Meta and Amazon have escalated. At the federal level, FERC’s recent data center registry decision for the PJM grid region reflects the same underlying tension: regulators trying to get visibility into hyperscale demand before it destabilizes the broader grid, rather than after.
Local zoning fights are following a similar arc outside Minnesota too, with communities in Pennsylvania’s Lehigh Valley region pushing through their own data center siting rules after contentious local votes. The pattern across these cases is consistent: communities and legislators feel they are being asked to approve infrastructure decisions after the fact rather than shaping them from the start, and they are increasingly unwilling to accept that position.
Historical Context: From Incentives to Scrutiny
It is worth remembering how recently data centers were treated as uncomplicated economic wins. Tax abatements and sales-tax exemptions for data center equipment and electricity were, for years, the default tool states used to attract this kind of investment, Minnesota included. The 2025 repeal of the electricity sales-tax exemption marks a genuine reversal of that posture, not a minor adjustment.
What changed is scale and visibility. AI-driven demand pushed individual facilities from tens of megawatts into the hundreds, and water and power consumption figures that once stayed buried in utility filings are now showing up in campaign materials and DFL resolutions. Local reporting outlets, including MinnPost, have described data centers as shaping up to be one of the defining issues of Minnesota’s next election cycle, a label that would have sounded far-fetched for this sector even five years ago.
Inside the Listening Sessions
DFL legislators have leaned heavily on community listening sessions to build the case for new rules. One such session with Rochester-area residents, recapped by Minnesota Senate DFL, became a venue for lawmakers to hear directly from residents living near proposed or existing facilities about noise, water draw, and the pace of approvals. These sessions feed directly into the resolution language that shows up months later at district conventions and the statewide platform vote.
Community organizing groups have mirrored that approach outside the legislature itself. Reporting from Twin City Telegraph has tracked how neighborhood associations and environmental groups across the Twin Cities metro and greater Minnesota have mobilized around specific proposed sites, turning what might have been a handful of county zoning hearings into a statewide political movement.
How the Resolution Votes Were Scored
District-level DFL organizations have also started publishing their own scoring of resolutions ahead of statewide votes, a process meant to give delegates a clearer sense of which proposals have momentum before they reach the floor. A resolutions packet with percentage scoring published by DFL Senate District 57 is an example of that groundwork, showing how granular the party’s internal vetting of data center policy has become at the district level before issues ever reach a statewide ballot.
That level of procedural detail might seem like inside baseball, but it explains why the 64% and 76% platform numbers carry real weight. These are not snap reactions to a news cycle. They are the output of a multi-month process of district resolutions, scoring, and debate that funnels into a single statewide vote.
Predictions: Where This Goes Next
Several trajectories look likely heading into 2027 budgeting and legislative sessions:
- Expect additional fee or tax proposals targeting data center water and electricity use to surface in the next Minnesota legislative session, building on the 2025 repeal rather than replacing it.
- A full statewide moratorium looks less likely to pass than targeted regulation, given the 76% versus 64% gap in platform-ballot support for the two approaches.
- Transparency requirements, including limits on NDA-shielded site selection, are likely to get renewed attention after Sen. Maye Quade’s comments about the Rosemount process.
- Other states watching Minnesota’s 2025 law, including those weighing their own moratorium bills, will likely use it as a reference point for tax-and-fee-based regulation as an alternative to an outright pause.
- Federal attention to grid strain, mirrored in FERC’s PJM data center registry move, will keep pressure on state legislatures to show they are addressing transmission costs tied to hyperscale demand.
What Developers Should Watch For
Companies with active or planned Minnesota projects should treat 2026 as a planning inflection point rather than a one-off news cycle. The combination of a repealed tax exemption, a new water-usage fee, and strengthened permitting already changes the underwriting math for any facility still in the pipeline. Add the SD40 resolution’s explicit focus on transmission expansion and equipment lifecycle, and it is clear state policymakers want visibility into costs that used to stay internal to a company’s own capital planning.
The transparency push matters just as much as the dollar figures. Projects structured around NDAs that keep city councils and residents in the dark, the kind of arrangement Sen. Maye Quade criticized in Rosemount, are now a political liability in Minnesota in a way they were not two years ago. Developers that get ahead of disclosure expectations, rather than waiting for a mandate, are likely to face less friction at the local level.
Frequently Asked Questions
What did Minnesota’s 2025 data center law actually change?
It repealed the electricity sales-tax exemption for qualifying data centers, created a new annual fee for large-scale facilities tied to water usage, and strengthened environmental-permitting requirements.
Did the Minnesota DFL vote for a data center moratorium?
At a DFL platform-ballot gathering, a statewide moratorium resolution received 64% support, while a separate resolution for tighter regulation short of a moratorium received 76% support. Neither figure represents an enacted state law on its own.
Who are the key DFL legislators pushing data center regulation?
Rep. Liebling has framed the issue around safety and corporate transparency, while state Sens. Jen McEwen (DFL-Duluth) and Erin Maye Quade (DFL-Apple Valley) have both pushed for a moratorium and criticized NDA-shielded site-selection deals.
What is the Senate District 40 data center resolution?
It is a 2026 DFL resolution calling for protecting communities from data centers through environmental review, public transparency, siting standards, and enforceable climate-related requirements.
Why do DFL lawmakers mention transmission lines and equipment lifecycles?
Resolutions note that hyperscale data centers can require major electrical-transmission expansions and that computing equipment inside them may be replaced every two to five years, framing data centers as recurring infrastructure obligations rather than one-time projects.
Is Minnesota the only state regulating data centers this way?
No. States including Louisiana have advanced their own moratorium proposals, and federal regulators at FERC have taken steps like a new data center registry for the PJM grid region to track hyperscale demand.
How does this affect companies already building data centers in Minnesota?
They face higher operating costs from the lost tax exemption and new water fee, longer permitting timelines, and growing political pressure for more transparent site-selection processes.
What should readers expect next?
Additional fee and transparency proposals are likely in the next Minnesota legislative session, with targeted regulation remaining more politically viable than an outright moratorium based on current platform-ballot support.
Related Coverage
- Kinesis vs Event Hubs vs Pub/Sub: 12x Retention Gap [2026]
- Eletronet Cuts Maxx Conectado Latency to 7ms With IP Transit Deal [2026]
- Yandex Bots Fell to 0.4%, Drone Link Still Unproven [2026]
- Yandex Go Down in 7 Cities as Drones Hit Payments [2026]
- Build a Game Streaming Service: AWS Setup in 13 Steps [2026]
