Microsoft CEO Satya Nadella stood on stage at Build 2026 and made a striking claim: the company’s newest AI data centers use so little water annually that the consumption is roughly equivalent to a single restaurant. “The cooling loop is filled once, and the data center can operate effectively with zero water consumption,” he said. It’s a genuinely appealing pitch to communities worried about a new data center draining their local water supply. It’s also, on close inspection, a claim doing a lot of quiet work to sound bigger than it actually is.
WHAT’S REAL ABOUT IT
Closed-loop cooling is a legitimate engineering improvement, not a scam. Traditional data centers mostly rely on open-loop evaporative cooling: water passes over server heat, evaporates into the air carrying that heat away, and has to be continuously replaced — the “millions of gallons a year” figure you hear associated with hyperscale facilities comes from this constant water loss to evaporation. Closed-loop systems work differently: water (or coolant) is sealed in pipes, circulates past server racks, and returns to be re-cooled and recirculated rather than evaporated away. According to the Florida Water and Pollution Control Operators Association and water-monitoring firm KETOS, this genuinely can cut freshwater consumption by up to 70% compared to open evaporative systems — a real, meaningful, independently-corroborated number, not just a marketing figure.
WHERE THE “ZERO WATER” FRAMING STARTS TO CRACK
Here’s the first honest caveat, straight from industry sourcing: closed-loop systems aren’t actually zero-loss. They require periodic “makeup water” additions to replace what’s lost to small leaks, evaporation at the cooling-tower stage, and system maintenance — the FWPCOA’s own explainer notes water losses are “minimal” but explicitly not zero, “with some makeup water added occasionally.” “Up to 70% less” and “zero consumption” are two very different claims, and Nadella’s language leaned toward the more dramatic one.
Second, and more substantively: closed-loop systems typically still rely on an outer cooling loop — a cooling tower or chiller — to get rid of the heat the inner loop absorbs. One detailed technical breakdown puts real numbers on this: that outer loop, using water cooling towers, is responsible for data centers consuming an estimated 60% of the water they withdraw industry-wide, even in facilities marketed as “closed-loop.” The inner loop that touches the servers may indeed be sealed and non-evaporative. The system as a whole, once you account for how it actually rejects heat to the outside world, frequently still isn’t water-free — it’s water-reduced.
Third: closed-loop isn’t free — it trades one resource for another. University of Utah computing professor Robert Ricci, whose Cloud Lab actually tests these systems, put it plainly: “You can burn more natural gas in order to do more compressive cooling, or you can evaporate water to do evaporative cooling. And those are the two kind of big choices.” Systems that minimize water use tend to lean harder on mechanical refrigeration — meaning more electricity, not less resource consumption overall. Reporting on Utah’s proposed 3–9 gigawatt Box Elder County facility notes the genuinely water-minimal systems being promised there are “relatively new” and “have not been tested anywhere near the scale” being proposed — meaning communities are being asked to trust a specific water-savings number at a scale nobody has actually operated it at yet.
THE PART DEVELOPERS DON’T VOLUNTEER
Critics quoted directly in Tom’s Hardware’s coverage of Nadella’s own claim made the sharpest point: even a genuinely water-minimal new facility “does not solve the consumption issue of Microsoft’s over 500 existing data centers” — most of which still run the older, thirstier evaporative systems. A single showcase facility’s efficient design doesn’t retroactively fix a company’s entire existing footprint, and “our newest building barely uses water” is a very different statement from “our company’s data center water use is under control.”
There’s also a real cost incentive shaping which claim gets made in which room. Closed-loop systems require more expensive specialized equipment upfront — which is exactly why cities like Yorkville, Illinois had to legally mandate closed-loop or equivalent systems before a developer would commit to using one voluntarily. The Shaw Local reporting on Illinois’ Project Steel and Project Cardinal data centers found local officials had to press developers directly on why they weren’t using the more efficient system by default — suggesting the water-saving pitch shows up prominently in public messaging, but doesn’t always show up as the actual engineering default until a community forces the issue.
THE ACTIONABLE TAKEAWAY FOR ORGANIZERS
When a developer’s public pitch includes “closed-loop” or “zero water consumption” language, the right response isn’t to dismiss the technology — it’s real and it does help. The right response is to ask specific, technical follow-up questions: What percentage of total facility cooling actually runs through the closed loop versus a still-evaporative outer cooling tower? What’s the annual makeup-water volume, in actual gallons, not percentages? Has this exact system been operated at this exact scale anywhere else, or is this facility the pilot? And critically: is the water-saving design a binding permit condition, or just a stated intention that could quietly change during construction? Communities that got the strongest protections — like Yorkville — got them by writing the water limits into the approval agreement itself, not by trusting the press release.