Washington Data Centers Face Local Limits

Spokane County moved from considering a moratorium to approving a temporary pause on data-center building permits, extending formal restrictions beyond Spokane city. The story also more clearly identifies Microsoft as a major Quincy operator and frames Avista’s proposal as nonbinding.

The story has broadened beyond Spokane and Seattle to show system-level grid constraints and infrastructure costs in Washington’s established data center hub, Quincy. The emerging issue is no longer only whether projects receive permits, but whether utilities can accommodate them and recover expansion costs.

• Quincy data centers use about 37% of Grant County PUD’s generation.
• Grant County PUD is planning $260 million in transmission upgrades.
• Transmission constraints are slowing new data center construction in Quincy.
• Medical Lake developers face calls for a county moratorium.
• Water questions now include wells, treated wastewater, and cooling demand.

The main shift is framing: the Spokane dispute is now presented as part of a broader wave of local policy reactions, with Seattle’s similar moratorium indicating concern is spreading beyond the original jurisdiction. The Avista and Spokane actions themselves are otherwise largely reinforced rather than materially changed.

The story has moved from a general pause around a 500-megawatt proposal to concrete local regulatory action, with Spokane now imposing a permit moratorium and Spokane County considering its own. A key new detail is that the load may ramp up gradually from 125 MW in 2029 to 500 MW by 2032, sharpening concerns about when infrastructure and water impacts would hit.

• Proposed electricity demand could start at 125 MW in 2029.
• The load could grow to 500 MW by 2032.
• Spokane adopted a one-year moratorium on data center permit applications.
• Spokane County proposed a nine-month county permit moratorium.
• Seattle paused approval of data centers larger than 20 MW.

The story has sharpened from a broad pattern of Washington data-center scrutiny into a more specific Spokane-area pause around a proposed 500-megawatt Avista-linked project. The new emphasis is on unresolved site details, water-rights scrutiny, and whether local governments can set standards before the project advances.

• Avista paused negotiations with an unnamed 500-megawatt data center customer.
• Spokane City Council considered a one-year moratorium on new data center construction.
• Mead-area site references appeared in marketing materials.
• Washington Department of Ecology cited water-rights requirements for well-based supply claims.
• Spokane Riverkeeper entered the story with water and environmental concerns.

The story has broadened from Avista’s paused Spokane negotiation into a wider Washington policy response, with Seattle and Spokane both moving toward temporary restrictions on larger data center development. The main new development is that local governments and utilities are now actively shaping rules around power, water, and infrastructure cost allocation rather than just debating one proposed project.

• Seattle City Council moved toward a one-year moratorium on larger data centers.
• Seattle City Light warned about rising load and constrained supply.
• Water rights proof and permitting are now part of the review process.
• Avista is slowing negotiations for a 500-megawatt project.
• Local resistance now includes both utilities and city councils.

Avista has paused negotiations over a proposed large data center load while it seeks broader policy, regulatory, and community alignment. The dispute has drawn local opposition over electricity demand, water use, infrastructure impacts, and whether new costs would be kept off existing ratepayers. The situation now sits at the intersection of utility planning, municipal regulation, and public scrutiny of hyperscale data center development.