Augusta Twp., Mason confront limits of local control as state paves way for data centers

Michigan communities facing a surge of hyperscale data center proposals are discovering the limits of local control under the Michigan Zoning Enabling Act.

While state law prevents townships from outright banning data centers, AI-driven demand and state tax incentives are fueling proposals—leaving townships and cities with limited time and resources to regulate this new type of resource-intensive facility while attempting to manage strained public relations.

Enacted as 2006 PA 110, the MZEA governs how cities, villages, and townships can regulate land use. Its key exclusionary zoning provision is straightforward yet restrictive: a zoning ordinance or decision “shall not have the effect of totally prohibiting” a lawful land use if there is a “demonstrated need” for it in the locality or the surrounding area within the state. According to legal experts at Fahey Schultz Burzych Rhodes, this means townships and cities cannot outright ban data centers, which developers and state incentives increasingly frame as essential infrastructure for AI and cloud computing.

Local governments can, however, regulate where such facilities go, impose performance standards on noise, water use, energy demands, setbacks, and environmental impacts, or require special use permits and site plan reviews. The law forces communities to balance economic development pressures against rural character, infrastructure strain, and resident quality of life—often sparking heated debates and citizen referendums.

Recent examples illustrate the difference in how two townships have tried to navigate these constraints—and how residents have pushed back.

In Augusta Charter Township, the board unanimously approved Ordinance No. 2025-02 in July 2025. The measure conditionally rezoned seven parcels totaling 522.2 acres from Agricultural Residential to General Industrial to specifically accommodate a proposed $1 billion Thor Equities hyperscale AI data center campus on roughly 810-acres. Twelve other parcels were already zoned GI. The ordinance included a key condition limiting the rezoned land exclusively to data center and ancillary uses, along with basic parameters like substation height caps and some landscaping requirements.

Critics, including the planning commission – which recommended a denial in a 5-1 vote – argued it effectively greenlit the massive industrial development on farmland and wetlands without robust, data-center-specific safeguards. Residents, led by the grassroots group Protect Augusta Charter Township or PACT, have since gathered 957 signatures, forcing a veto referendum. Residents will now have an opportunity to vote against the ordinance on the August 4, 2026, ballot.

A “No” vote would repeal the rezoning and keep the parcels zoned for Agricultural use, blocking the project as currently proposed without creating a township-wide ban.

By contrast, Mason officials took a proactive regulatory approach with Ordinance 266, adopted in February 2026. The ordinance created a new classification for zoning called M-3 Technology Innovation, which specifically tailored standards to handle an application for a future hyperscale data center. The standards included tighter rules on noise, emissions, visual screening, setbacks, and requirements for developers to prove that water, sewer, and electricity demands could be met without harming existing users.

Supporters saw it as adding stronger guardrails than default general industrial zoning—an outdated classification that applies to regular industrial buildings like a machine shop or gas station.

Yet a group, Mason Data Center Facts, collected enough signatures for a referendum, arguing the ordinance was vague, insufficiently protective, and essentially a “welcome mat” for developers. Facing the vote, the council repealed the ordinance in a 4-2 vote, mid-March 2026, reverting to less stringent underlying zoning and leaving future proposals potentially harder to constrain.

The juxtaposition highlights a common dilemma under the MZEA. Under Gov. Whitmer’s 2040 climate initiatives, the State of Michigan has increasingly centralized control over local zoning, siting, and land use. Laws such as PA 233 and PA 235, combined with Ready Renewable grants for rezoning have sacrificed local control in the pursuit of ideological goals—only leaving room for minor regulation as local officials bear the full brunt of public opinion.

Augusta’s ordinance was largely permissive—a site-specific rezoning that lowered barriers for one major project while relying on conditional use limits rather than comprehensive performance standards. Meanwhile, the Mason ordinance attempted to be proactive and stricter by crafting a dedicated classification with detailed operational controls to mitigate future projects.

        [
            Facebook
        ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.themidwesterner.news%2F2026%2F03%2Faugusta-twp-mason-confront-limits-of-local-control-as-state-paves-way-for-data-centers%2F)
    
    
        [
            
        ](https://twitter.com/intent/tweet?text=Augusta Twp., Mason confront limits of local control as state paves way for data centers&url=https%3A%2F%2Fwww.themidwesterner.news%2F2026%2F03%2Faugusta-twp-mason-confront-limits-of-local-control-as-state-paves-way-for-data-centers%2F)
    
    
        [
            
                
            
        ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.themidwesterner.news%2F2026%2F03%2Faugusta-twp-mason-confront-limits-of-local-control-as-state-paves-way-for-data-centers%2F)
    
    
        [                
                
                
                
            
        ](mailto:?subject=Augusta Twp., Mason confront limits of local control as state paves way for data centers&body=https%3A%2F%2Fwww.themidwesterner.news%2F2026%2F03%2Faugusta-twp-mason-confront-limits-of-local-control-as-state-paves-way-for-data-centers%2F)
    
    
        [
            
                
            
        ](javascript:void(0);)