Are Moratoriums Undermining Data Center Growth?

When a locality slaps a moratorium on data center development, officials often frame it as a pause — a reasonable timeout to assess infrastructure strain, water usage, or community impact. Developers hear something different. They hear: *go build somewhere else.*

That distinction matters more than most local governments seem to realize.

The data center market is moving at a velocity that doesn't accommodate indefinite waiting. Hyperscalers like Microsoft, Google, and Amazon have capital deployment timelines measured in quarters, not years. When a jurisdiction makes itself unpredictable, it doesn't get pushed to the back of the line — it gets removed from the list entirely. A moratorium sold as temporary can produce consequences that are permanent.

What a Moratorium Actually Does to a Market

A data center moratorium is a legislative or regulatory action that halts the permitting, approval, or construction of new data center facilities within a defined jurisdiction. On paper, the rationale is often sympathetic: grid stress, water scarcity, strained municipal services, or community pushback over industrial-scale development moving into suburban or rural areas.

In practice, moratoriums have emerged across multiple localities as the data center buildout — driven by AI compute demand — has accelerated faster than local infrastructure planning cycles. Northern Virginia, the world's largest data center market, has seen surrounding counties grapple with exactly this tension. Loudoun County, which hosts a massive concentration of existing facilities, has faced repeated debates over how much further development should proceed. Other regions across the Sun Belt and the Pacific Northwest have encountered similar friction as developers scout new markets.

The problem isn't that communities want to pause and think. That instinct is understandable. The problem is that the market doesn't pause with them.

The Economic Case Against Moratoriums

Data centers are, by any objective measure, extraordinarily valuable tenants. A single hyperscale facility — think 100MW or larger — can generate hundreds of millions of dollars in local tax revenue over its operational lifetime. They employ construction workers during the build phase, and while operational headcounts are leaner than traditional industrial facilities, the jobs that exist are high-skill and high-wage. The indirect economic activity — from engineering firms to fiber contractors to facility management services — compounds that value further.

When a moratorium pushes a project to an adjacent county or a competing state, that entire economic chain moves with it.

Consider what that means in competitive terms. Data center developers evaluating a 200MW campus have options. They're simultaneously looking at sites in three or four states, often with dedicated economic development teams making active pitches. A moratorium in one jurisdiction doesn't create a delay in the broader project timeline — it just reroutes it. The facility gets built. The jobs get created. The tax base grows. Just not for the locality that decided to pause.

The revenue loss isn't hypothetical. Virginia's data center sector alone generates over $1 billion annually in sales tax revenue — a figure that exists precisely because the state has historically maintained a development-friendly regulatory environment. Localities that undermine that environment don't just lose one project; they signal unreliability to an industry that treats regulatory predictability as a core site-selection criterion.

What Developers Are Actually Facing

For developers already in the pipeline when a moratorium hits, the situation moves from inconvenient to genuinely damaging. Carrying costs on land already acquired don't stop. Contracts with equipment suppliers and engineering firms have their own timelines and penalties. Debt service doesn't pause while a city council deliberates.

The longer a moratorium extends, the more it functions not as a pause but as a de facto denial.

There's also a compliance complexity layer that doesn't get enough attention. Moratoriums rarely arrive with clear sunset provisions or defined criteria for what would satisfy the locality's concerns. Developers are left reading political signals rather than regulatory frameworks — a fundamentally unstable operating environment. Do you continue investing in pre-development work, betting the moratorium lifts? Do you write down the asset and move on? These aren't easy calls, and they consume management bandwidth and capital that would otherwise go toward actual development.

Smaller regional developers face the sharpest edge of this problem. A hyperscaler can absorb a delayed market and simply accelerate deployment elsewhere. A mid-sized developer with concentrated exposure to a single metro doesn't have that buffer.

Strategies That Actually Work

The developers navigating this environment most effectively are doing a few things that the industry as a whole should be watching.

First, they're engaging earlier. The communities most likely to impose moratoriums are the ones that feel surprised by data center development — where a 500-acre campus appears to materialize overnight without meaningful local dialogue. Developers who build relationships with county administrators, utility planners, and community stakeholders before breaking ground give those stakeholders something to defend internally. A project with community buy-in is dramatically harder to impose moratoriums on than one that arrives as a fait accompli.

Second, smart developers are investing in the infrastructure argument. Many moratoriums are triggered by legitimate grid concerns — utilities that can't commit to sufficient power delivery within project timelines. Developers who come to the table with co-investment proposals for transmission upgrades, substation builds, or on-site generation capacity change the conversation. They stop being a burden on the system and become a partner in solving a problem the utility already had.

Third — and this is the less comfortable recommendation — the industry needs to get more serious about regulatory advocacy at the state level. Individual localities shouldn't be the sole arbiters of decisions that affect regional economic competitiveness and, frankly, national digital infrastructure capacity. States that establish clear, consistent frameworks for data center permitting — with defined timelines, transparent criteria, and preemption of arbitrary local moratoria — will capture a disproportionate share of the next wave of investment.

Georgia, Texas, and Indiana have all moved in this direction to varying degrees, creating environments where developers can underwrite projects with confidence. That's not an accident; it reflects deliberate policy choices by state governments that understand what's at stake.

What Success and Failure Actually Look Like

The counties surrounding Phoenix offer a useful case study in divergent outcomes. Maricopa County built a data center ecosystem by maintaining regulatory continuity even as water usage debates intensified. Developers responded by investing in water recycling systems and entering into formal commitments around PUE efficiency targets — concessions they made voluntarily because the regulatory environment made the market worth fighting for.

Contrast that with localities that have imposed open-ended moratoriums without clear resolution pathways. Projects stall, developers redirect capital, and the locality eventually lifts the moratorium into a market that has already moved on. The sites sit undeveloped. The tax revenue never materializes. The community got the pause it wanted and none of the investment it needed.

The lesson isn't that communities should accept whatever developers propose. It's that leverage is perishable. A locality with a genuinely attractive site — good power access, fiber infrastructure, tax incentives, proximity to fiber routes — has real negotiating power. Use it to extract commitments on water, grid co-investment, and community benefit agreements. Don't use it to impose indefinite uncertainty, because that's the one thing that makes the leverage disappear entirely.

Where This Goes From Here

The data center buildout driven by AI infrastructure demand isn't slowing. The compute requirements for training and running large language models are doubling on timescales that make even aggressive development pipelines look conservative. That pressure will keep pushing developers into new markets, and it will keep testing the regulatory environments of localities that haven't thought carefully about how they want to engage.

Localities that establish clear, workable frameworks — even demanding ones — will attract investment. Those that default to moratoriums as a management tool will find that developers are polite about it, professional about it, and gone.

The infrastructure that powers the next decade of the digital economy is being sited right now. The decisions that localities make about data center development in the next 24 months will shape their economic trajectories for 20 years. That's not a reason to abandon community concerns — it's a reason to resolve them urgently, with specificity, rather than parking them behind a moratorium and hoping the problem sorts itself out.

It won't. The market will.

Call to Action: Ready to explore opportunities in the data center market? Visit InfraSale Marketplace for more information.

[INTERNAL LINK: data center growth]

[INTERNAL LINK: economic impact of data centers]

[INTERNAL LINK: regulatory frameworks for data centers]