Weekly Briefing: Data Centers

The clearest development was the normalization of the moratorium as a planning tool. Linn County, Iowa, approved an 18-month halt on new data centers in unincorporated areas while it evaluates rules around water studies, water-use agreements, economic development agreements, and road-use plans. Cleveland advanced a shorter permitting pause to study infrastructure capacity and electricity and water effects. St. Charles County introduced a six-month pause tied to health, infrastructure, and quality-of-life studies. Desert Hot Springs moved to extend an interim ordinance, while Brentwood explored a citywide ban and Sioux County continued working under a one-year pause. Seen together, these are not identical anti-development measures. They are evidence that local governments increasingly regard ordinary zoning as inadequate for hyperscale loads.

Nashville provided the week’s sharpest example of local control becoming more forceful. Reporting from the Nashville Banner showed two distinct but related pressures: Fisk University faced North Nashville scrutiny over a proposed 30-megawatt facility on its historic campus, while Mayor Freddie O'Connell moved toward condemnation proceedings for a separate property near the Nashville Zoo tied to DC Blox. The significance is not simply that residents objected. It is that city officials were considering tools beyond routine zoning, while also directing attention to a July 7 public hearing on broader data center regulations. Nashville may become a test of how far a city is willing to go to block or redirect specific sites rather than merely slow the category.

Water access became more visibly decisive. In California’s Imperial Valley, Business Insider reported that Imperial Valley Computer Manufacturing sued after Imperial Irrigation District denied access to Colorado River water for a proposed 330-megawatt AI data center said to require 287 million gallons. In North Texas, the Fort Worth Report described West Cedar Creek Municipal Utility District suspending high-intensity water-service commitments through April 2027 after a Diode Ventures proposal raised questions about 1 million to 5 million gallons per day of cooling demand. In Michigan, The Conversation highlighted utility limits around proposed projects connected to the University of Michigan and Google. The pattern is important because water concerns are shifting from public talking points into feasibility constraints imposed by the institutions that actually control service.

Grid pressure remained a broader backdrop, but it was not merely abstract. Reuters reported that PJM issued emergency demand-response orders during a heat wave as demand neared record levels, generation availability fell, and transmission congestion raised costs in Mid-Atlantic zones that include major data center concentrations. WJLA’s Northern Virginia reporting showed the local face of that pressure: Dominion planning transmission upgrades, including a proposed 500,000-volt line and 185-foot tower, while residents resisted the infrastructure needed to serve load growth. The caution is that PJM’s emergency action was a heat-wave grid event, not a data-center-only event. Even so, it gave communities and policymakers a concrete example of why large-load growth now belongs inside siting and ratepayer debates.

Several fights also crossed into legal or quasi-legal channels, showing that the conflict is maturing. Wisconsin Public Radio covered a federal noise lawsuit against Microsoft over the Fairwater data center in Mount Pleasant, where residents alleged excessive sound from generators and cooling equipment. WUSF reported procedural claims around Fort Meade’s approval of a 1,300-acre AI hyperscale project in Florida. NetChoice challenged Wrightstown, Wisconsin’s advisory referendum, arguing Wisconsin law restricts such votes. In Hoffman Estates, Illinois, Karis Critical withdrew a rezoning request after organized opposition, a negative Plan Commission recommendation, an Open Meetings Act complaint, and concerns about missing site plans, water details, and environmental review. The week showed that opposition is no longer confined to the hearing room; it is moving through courts, claims, withdrawals, and procedural challenges.

The political story remained messy, which is part of what made the week revealing. Reuters reported that Energy Secretary Chris Wright urged data center supporters to push back against critics, while Washington Post reporting described a divide among Republicans between competitiveness arguments and local opposition to AI infrastructure siting. Gallup polling cited by Planetizen found heavy opposition to data centers near homes, and Utah reporting from KSL showed Kevin O'Leary and others walking back China-linked claims about opponents to a Box Elder County project. The emerging lesson is that the economic-development pitch is weakening when it stands alone. Communities are increasingly asking for enforceable detail: how much water, whose power, what noise level, what tax treatment, what permanent jobs, and what recourse if promises fail.

The week should not be overread as evidence that data center development is broadly stalling. Many moratoriums are temporary, many disputes are site-specific, and jurisdictions with available land, power, water, and negotiated benefits may still welcome projects. But the direction is clearer than it was: the physical infrastructure of AI is being pulled into local democratic process, utility planning, and environmental scrutiny. For developers, that means political risk now begins well before a formal application. For communities, it means the most consequential decisions may occur while rules are being written, not after a site plan is filed.