Last Update: 08/01/2026 at 1:34 PM EST

Morning Briefing: Data Centers

Saturday, June 27, 2026

June 27, 2026

Data Center Moratoria Move Ahead Of The Projects

Yesterday was less about new capacity breaking ground than about communities, utilities, and courts trying to define the rules before the next large data center arrives. That distinction matters: several of the strongest developments involved places acting before a formal application, before permanent zoning language, or before utility agreements have a settled form.

The day reinforced a pattern that has been building all week. Data center scrutiny is becoming procedural, not just political. Moratoria, narrow zoning districts, disclosure requirements, community benefit agreements, utility flexibility arrangements, and lawsuits are becoming the machinery through which AI infrastructure is either slowed, reshaped, or made more acceptable.

The practical takeaway is that power access and public permission are now intertwined. Developers can still point to demand, capital, and economic upside, but yesterday’s reporting showed that communities and utilities increasingly want proof: who pays for grid upgrades, how water and noise will be managed, what happens during grid stress, and whether local governments retain meaningful control.

Knox County, Tennessee, implemented a one-year moratorium on new data centers after a unanimous county commission vote, WBIR reported. The pause runs through June 30, 2027, unless new placement and operating rules are adopted sooner. That is a concrete development, not just local unease: the county is using time as a regulatory tool while it writes standards for a category of project that can arrive faster than local codes are prepared to handle.

East Fishkill, New York, offered another version of the same dynamic. Spectrum News 1 Hudson Valley reported that residents rallied against a potential large data center after New Jersey-based Treetop Development had indicated interest in a 1,000-MW facility. Town leaders stressed that no formal application had been submitted, but the town had already approved a three-year local moratorium. The notable point is the timing: opposition and policy are forming around prospective load and land-use risk before a project enters the normal approval pipeline.

Lancaster, Pennsylvania, showed how difficult it can be to turn broad concern into workable zoning language. LancasterOnline reported that the city delayed a vote on rules that would restrict future data centers to a small industrial district and require zoning hearing approval, setbacks, and reports on noise, energy use, water use, decommissioning, heat mitigation, and emergency response. The delay came partly from confusion over whether the ordinance could affect two already-planned projects. For cities, the lesson is that precision matters: an ordinance meant to control future projects can become contentious if its effect on existing proposals is unclear.

Utility Dive’s reporting on flexible data center operations was the day’s most important power-access development. EPRI’s FlexMosaic and DCFlex efforts, along with Emerald AI’s software tests with utilities, point toward a potential bargain: data centers may get faster or more feasible interconnection if they can reduce, shift, or manage load during grid stress under preapproved rules. But the same reporting showed the unresolved issue clearly. Utilities and data centers still lack standardized binding agreements over control, visibility, dispatch authority, and operational guardrails.

Texas remained the clearest scale test. Houston Public Media reported that the state has 335 existing data centers and at least 248 additional projects planned, with nearly half of planned projects in unincorporated areas where city-level blocking authority is limited. ERCOT has received large-load requests that could require up to 439 GW of capacity, though not all will be built. That number is less a forecast than a measure of pressure on planning systems that were not designed for so many speculative or competing large-load requests at once.

KARE11 detailed a pending lawsuit by Eagan Capital against the City of Eagan, Minnesota, over a one-year moratorium that restricts data centers above 20 MW and limits upgrades that would push existing facilities above 9 MW. The case matters because it tests how far local governments can go when they regulate by electricity demand. If courts find local caps are preempted or arbitrary, some moratoria may have to be rewritten around land use, noise, water, emergency planning, or other municipal concerns rather than power thresholds alone.

Key Points

  • Local governments are moving from protest management to rule design. The Tennessee Lookout’s community guidance emphasized zoning definitions, conditional use processes, disclosure of water and energy use, limits on nondisclosure agreements, and legally binding community benefit agreements. That kind of advice reflects a maturing opposition environment: communities are not simply asking whether they want data centers; they are learning which documents and legal tools shape the outcome.
  • Utilities are beginning to treat compute flexibility as an operational asset, but not yet as a settled contract model. The emerging question is no longer only whether a substation or feeder can serve a project. It is whether a data center can become predictable enough, visible enough, and controllable enough to help manage local overloads, voltage issues, and peak stress without giving utilities unacceptable authority over customer operations.
  • Public resistance is broadening from individual projects into a trust problem for the sector. The Star Tribune cited a Minnesota Poll showing 63% of respondents would oppose data center construction in their communities, with opposition spread across parties. That does not mean every project is doomed, but it does suggest developers are entering many hearings with a credibility deficit before site-specific facts are even debated.
  • Unincorporated and lightly governed sites are becoming more consequential. Texas illustrates the issue most clearly: when many planned projects sit outside municipal boundaries, local city tools are less effective, pushing attention toward county limits, state oversight, utility cost recovery, water disclosure, and ERCOT planning. The governance challenge shifts from one city council vote to a more complicated patchwork of state, utility, and local authorities.
  • The legal response is starting to run in both directions. Communities are using moratoria and zoning rewrites to slow projects, while property owners and developers are challenging those pauses when they believe local governments have overreached. That two-sided pressure could eventually produce clearer rules, but in the near term it adds uncertainty to site control, entitlement timelines, and financing assumptions.

Implications

For developers, pre-application risk is rising. East Fishkill’s moratorium and rally around a project with no formal filing show that land control or early interest can trigger political and regulatory response before the developer is ready to present a full mitigation package.

Permitting packages will need to look more like infrastructure accountability packages. Lancaster’s proposed reporting requirements and the Tennessee Lookout’s community toolkit point toward a more demanding baseline: noise studies, water and energy disclosure, emergency response planning, decommissioning plans, heat mitigation, and clearer community benefits are becoming part of the expected conversation.

Flexible load could become a serious speed-to-power tool, but only if it becomes enforceable. Yesterday’s utility reporting made the promise visible and the gap just as visible: software, workload management, and backup power can help during grid stress, but utilities still need binding terms before they can rely on those capabilities for planning or operations.

Moratoria may buy time, but they also invite legal tests. The Eagan case is a reminder that local governments need defensible authority and careful drafting, especially when rules are framed around electricity use rather than traditional land-use impacts.

Texas will remain a bellwether because it combines enormous load interest, water stress, fast-growing AI demand, and uneven local authority. If state agencies or lawmakers tighten disclosure, tax exemptions, or cost-recovery rules there, the effects could shape how other high-growth markets handle large-load development.

Watchpoints

Watch

Whether New York Gov. Kathy Hochul signs, vetoes, or modifies the statewide one-year data center moratorium passed by state legislators.

Watch

Lancaster City Council’s expected July 14 return to its proposed data center zoning ordinance, especially whether the language clearly excludes or affects already-planned projects.

Watch

How Knox County drafts permanent rules during its one-year pause, and whether nearby Tennessee jurisdictions adopt similar guardrails.

Watch

The Eagan Capital lawsuit and whether courts limit local authority to regulate data centers through electricity-demand caps.

Watch

Whether the 96-MW Aurora AI Factory in Manassas, Virginia, helps validate flexible data center operations at commercial scale.

Watch

Texas follow-through on data center water reporting, tax exemptions, utility cost recovery, and treatment of large-load requests in ERCOT planning.

Fallout

Meaningful movement came in three areas: local governments converting opposition into moratoria and zoning tools, utilities exploring flexible-load arrangements as a response to grid constraints, and high-growth states confronting the practical limits of water, power, and local control. None of these amounted to a single national break, but together they strengthened the recent move toward earlier and more formal gatekeeping of large data center projects.

Moratoria And Local Siting Control

Local governments are increasingly using temporary pauses, zoning rewrites, and project-specific review requirements to slow data center development until they understand the power, water, noise, and neighborhood consequences.

Fresh developments

Knox County’s one-year moratorium and East Fishkill’s three-year pause showed communities acting before permanent rules are settled and, in East Fishkill’s case, before any formal application has been filed. Lancaster added a more technical example: the city is trying to create a narrow future siting path, but delayed its vote when council members questioned how the language would affect two already-planned projects. KARE11’s reporting on the Eagan lawsuit added a legal counterweight, showing that moratoria built around power thresholds may face court scrutiny.

Why we noticed

These developments matter because moratoria are becoming more than expressions of concern. They are now a standard first move in places where local codes lag the scale of proposed data centers. For developers and investors, that turns early community and legal diligence into a schedule-critical issue, not an afterthought.

Watch for:

  • Whether Lancaster approves revised zoning language on July 14.
  • Whether the Eagan lawsuit narrows how cities can write moratoria tied to electricity demand.
  • Whether East Fishkill’s local pause becomes more consequential if New York adopts a statewide moratorium.

Topic links:

  • New York Data Center Moratorium
  • Pennsylvania Data Center Standards
  • Data Center Backlash Grows Nationwide

Power Access And Grid-Responsive Compute

Power availability remains one of the main constraints on AI data center growth. The emerging question is whether operators can make their loads flexible enough to reduce grid stress and improve the case for faster interconnection.

Fresh developments

Utility Dive reported on EPRI’s FlexMosaic and DCFlex efforts and Emerald AI’s tests that translate utility grid signals into preapproved data center actions. The day’s reporting made the opportunity and the obstacle clearer at the same time: data centers may be able to reduce peak demand, manage workloads, or rely on backup power during grid stress, but utilities and operators still need standardized, enforceable agreements over control, visibility, and guardrails.

Why we noticed

This is strategically important because flexibility could become one of the few tools that helps both sides: developers want faster access to power, while utilities need headroom and reliability protections. But without binding service terms, flexibility remains a promising argument rather than bankable capacity planning.

Watch for:

  • Whether utility-data center flexibility agreements become standardized rather than negotiated case by case.
  • Whether the Aurora AI Factory in Manassas demonstrates flexibility at a scale utilities can rely on.
  • Whether regulators begin treating flexible data center load differently from inflexible large load.

Topic links:

  • Texas Tightens Data Center Oversight
  • Texas Data Center Water And Grid Pressure

Water, Grid Burden, And Public Accountability

As data center proposals grow larger, communities and state officials are pressing for clearer answers on water use, cooling design, grid costs, tax incentives, and public disclosure.

Fresh developments

Houston Public Media’s Texas overview underscored the scale of the problem: 335 existing facilities, at least 248 planned projects, and ERCOT large-load requests that could total up to 439 GW if fully realized. The same reporting pointed to closed-loop cooling plans by Google in water-stressed parts of Texas, local restrictions in several communities, and state-level scrutiny of tax exemptions and utility cost recovery. The Tennessee Lookout’s community guidance added the governance side, emphasizing disclosure, public hearings, and legally binding community benefit agreements.

Why we noticed

Water and power questions are no longer technical appendices to development applications. They are becoming the basis for local legitimacy, state oversight, and, potentially, whether a project can move through permitting without litigation or political backlash.

Watch for:

  • Whether Texas moves toward stronger water-use disclosure or cooling-technology requirements.
  • Whether state officials revisit data center tax exemptions as grid and water concerns rise.
  • Whether more communities require community benefit agreements before supporting large projects.

Topic links:

  • Texas Data Center Water And Grid Pressure
  • Data Center Water Use And Regulation
  • Data Center Tax Break Backlash

Final Thought

The industry often describes the bottleneck as speed to power. Yesterday showed a second bottleneck becoming just as important: speed to public trust. In more places, a data center now has to prove not only that it can be built, but that its power, water, noise, and cost impacts can be governed before the project gets too far ahead of the community.