Is a Moratorium on Data Center Construction Inevitable?
A potential moratorium on data center construction in Michigan City could reshape the industry landscape. What does it mean for you?
The data center industry has spent the last decade moving fast and asking questions later. Cheap land, favorable tax incentives, and insatiable demand from cloud providers and AI workloads meant that developers could outrun local opposition — breaking ground before communities fully understood what was being built next door. That era may be ending.
A proposed moratorium on data center construction in Michigan City, Indiana, is a small but telling signal. On Royal Road, a site that would otherwise be just another square footage entry in a developer's portfolio, local government officials are pumping the brakes. They want time. Time to listen, time to understand, and time to decide whether the trajectory they're on actually serves the people who live there.
That pause — however temporary — deserves more attention than the industry is giving it.
What a Moratorium Actually Means (And Why Michigan City Matters)
A moratorium isn't a rejection. It's a timeout. It's local government saying: we need to understand this before we approve it, not after. In Michigan City's case, officials are seeking space to hear from stakeholders before a data center construction project on Royal Road moves further along.
On the surface, that sounds reasonable. But for developers with capital deployed, lease commitments made, and hyperscaler contracts waiting, a moratorium is a serious disruption. Timelines in data center development are brutally unforgiving. A six-month regulatory pause can cascade into 12 to 18 months of actual delay once permitting, procurement, and contractor scheduling are recalibrated. At the scale of a utility-grade data center — think 50 to 200+ MW of critical load — that's not just an inconvenience. It's a material financial event.
Michigan City is not a Tier 1 data center market. It doesn't have the established infrastructure of Northern Virginia, Phoenix, or the Chicago suburbs. And that's precisely why this situation is interesting. Developers have been pushing into secondary and tertiary markets to find available land, lower power costs, and less regulatory friction — and some of those markets are now pushing back.
The Real Concerns Driving Local Resistance
To understand why moratoriums happen, you have to understand what communities are actually worried about. It's rarely just NIMBYism.
Data centers are infrastructure-heavy, power-hungry, and water-intensive. A large-scale facility can draw 50 to 100 megawatts of electricity continuously — enough to power tens of thousands of homes — and that load hits local utility grids immediately. In markets without spare transmission capacity, that means ratepayers may face grid upgrades they didn't ask for and may ultimately help finance.
Water consumption is another friction point. Evaporative cooling systems in large data centers can consume millions of gallons annually. For communities in areas with existing water stress or aging municipal infrastructure, that's a legitimate concern, not a talking point.
Then there's the jobs question. Data centers are often sold to local governments on an economic development narrative: jobs, tax revenue, investment. The tax revenue part is often real. The jobs part is more complicated. A fully operational hyperscale facility might employ 30 to 50 full-time staff. For a municipality that approved a multi-hundred-million-dollar development expecting an employment boon, that gap between expectation and reality creates resentment — and eventually, regulatory reconsideration.
The moratorium in Michigan City is, at least in part, a symptom of communities feeling like they weren't given enough information to make an informed decision the first time around.
The Regulatory Direction of Travel
Michigan City isn't operating in isolation. Across the country — and in Europe, where restrictions on data center development in Amsterdam and Dublin have already forced major developers to reroute investment — local governments are getting more assertive about controlling where and how data centers get built.
In the U.S., the regulatory framework for data centers remains fragmented. There's no federal standard. Zoning decisions happen at the county or municipal level, environmental reviews vary by state, and utility interconnection rules are governed by regional transmission organizations that often move on timelines completely disconnected from developer expectations.
What's changing is the sophistication of local opposition. Residents and local officials are learning from each other. A community in Virginia that negotiated successfully for tax agreements and infrastructure commitments becomes a reference point for communities in Indiana or Texas. The information gap between developers and municipalities is closing — and as it closes, developers can expect more scrutiny, more conditions, and yes, more moratoriums.
The regulatory trajectory here is clear: data center development is going to get more complicated in markets that aren't already deeply embedded in the industry. That's not a reason to avoid those markets — but it is a reason to engage them very differently than developers have in the past.
What Developers and Investors Should Do Now
Waiting out a moratorium is a strategy, but it's a passive one. The developers who navigate this environment most successfully will be the ones who get ahead of community and regulatory concerns before ground is broken, not after opposition has organized.
A few concrete shifts worth considering:
Invest in community engagement early and seriously. Not a single town hall the week before a zoning vote — sustained outreach that explains what the facility will actually do, what it will consume, what it will employ, and what the municipality can expect in tax revenue over 10 and 20 years. Developers who treat this as a checkbox exercise will keep running into moratoriums.
Restructure project timelines to account for regulatory risk. Secondary markets are attractive for cost reasons, but that cost advantage can evaporate quickly if a project sits idle through a prolonged regulatory review. Underwriting deals in these markets should include realistic assumptions about entitlement timelines — and those assumptions should be more conservative than they were three years ago.
Get ahead of the power conversation. One of the fastest ways to lose a community is to show up to a utility commission meeting after the fact. Developers who proactively engage with utility partners and local governments about grid capacity, upgrade costs, and rate impacts are in a fundamentally stronger position than those who treat power as a procurement problem to solve internally.
Consider the water story. Air-cooled and liquid-cooled systems that reduce or eliminate water consumption are increasingly available and competitive on total cost of ownership. In water-stressed markets, leading with that technology choice is a genuine differentiator — and a meaningful signal to regulators that the developer is thinking about long-term community fit.
The Opportunity Inside the Disruption
Here's the non-obvious take: moratoriums, handled correctly, can actually benefit developers who are serious about long-term market presence.
A moratorium that forces a genuine dialogue between a developer and a community — and results in real commitments on power, water, local hiring, and tax structure — creates a more durable operating environment than a project that got approved over community objection. Facilities that communities feel were imposed on them face ongoing friction: political opposition, regulatory revisiting, challenges to incentive agreements. Facilities that communities understand and feel some ownership over tend to operate without that drag.
The Michigan City situation is still unfolding. But the question it raises is one every developer, investor, and infrastructure owner in this space should be asking themselves right now: are we building relationships in these communities, or are we just building data centers?
The answer will determine a lot about which projects get built in the next decade — and which ones don't.
Explore the InfraSale Marketplace for more insights on data center development.