New York's 2026 Data Center Moratorium: What the Scope Actually Covers — and What Keeps Moving
← Back to Blog Environmental

New York's 2026 Data Center Moratorium: What the Scope Actually Covers — and What Keeps Moving

New York's 2026 hyperscale data center moratorium pauses new state permits for facilities of 50 MW or more. Here is the actual scope, exemptions, and timeline.

by iSi Environmental

On July 14, 2026, New York became the first state to pause permitting for new hyperscale data centers — and within 24 hours, headlines were calling it a ban. It is not one. The scope of New York’s 2026 data center moratorium is narrower than most coverage suggests: Executive Order No. 62 directs the Department of Environmental Conservation (DEC) to hold in abeyance new applications for discretionary state environmental permits — only for covered facilities of 50 MW or more, only for applications not already deemed complete, and only until a statewide environmental review is finished.

If you are a data center developer or facility planner trying to figure out what is actually frozen in New York, here is the precise answer: complete-as-of-July-14 applications proceed. Local permits are expressly untouched. Sub-50 MW facilities are out of scope entirely. Manufacturing, research, education, and medical facilities are exempt. The pause lifts when the Department of Public Service (DPS) submits a final Generic Environmental Impact Statement (GEIS) — a process the Governor’s office says will take up to one year.

That precision matters, because the counter-narrative is loud. The Associated General Contractors of NYS called the order a “missed opportunity” for the construction industry (Spectrum News), national political criticism landed the next day (CNBC), and every other state is still recruiting hyperscale projects with incentives. Both things are true: the instrument is narrow, and the competitive stakes are real. This post walks through the actual scope, question by question, from the primary sources.

What does New York’s data center moratorium actually pause?

One thing: under EO 62 §1, DEC must hold in abeyance discretionary state environmental permit applications for construction or expansion of covered data centers — but only applications not determined complete before July 14, 2026. Complete applications proceed, local permits are unaffected, and the pause ends when DPS submits the final GEIS.

That is the entire operative mechanism. The order does not revoke any existing permit, does not stop construction already authorized, and does not touch building permits, zoning approvals, or any other local government action — those are expressly outside the order. It also builds in a disclosure requirement worth flagging now: expect DEC to require a written statement identifying whether any discretionary-permit application “relates to or involves” a data center (EO 62 §1). If you have New York exposure, that statement belongs in your application packages going forward. The dividing line for pending work is completeness, not submission date — an application filed in June but not yet deemed complete by DEC sits in abeyance; one deemed complete on July 10 proceeds.

Which facilities count as a “data center” under Executive Order 62?

EO 62 §6 covers facilities — or groups on contiguous sites — housing servers or computing equipment with uninterruptible power supplies, high-density cooling, and/or dedicated cybersecurity infrastructure, providing data storage, cloud computing, or content delivery, and consuming or capable of consuming 50 MW or more. All elements matter; a 30 MW enterprise facility is out of scope.

The definition is a three-part test: facility characteristics (UPS systems, high-density cooling, dedicated cybersecurity), function (data storage, cloud computing, or content delivery), and the 50 MW threshold. A project has to satisfy all three — plus a non-exempt primary use — before the moratorium touches it. Note the “capable of consuming” language and the contiguous-sites provision: a campus phased as three 20 MW buildings on adjacent parcels does not slip under the threshold by subdivision. Expect definitional pressure on exactly these edges — the 50 MW line and the “primarily used for” exemption language are where scoping disputes will concentrate as DEC applies the order.

Which projects are exempt from the New York moratorium?

Four primary-use exemptions appear in EO 62 §6: manufacturing, research (explicitly including quantum computing and biomedical research), education (accredited New York colleges and universities conducting academic research, plus the Empire AI consortium), and medical care. Also effectively outside the order: applications DEC deemed complete before July 14, 2026, and projects needing only local approvals.

The exemption list is broader than the headline coverage acknowledged, and it tracks the state’s economic-development priorities — quantum and biomedical research facilities and the Empire AI consortium keep moving regardless of their power draw. For a developer, the practical exercise is self-qualification: run each New York project through the §6 test and the exemption categories before assuming the pause applies. A high-density computing facility whose primary use is manufacturing process control, for example, sits on different footing than a colocation campus. Where a project genuinely straddles categories, the completeness status of its DEC applications as of July 14 may matter more than the definitional argument.

How long will the New York data center moratorium last?

Up to one year, per the Governor’s press release — but the trigger is a milestone, not a date. The moratorium ends when DPS submits its final Generic Environmental Impact Statement and findings statement. There is no fixed sunset in the order itself; the GEIS submission, not the calendar, lifts the pause.

That structure cuts both ways for planners. If the GEIS moves faster than expected, the pause could lift early; if the SEQRA process — which requires public comment and a hearing — runs long, “up to one year” is an estimate, not a ceiling written into the order. The planning-safe assumption is a window running to roughly July 2027, with the post-moratorium standards taking shape publicly along the way. That is the argument for engaging the GEIS process rather than waiting it out: the document that ends the moratorium is also the document that defines what new projects will be measured against when it does.

What is the Generic Environmental Impact Statement (GEIS) for data centers?

A programmatic SEQRA review under ECL Article 8 that EO 62 directs DPS to prepare — with public comment and a hearing — assessing data centers’ impacts on energy demand, water use and quality, air quality, disadvantaged communities, and noise. It connects to DPS Case 26-E-0045 on large-load interconnection and, once finalized, becomes the consistent statewide standard new projects are measured against.

A generic EIS differs from a project-specific one: instead of reviewing a single site, it evaluates a class of development statewide and produces findings that individual projects can then tier from. For developers, that is not purely a burden — a finished GEIS can make individual project reviews faster and more predictable, because the programmatic questions are answered once. The scope list is the preview of your future permit conditions: energy demand, water, air, environmental-justice impacts, and noise are the five areas where post-moratorium New York projects should expect substantive standards. The public comment window is the one lever developers control during the pause. Use it.

Is New York banning data centers?

No. EO 62 is a temporary permit pause on new hyperscale (≥50 MW) projects while standards are written — not a prohibition. Applications already deemed complete proceed, sub-50 MW facilities are untouched, the four primary-use exemptions are broad, and the order lifts once the final GEIS is submitted.

Some of the loudest coverage got this wrong — including headlines framing the order as a “ban” (CNBC). The accurate description is a conditional, milestone-limited pause on one category of state permit issuance for one class of facility. It creates no penalties; a covered project that proceeded without a required DEC permit would face ordinary ECL permit-enforcement exposure, exactly as it would have on July 13. What the order actually does is sequence: framework first, then permits under the framework. Whether that sequencing costs New York projects is the live business question — contractors say fast-moving projects will not wait a year (Construction Dive) — but “ban” is not what the instrument says.

What is the Community Investment Framework and when is it due?

Within 60 days of the July 14 order — approximately September 12, 2026 — Empire State Development must publish a Community Investment Framework, and an outline is already posted for public feedback. It is guidance to help localities negotiate benefits from data-center deals: community investment funds, local infrastructure, prevailing-wage and project-labor-agreement standards, local hiring, and transparency reporting.

The CIF is not a permit requirement — it is a negotiating baseline. But its practical effect on project economics is direct: once the state publishes an expectations document, localities will negotiate against it, and community-benefit terms that were bespoke deal points become table stakes. Developers modeling New York projects should treat the CIF’s categories — investment funds, infrastructure contributions, labor standards, local hiring, reporting — as line items in the post-moratorium cost stack. The feedback window on the outline is open now, which makes this the second public process (alongside the GEIS) where operators can shape the rules they will later build under, rather than reading them for the first time in a term sheet.

Will data centers pay more for electricity in New York?

That is the direction of travel. EO 62 directs DPS to consider a Grid Acceleration Fund requiring upfront capital contributions from large loads, demand-response participation, clean-supply procurement, and an insurance pool against stranded assets — layered on top of the Energize NY proceeding, which directs the PSC to make large loads pay their fair share or supply their own power.

None of these mechanisms is finalized, and that distinction matters for underwriting: the Grid Acceleration Fund is something DPS must “consider,” not a levy in effect. But the through-line across Energize NY rate classification, the fund concept, and the EO’s ratepayer framing is consistent — New York intends large computing loads to carry their own grid costs rather than socializing them. The EO also stands up a Data Center Interconnection Working Group within 60 days and requires a DPS report on transmission-owner study practices within 90 days (approximately October 12, 2026), which will shape how interconnection studies for large loads are run. Model New York power costs with a beneficiary-pays regime as the base case.

What did the order change about water use?

Nothing immediately — it ordered a review. EO 62 directs DEC to assess whether its water-withdrawal program rules (6 NYCRR Parts 601 and 602) adequately capture large-user demands like data-center cooling, and to deliver a report with recommended regulatory or policy changes within 12 months — by approximately July 14, 2027. Water impacts are also within the GEIS scope.

So today’s water-withdrawal permitting in New York runs under the same 6 NYCRR 601/602 rules it did in June; the change is that those rules are now under formal review with data-center cooling demand as the stated reason. That mirrors a national pattern: water for large computing loads is governed state by state, with no single federal permit and fast-moving state legislation — with multiple states enacting new data-center water legislation in their 2026 sessions. If water is on your siting checklist, our breakdown of how data center water permitting actually works state by state covers the permit map in detail. For New York specifically, watch the DEC report: recommended changes to withdrawal thresholds or permit conditions land right as the moratorium lifts.

Why did New York pause data center permits now?

Load growth. EO 62’s own recitals cite nearly 12 GW of data-center load requests in the NYISO interconnection queue as of May 2026 — more than 8 GW of it entering in 2025 alone (EO 62). The order frames the pause as protecting ratepayers from funding speculative transmission buildout while protecting water, air, and grid reliability as standards catch up.

The interconnection-queue math explains the politics better than any ideological framing. When 12 GW of requested load lands on a system in roughly 18 months, someone pays for the transmission studies and upgrades that follow — and a meaningful share of queue requests never become built projects, which is the “speculative buildout” the recitals target. Whether a pause is the right response is contested: the construction industry argues the projects and their jobs will simply land in other states (Construction Dive), and no other state has followed New York’s lead. But the driver named in the order itself is grid and ratepayer arithmetic, not hostility to the industry.

Are other states doing the same thing?

No — New York is explicitly first, per the Governor’s announcement, and as of mid-July 2026 no other state has a statewide moratorium. The competitive counter-current is real: most states are still recruiting hyperscale projects with incentives, while local-level pauses and utility-rate fights exist in multiple states.

For multi-state operators, the honest read is a split map. Kansas, Missouri, Oklahoma, Texas, and Nebraska — the markets we work most — remain active recruitment states with no comparable instrument. At the same time, the components of EO 62 travel well: GEIS-derived siting standards, community-benefit frameworks, and beneficiary-pays cost allocation are exactly the instruments other states’ regulators and legislatures will study, particularly where local water and rate fights are already live. The planning posture that holds up: treat New York as the strictest-case preview of the regulatory stack, not the norm — and assume pieces of it will be borrowed piecemeal, state by state, on no predictable schedule. The template risk is real even where the moratorium is not.

What should a multi-state data center operator do right now?

Five moves, drawn from the compliance requirements in EO 62: confirm the completeness status of any pending New York DEC applications; screen every project against the §6 definition and exemptions; file comments in the GEIS and Community Investment Framework processes; model post-moratorium economics; and re-sequence multi-state siting plans around the up-to-12-month New York pause.

Two of those deserve emphasis. First, the completeness lesson generalizes beyond New York: a July 14 line now divides projects that proceed from projects that wait up to a year, based entirely on whether DEC had deemed the application complete. Application quality is a strategic asset — a deficient submittal can cost you a regulatory window you did not know was closing, in any state. Second, model the full post-moratorium cost stack with appropriate caution about what is and is not law: the Responsible Data Center Development Act has passed both houses but remains unsigned, and the proposed repeal of sales-tax exemptions for large data centers is announced intent only — neither is enacted. Track what actually becomes law, not the press-release version. And remember the environmental permit stack extends past the moratorium’s subject matter — backup generator fleets carry their own air permit requirements that scale sharply at campus size, in New York and everywhere else.

The siting takeaway

New York just demonstrated that a state can freeze a permitting pathway for a whole asset class with 60 days’ worth of recitals and an executive signature — and that the difference between a stalled project and a proceeding one can come down to whether an application was deemed complete on a specific Tuesday. For facility planners running sites in multiple states, that is the operational lesson: the regulatory ground under a siting decision moves faster than a development timeline, and permit-application discipline is what buys you the benefit of the doubt when it does.

That is the work iSi does for multi-site operators: environmental permitting and compliance support across 40 states — tracking which instruments are law versus announced intent, keeping application packages complete and defensible, and building the state-by-state permit map before land is optioned rather than after. If your siting pipeline touches more than one state’s environmental agency, our environmental compliance services team can put the full permit picture — air, water, waste, and the state-specific overlays — in front of you before the next window closes. Call (316) 264-7050 to talk through your project list.

Sources

Tags: