17JUN

Virginia forces water draw into daylight

2 min read

10:13UTC

A new Virginia law will make water utilities report data-centre use separately from 2027, landing as Google fights to keep one Botetourt County site's draw sealed after a court forced its release.

← Back to Virginia taxes the backup, not the draw Jump to analysis ↓

IndustryDeveloping

Key takeaway

Virginia will make utilities publish data-centre water draw, closing the gap voluntary disclosure leaves open.

A new Virginia law, reported on 25 June and prospective to 2027, will require waterworks to break out data-centre sales from household and industrial customers, ending the aggregation that has hidden site-level draw. ¹ A utility that today reports one lumped figure will have to name what its data centres take.

The mandate lands on an awkward record. Google markets itself as the only hyperscaler that publishes per-site water figures, yet its Botetourt County subsidiary spent months fighting a freedom-of-information request for that exact site data, needing a November 2025 court order to release it. ² A Google director had argued in an affidavit that the numbers could let rivals infer the campus's size and design. The figures a judge finally prised loose, a draw rising from 2 to 8 million gallons a day, 7 to 30 times the utility's largest existing customer, never appeared in Google's own sustainability report.

The company had earlier answered the water question on its own terms, pledging $17m in replenishment as its Dalles, Oregon site faced a steep rate rise . That is the gap the law closes. Voluntary disclosure lets an operator choose the framing, the baseline and the offset; a statutory per-class report does not. Google's Botetourt fight shows what a company will do to keep a single site's number sealed even while branding itself the transparent one, which is why the 2027 mandate matters more than any pledge.

Deep Analysis

In plain English

Starting in 2027, Virginia's water companies will have to say exactly how much water data centres are using, separately from homes and factories. Right now that number gets lumped in with everyone else's, so nobody outside the company can see one site's actual draw. The law arrives just as Google has been fighting in court to keep exactly that kind of number secret for one of its Virginia sites, even though the company publishes its own water figures elsewhere, on its own terms, whenever it chooses.

Deep Analysis

Root Causes

The disclosure gap exists because water utilities have historically billed data centres inside an aggregated industrial-customer class, so no single invoice ever isolated one campus's draw; Virginia's law is a billing-classification fix, not a new water right or a discharge limit, which is why it took a legislative change rather than a permit condition to close it.

Google's Botetourt objection rested on a specific competitive-harm theory, that a precise gallons-per-day figure lets rivals infer a campus's size and cooling architecture, a concern its own voluntary aggregate reporting was structured specifically to avoid triggering.

What could happen next?

Consequence
Utility-level reporting from 2027 will let Virginia regulators and journalists compare data-centre water draw across sites for the first time, ending the aggregation that let voluntary corporate figures go unchecked.
Precedent
Other water-stressed states can adopt the same utility-reporting mechanism without waiting for a hyperscaler to volunteer site-level data.

Source Landscape

This story draws on neutral-leaning sources

Primary parallel: Microsoft's Racine, Wisconsin development agreement carried a non-disclosure clause covering community-impact data that only broke when Milwaukee Riverkeeper sued for the records, releasing a figure of 8 million gallons a year for the site's first phase; Google's Botetourt fight follows the identical pattern, litigation as the only route past a corporate non-disclosure posture.

Counter-parallel: Amazon has published no comparable electricity figures at all for any US site, so Virginia's new law, which binds water utilities rather than the operators directly, may prove the more durable transparency mechanism precisely because it does not depend on any single hyperscaler agreeing to disclose.

Consensus view: Lawrence Berkeley National Laboratory's (LBNL) national data-centre water-use research treats utility-verified, site-level reporting as the only reliable way to reconcile corporate sustainability claims against actual local draw, since self-reported aggregate figures let a company choose its own baseline and boundary.

Counter-view: Google's own sustainability reporting frames per-site publication as insufficient on its own, arguing a bare gallons-per-day figure without local hydrological context invites exactly the competitive-harm objection it raised in its Botetourt affidavit; the company presents its Oregon-style replenishment pledges as the more actionable disclosure.

Key tension: Whether mandatory utility-level reporting from 2027 forces the comparability Google's voluntary figures don't provide, or whether operators simply route disputed sites through the same competitive-harm objection that already took a court order to overcome once.

Sources:VPM·Roanoke Rambler

Mentions:Virginia →Google →Boone County →Milwaukee Riverkeeper →Racine →Lawrence →Oregon →Wisconsin →Microsoft →Amazon →

First Reported In

Update #9 · US data-centre backlash becomes law

VPM· 7 Jul 2026

Read original →

Causes and effects

Caused by

Google prices its water ahead of rules

Extends Google's water-transparency posture from the Dalles pledge to the Botetourt disclosure fight.

Occurred 3 Jun 2026

Read story →

This Event

Virginia forces water draw into daylight

Statutory per-class reporting removes the aggregation that lets operators publish flattering company-wide figures while site-level draw stays hidden.

Different Perspectives

Government of Odisha

Odisha signed a $1.5bn agreement with HCLTech and Sarvam AI on 24 July for a sovereign AI data centre in Bhubaneswar, targeting 2028 operations. While regulators elsewhere price developers out of the queue, Odisha is bidding state financial assistance to bring capacity in, betting the AI infrastructure boom is worth courting rather than rationing.

Switch Datacenters and Uithoorn

The developer, the municipality, Liander and dozens of greenhouse growers signed a waste-heat agreement letting a 60 MVA facility proceed under a provincial rule that bans sites above 5 MVA. The public-interest exception argues the site relieves rather than adds to grid congestion, working around a standing ban from inside rather than waiting for it to change.

Iskandar Puteri residents

Residents protested in February over falling water pressure they attribute to ZDATA's 300 MW construction; ZDATA disputes causation and has not yet resolved the dispute with its wastewater-only pivot. The complaint sits unadjudicated while the operator advertises compliance to state authorities the residents cannot address directly.

Microsoft

DC Byte reports Microsoft looking to the Nordics for new capacity while Dublin's regional share falls to 15 per cent, though this is a market-intelligence inference rather than a company statement. Microsoft keeps its existing Dublin cloud region, which is costly to relocate, while directing new investment where power is cheaper and the queue is shorter.

ISO New England

ISO-NE proposed excluding new large loads from its Installed Capacity Requirement entirely, forcing data centres to bring their own generation or accept curtailment, even though New England's demand has been flat or falling for a decade. The reform is pre-emptive, written before the region has felt the strain PJM and MISO already report.

Ofgem

Ofgem opened its Data Centre Commitment Fee consultation on 29 July, arguing that free options on grid capacity let developers bank places on ten sites and abandon nine, crowding out projects that would build. It expects the deposit to filter the queue before the rule even takes final form.