No Means Nothing: How Data Centers Are Overriding Communities, Draining Public Resources, and Rewriting the Rules of Land Use

The New Land Rush Doesn’t Ask Permission

The AI boom has a physical infrastructure problem. Every large language model, every cloud query, every automated system requires server farms, and those server farms require land, water, and power at a scale that rewrites local economics. Hyperscale data centers, the facilities that power the largest commercial AI systems, can consume as much electricity as a city of 50,000 people. They require hundreds of acres of buildable land. They pull water from local systems at rates that stress municipal aquifers. And they generate constant mechanical noise that does not stop.

What they do not require, in an increasing number of states and under the current federal posture, is community consent.

That is the accountability gap at the center of the data center land rights fight. And Michigan is ground zero.

Michigan Set the Table, Then Watched Developers Eat

In late 2024, Michigan’s Democratic-controlled legislature passed a bipartisan two-bill package granting large data centers full exemptions from sales and use taxes on equipment through at least 2050. To qualify, developers need to invest at least $250 million and commit to employing 30 people. Thirty people. For a facility that might draw a gigawatt of electricity and consume the water resources of a mid-sized city.

The tax legislation bitterly divided Michigan Democrats. Progressive members wanted renewable energy requirements, ratepayer protections, and binding environmental safeguards. Pro-business factions and organized labor backed the package. The protections were stripped. The exemptions passed. And within months, a wave of hyperscale proposals descended on communities that had never been part of the negotiation.

Michigan’s natural assets made it a target: cold climate to naturally cool server infrastructure, abundant freshwater from the Great Lakes watershed, and legacy industrial grid capacity from decades of manufacturing decline. As one Michigan State University researcher described it to state legislators, the combination of available energy, water, and cold weather created conditions developers had been looking for.

What developers also found was a legal landscape where local “no” votes could be quickly transformed into expensive litigation pressure on under-resourced township governments.

Saline Township: When “No” Means Nothing

The sharpest illustration of how this plays out came in Saline Township, Washtenaw County, when Related Digital, Oracle, and OpenAI selected 250 acres of farmland just south of Ann Arbor for what would become Michigan’s first proposed hyperscale data center, connected to the multi-billion-dollar Stargate initiative.

The lawsuit alleged “exclusionary zoning,” a legal theory that a municipality has unreasonably banned an entire category of lawful land use. Related Digital’s argument was specific: Saline Township had no industrially zoned land at all, and a data center qualified as a “necessary” use that could not be categorically excluded under Michigan law. The township, lacking the legal resources to sustain prolonged litigation against a billion-dollar developer, settled within weeks.

Construction is now underway. The facility is projected to consume approximately 1.4 gigawatts of electricity, making it one of the largest AI infrastructure projects in the United States. Michigan Attorney General Dana Nessel intervened separately, asking the Michigan Public Service Commission to slow DTE Energy’s process of fast-tracking a special power contract for the facility before adequate public review. The question of who pays for grid infrastructure upgrades remains contested.

The pattern in Saline is not unique to Michigan. It is the playbook.

The National Pattern: Opposition That Gets Overridden Anyway

Michigan is not alone. Across the country, community opposition to data center siting has produced wins, stalemates, and outright reversals, often within the same project timeline.

In Prince William County, Virginia, the $24.7 billion PW Digital Gateway project drew three separate lawsuits from activist groups who raised concerns about environmental impact, noise, grid strain, and damage to nearby historic sites. A county judge dismissed one challenge in October 2024. The plaintiffs appealed to the Virginia Court of Appeals. As of spring 2025, the project remained in legal limbo, but the developer had not withdrawn.

In Coweta County, Georgia, residents are fighting a proposed 829-acre hyperscale campus on land that was rezoned from rural conservation to industrial in a narrow 3-2 county commission vote. A peer-reviewed study cited in the community’s appeal projects that the rezoning could produce an estimated $118 million decline in residential property values across more than 1,200 parcels within 1.25 miles of the site. Construction could run for up to ten years. The appeal also argues that when the developer amended its application to seek a more intensive industrial classification in January 2026, residents were cut out of the process and no new environmental review was triggered.

In Wisconsin, a 600-acre AI data center proposal triggered the formation of the community group Great Lakes Neighbors United, which organized protests including a rally at the state capitol. The concerns there mirror Michigan’s: eminent domain risk for transmission line corridors, electricity price increases hitting residential ratepayers, and minimal binding job commitments from developers.

The Legal Toolkit Communities Are Actually Using

The good news, to the extent there is good news, is that communities facing data center proposals have more legal tools than most residents realize. The difficult news is that those tools work best before the shovels go in.

Zoning and moratoriums represent the first line of defense. At least 19 Michigan townships enacted moratoriums on data center development after the 2024 tax incentive package passed, buying local officials time to draft ordinances governing where and how facilities could be sited. Moratoriums do not stop projects permanently, but they create a legal window for communities to establish the specific regulatory frameworks that make future denials harder to challenge as exclusionary.

Environmental review challenges offer a separate litigation pathway, particularly when developers amend applications to seek more intensive uses without triggering new public comment periods. State equivalents of the National Environmental Policy Act create procedural rights that courts have enforced when agencies skip required steps. Noise, light, water quality, impervious surface impacts, and habitat loss have all been successfully pleaded as cumulative community burdens, not merely private neighbor-to-neighbor nuisances.

In South Carolina, a January 2026 complaint in Miles Crosby and Jennifer Singleton v. Colleton County specifically framed data center noise as an environmental harm tied to the category of land use broadly, not a one-time event. That framing matters for establishing ongoing injury, which is necessary for injunctive relief.

Water rights challenges are an underutilized frontier. The Ypsilanti Community Utilities Authority voted in April 2026 to impose a 12-month moratorium on supplying water to large data centers, citing strain on utility capacity. That decision was itself challenged. But water authority governance structures give municipalities a direct chokepoint that does not depend on zoning law: a data center cannot operate without water, and the utility that controls supply has independent legal authority over service agreements.

Over 40 percent of planned and existing U.S. data centers are located in areas classified by environmental researchers as having high or extremely high water scarcity. In Texas, data center water consumption is projected to reach up to 399 billion gallons annually by 2030, roughly 6.6 percent of the state’s total water use. Michigan’s Great Lakes watershed has made it a target for exactly this reason. The question of whether public water systems can legally be required to serve private hyperscale operations at the expense of residential capacity has not been fully litigated. It should be.

The Subsidy Accountability Problem

Beyond the immediate land use fights, there is a structural accountability failure baked into how data center incentive deals are structured. Tax exemptions reduce the local tax base. Utilities extend infrastructure. Fire departments and roads absorb additional demand. And residents pay for all of it while the developer captures the value.

In Michigan City, Indiana, Mayor Angie Nelson Deuitch rejected an $800 million data center proposal in July 2025 specifically because the developer could not provide binding commitments for meaningful job creation, community benefits, or substantial tax impact. That outcome is instructive: executive political will, backed by clear standards, can hold developers accountable before the deal is made. The problem is that most communities are not negotiating from that position. They are reacting to announcements that were finalized in Lansing or Silicon Valley months before the township board received a rezoning application.

What Communities Can Do Right Now

The legal window for meaningful intervention closes fast. Once a consent judgment is signed, once construction begins, once a utility contract is approved, the procedural options narrow sharply. For communities that are currently facing proposals, or that want to build defenses before proposals arrive, the most important actions are immediate.

First, document baseline conditions now. Noise levels, water table measurements, air quality readings, and utility usage data create the evidentiary foundation for any future nuisance, environmental, or property damage claim. Attorneys investigating data center harms consistently note that the strongest cases are built on documented before-and-after comparisons. You cannot create that record retroactively.

Second, file public records requests for all communications between state economic development officials and data center developers. In Michigan, the Stargate deal was shaped by conversations between Governor Whitmer’s office and OpenAI that began in February 2025, months before Saline Township saw a rezoning application. Those communications are public records. The Michigan FOIA Generator in The Lab can help structure those requests.

Third, push your local governing body to adopt specific performance standards rather than categorical bans. Exclusionary zoning claims succeed when municipalities cannot point to affirmative, reasonable standards. A township that can demonstrate it allows data centers in appropriate zones, with documented noise limits, water use caps, and setback requirements, is in a categorically stronger legal position than a township that simply voted no.

Fourth, coordinate across jurisdictions. Data center developers are shopping across regions, and they are comparing community resistance levels when selecting sites. Michigan communities that coordinated moratoriums and shared legal resources demonstrated that collective action can shift developer calculations, even when individual townships lack the resources to sustain litigation alone.