Michigan Data Centers: The State Picture

The grid advantage. The I-96 corridor through Kent, Ottawa, and Allegan counties has available substation capacity that coastal markets exhausted years ago. Consumers Energy and DTE have not yet faced the interconnection queues that are blocking projects in Northern Virginia and the Phoenix metro. That window is finite — large loads accelerate queue formation.

The water advantage. Michigan sits atop the Great Lakes, the largest surface freshwater system on Earth. Data center cooling is water-intensive. This is attractive to developers and raises legitimate concerns for residents and environmental advocates under the Great Lakes Compact (MCL §324.32701).

The land advantage. Industrial-zoned parcels in West Michigan townships are available at price points that make comparable coastal land uneconomical. With greenfield land available, developers can design purpose-built campuses rather than retrofitting existing industrial space.

The zoning gap. None of the townships receiving applications had data center–specific zoning standards. The Michigan Zoning Enabling Act (PA 110 of 2006) gives townships broad authority to write such standards — but the state has provided no model ordinance, no guidance, and no framework. Every community is starting from scratch.

Sources: Consumers Energy grid planning reports; Michigan Great Lakes Compact (MCL §324.32701); Bridge Michigan (April 2026); MIRS Michigan Information & Research Service.

The term “data center” covers facilities ranging from a converted warehouse to a multi-building campus drawing 400+ megawatts. The applications arriving in Michigan townships are at the large end.

The Gaines Township application (Microsoft subsidiary): The application involves a multi-building campus on industrially zoned land near the I-196/I-96 corridor. The specific power load and water use figures were not publicly disclosed in available permit materials as of April 2026. Comparable Microsoft campuses in other markets draw 100–300 MW.

For context — what 100–300 MW means locally:

• The City of Grand Rapids’s entire residential load is roughly 200–250 MW at peak. A single hyperscale campus can match or exceed that figure.
• A 200 MW facility requires a dedicated substation and transmission line upgrade. In Michigan, that infrastructure is built and owned by Consumers Energy — and its cost is recovered through rate cases that affect all ratepayers in the service territory.
• Water cooling for a 100 MW facility consumes 1–3 million gallons per day depending on cooling technology. That volume triggers Michigan’s Water Withdrawal Assessment Process under the Great Lakes Compact (MCL §324.32701).

Construction footprint: A hyperscale campus typically requires 100–500 acres of industrially zoned land. Buildings are 1–4 stories, with significant outdoor cooling infrastructure (cooling towers, generator pads, transformer yards). Visual and noise impact extends well beyond the property line.

What townships are actually reviewing: Most Michigan townships receiving applications have never reviewed a use like this. Their industrial zoning was written for manufacturing plants, warehouses, and distribution centers — uses with workers, trucks, and regular activity. A data center has almost no on-site employees after construction and almost no truck traffic, but its infrastructure footprint is larger and its utility demands are far higher than any prior industrial tenant.

Sources: Microsoft data center infrastructure disclosures; FERC load data; Michigan Water Withdrawal Assessment Tool (EGLE); Gaines Township permit application materials (partially available).

By April 2026, Bridge Michigan reported at least 19 Michigan communities pausing or actively considering a pause on data center permits. The pattern crosses county lines and township types:

Why the clustering? West Michigan’s concentration reflects the I-96/I-196 corridor — industrially zoned land, Consumers Energy substation capacity, and fiber infrastructure. Site selectors target contiguous options, so a pause in one township pushes developer attention to its neighbors. That neighbor-pressure dynamic is new, and most townships have not thought through how to coordinate.

The legal floor: Every community that pauses is implicitly saying the same thing: our zoning code was not written for this use. PA 110’s moratorium provision is only valid if the township is actively writing new standards. A pause for any other reason — community opposition, political pressure, or general uncertainty — is legally indefensible and invites litigation under MCL §125.3604.

Sources: Bridge Michigan (April 2026); MIRS Michigan Information & Research Service; Cascade Township Ordinance No. 002 of 2026.

Every known proposed or pending data center in Michigan being tracked as of April 2026. This list focuses on active permit applications and moratorium actions — not hyperscale campuses already built and operating. Updated as new permit actions are confirmed.

Michigan is a Great Lakes Compact signatory state (MCL §324.32701). The Compact gives Michigan unusually strong legal tools to protect its water resources — including mechanisms to restrict water withdrawals that would harm the basin. But Compact protections are state-level and aggregate. They do not automatically give a township the ability to impose a local water use cap on a specific data center permit.

To enforce local water use limits, a township needs to write those limits into its zoning code before issuing a permit. A data center that is permitted without binding water use standards in the permit conditions cannot be ordered to reduce consumption after construction — the township’s only option is a lawsuit against a multi-billion-dollar company with more legal resources than the township will ever have.

The Cascade Township moratorium is specifically designed to give the Planning Commission time to write water use standards into the permanent data center zoning ordinance. That ordinance will be the first locally drafted data center water standard in Kent County.

Sources: Michigan Great Lakes Compact (MCL §324.32701 et seq.); Cascade Township Ordinance No. 002 of 2026; Arizona DEQ water guidance.

A 100 MW data center campus draws as much power as a mid-sized American city’s residential load. That power must be delivered through dedicated substation infrastructure. In Michigan, that means Consumers Energy (West Michigan) or DTE (Southeast Michigan) must build and recover the cost of new infrastructure.

As of April 2026, neither Consumers Energy nor DTE had published specific data center load projections or disclosed how pending applications would affect their infrastructure plans or rate cases. In Virginia, Dominion Energy’s data center load growth contributed to a significant rate hike request that affected all residential customers. That story is worth watching in Michigan before large facilities are permitted.

The key question for any Michigan community approving a large data center: who pays for the substation? If the utility absorbs the cost, ratepayers across the service territory pay. If the developer pays, that cost may influence location and design decisions. Most townships have never had to negotiate this before.

Sources: Virginia SCC rate case filings; Michigan Public Service Commission proceedings; Consumers Energy annual reports.

The central irony of the Michigan data center moment: Michigan’s Zoning Enabling Act (PA 110 of 2006) gives townships unusually strong legal authority to set land use rules for new categories of development. Townships can write performance standards for noise, water use, lighting, setbacks, and energy source. They can require disclosure. They can define data centers as a conditional use requiring a special use permit.

What PA 110 doesn’t do: tell townships what to write. And unlike Virginia, Texas, or Arizona, Michigan has never issued model ordinance language, statewide performance standards, or even an advisory guide for townships facing first-time data center applications.

The result is a township-by-township patchwork. One community approves with water restrictions. A neighbor approves with none. A third pauses entirely. A fourth rejects outright. Neighboring townships draw from the same water table, connect to the same grid, and share roads — but there is no coordination mechanism.

Cascade Township’s ordinance work is the closest thing Michigan has to a model right now. The Planning Commission began drafting in March 2026 with a 12-month clock. Their output will be the first locally-written data center performance standard in Kent County — and likely a reference document for every other Michigan township that hasn’t voted yet.

Primary source: Michigan Compiled Laws §125.3101 et seq. (Zoning Enabling Act, PA 110 of 2006); Cascade Township Ordinance No. 002 of 2026; HB 5814 (Michigan Legislature, 2026).

As of April 2026, Michigan has no statewide data center development framework — no model ordinance, no mandatory disclosure requirements, no coordinated guidance from the state to townships about what standards to write. This is the policy vacuum that makes each community’s permit decision harder and more consequential than it needs to be.

What the state is doing:

• MEDC recruitment: The Michigan Economic Development Corporation has listed AI data center infrastructure as a strategic investment priority. MEDC offers site selection assistance and connects projects to state incentive programs. This recruitment activity is occurring simultaneously with townships writing rules from scratch — there is no formal coordination mechanism.
• EGLE guidance development: The Department of Environment, Great Lakes, and Energy is developing supplemental guidance on how the Water Withdrawal Assessment Program applies to data center cooling water use under the Great Lakes Compact. This guidance interprets existing law; it does not create new local enforcement authority.
• Michigan PSC inquiry (Case U-22103): The Public Service Commission opened an inquiry into the grid and ratepayer implications of large data center loads for Consumers Energy and DTE customers. The proceeding will determine how infrastructure upgrade costs are allocated — a decision that affects every Michigan utility ratepayer, not just host communities.
• Gov. Whitmer Executive Order 2026-03: Directs state agencies to streamline permitting for AI infrastructure projects. Does not create zoning standards or provide model ordinances to townships.

What the state is not doing:

• No model data center zoning ordinance has been provided to the 1,240+ townships in Michigan.
• No mandatory disclosure requirements for data center energy or water use exist at the state level.
• No inter-township coordination mechanism exists for communities that share water, grid, and infrastructure resources.
• No independent economic review requirement for developer-submitted impact studies.

What the Legislature is considering: HB 5814, introduced by Rep. Skaggs, would direct LARA to develop a model data center zoning ordinance for townships. The bill is in committee. If it passes, it would not require townships to adopt the model but would give communities a starting point. The bill has bipartisan interest — conservative townships wanting local control and progressive members concerned about environmental standards share an interest in giving communities better tools.

Sources: MEDC Strategic Investment Program documentation; EGLE Water Withdrawal Assessment Program (Michigan.gov/EGLE); Michigan PSC Case U-22103; HB 5814 (Michigan Legislature, 2026).

The most consequential financial question that doesn’t appear in a permit application: who pays for the electrical infrastructure a data center requires?

A 100–300 MW hyperscale campus requires a dedicated substation and transmission line upgrades that don’t exist on the I-96 corridor today. Consumers Energy would need to build that infrastructure. In Michigan’s regulated utility model, Consumers Energy recovers infrastructure costs through rate cases before the Michigan Public Service Commission — proceedings in which the cost is spread across the utility’s entire service territory, including all residential and business customers in West Michigan.

In practical terms: if Consumers Energy builds a new $50–150 million substation to serve a data center campus and recovers that cost through rates, West Michigan homeowners and small businesses pay for it through marginally higher electric bills over 20–30 years — whether or not the data center benefits their community.

What the Virginia precedent shows: Dominion Energy’s rate increase request in Virginia explicitly cited data center load growth as a contributing factor. Virginia’s State Corporation Commission approved a portion of the request. Residential ratepayers in Northern Virginia are now paying for grid infrastructure built for data centers — infrastructure that also provides some broader grid benefit, but whose primary driver was large commercial loads.

What Michigan communities should be asking:

• Has Consumers Energy submitted a load interconnection study for the Gaines Township application? What infrastructure is required and what does it cost?
• Is the developer (Microsoft) paying for grid infrastructure as part of the project, or will it enter the Consumers Energy rate base?
• Has the Michigan PSC been notified of this application, and has it assessed the ratepayer implications?
• What is Consumers Energy’s current interconnection queue, and how does a 100–300 MW load affect its capacity planning?

None of these questions have been publicly answered for the Gaines Township application as of April 14, 2026.

Sources: Dominion Energy SCC rate case filings (Virginia, 2024–2025); Michigan PSC Case U-22103; Consumers Energy annual report (2025); FERC interconnection filing data.

The Debatable government dashboard tracks the Michigan data center debate across local, state, and federal levels — including upcoming meetings, state legislation, PSC proceedings, and federal bills. Enter your zip code to see your specific representatives and their positions.

The dashboard is free, works offline, and doesn’t require an account to read. It pulls from the same primary source documents linked throughout this page.