What a zero-water cooling claim should tell a host community
Microsoft’s newer cooling designs sharpen an important distinction: water circulated inside a system is different from water consumed in operation.
Image: AI-generated editorial illustration, not a photograph of a specific project.
INFRADAY ANALYSIS
A planning board reviewing a data center needs more than an annual water estimate. It needs to know where the water goes, when demand peaks and which parts of the facility the estimate actually covers.
In a June 2026 update, Microsoft described a design introduced in 2024 that recirculates water in a closed-loop, direct-to-chip system without evaporating it for cooling. The company says this design consumes zero water for cooling during operations. Its account also distinguishes that approach from cooling towers, hybrid equipment and other systems used across its existing fleet.
The wording matters. The claim concerns operational cooling at facilities using that design. It should not be read as a statement that every Microsoft site, every construction activity or every source of electricity has no water requirement.
Ask for the boundary around the number
For host communities, a useful submission would separate initial system filling, routine cooling consumption, domestic use and any other site demand. It should also distinguish withdrawals from consumption, rather than using the terms interchangeably.
Infraday’s recommendation is to publish the assumptions alongside the headline figure. The proposed cooling design, expected operating conditions and expansion phases should be understandable without requiring residents to interpret an engineering model.
A community should also ask how performance will be measured once the building is occupied. A design estimate and an operating record serve different purposes. A defined reporting schedule can show whether the project is performing as described and explain changes as additional capacity enters service.
Put the hot-day question on the table
Annual averages can conceal the conditions residents care about most. Local review should ask what the facility expects to draw on a very hot day, whether any alternate operating mode changes that demand, and who verifies the answer.
The electricity implications should sit beside the water discussion. The purpose is to understand the selected system as a whole, including how its operating choices fit local infrastructure constraints.
Water-saving designs deserve close attention because they can change the conversation about siting. The most useful promise, however, is one that a host community can trace from the design documents to a meter and a published operating result.
Sources: Microsoft, water intensity and cooling design update, June 24, 2026.
Based on the public sources linked above, reviewed September 27, 2026. Project schedules and company commitments are attributed to their issuers; analysis and recommendations are Infraday’s.