MN — Power Infrastructure Updated 2026-07-17

Minnesota

MISO Solar Wind Storage Transmission Constraints

Research date: July 17, 2026

1) Grid operator and market context

2) MISO interconnection queue and transmission planning

  • MISO’s generator-interconnection queue remains the relevant queue for wind, solar, storage, and dispatchable resources that may be paired with new data center load, but it is not itself a queue for retail data center interconnections (MISO Generator Interconnection, accessed 2026-07-17).
  • MISO’s long-range transmission planning and MTEP processes continue to matter for Minnesota because large loads can drive the need for new generation deliverability, regional transfer capacity, and local network upgrades (MISO MTEP, accessed 2026-07-17; MISO LRTP Tranche 2.1, accessed 2026-07-17).
  • MISO large-load framework remains under development, not final. MISO continued a footprint-wide large-load initiative in 2026, including a February proposal to define a “large load” as a single-site load above 50 MW, an April long-term load-forecast workshop focused more heavily on data centers and advanced manufacturing, and a June proposal for staged firm-service increases. These remain regional proposals and stakeholder processes rather than a final Minnesota-specific interconnection rule (MISO, 2026-02-25; MISO, 2026-04-13; MISO, 2026-06-10).
  • Forecast uncertainty is an explicit regional issue. MISO’s 2026 workshops solicited methods for incorporating prospective large loads while avoiding double counting and accounting for behind-the-meter generation and uncertain energization schedules; the resulting framework remained active as of July 17 (MISO, 2026-02-23; MISO, accessed 2026-07-17).

3) Ratepayer protection, tariffs, and PUC proceedings

  • Minnesota’s 2025 very-large-customer statutes require special treatment for large loads of at least 100 MW and direct the PUC to address cost allocation so that incremental costs caused by those customers are not shifted to other ratepayers (Minnesota Statutes 216B.1622, accessed 2026-07-17; Minnesota Statutes 216B.1623, accessed 2026-07-17).
  • On May 18, the PUC approved a standalone Xcel class for customers at or above 100 MW and certain 20-100 MW “system intensive” customers. The default contract term is 15 years, customers generally face an 80 percent minimum bill and 80 percent early-exit obligation, and all transmission and distribution upgrades are funded through contributions in aid of construction; incremental revenue beyond incremental cost benefits the rest of the class (Minnesota Public Utilities Commission, 2026-05-18).
  • The Commission also required Xcel to propose a voluntary clean-energy tariff by December 1, 2026 so very large customers may contract for clean resources without shifting costs to other customers (Minnesota Department of Commerce, 2026-05-18).
  • Pine Island Google/Xcel ESA, E-002/M-26-170. Xcel filed a 15-year ESA on April 14 with confidential total demand, a clean-energy adjustment clause, a minimum bill, and cost-protection terms. Xcel estimates $1.1 billion in net benefits for other customers and says initial service depends on completion of one of two 345 kV transmission lines to North Rochester. The matter remained pending as of July 17 (Minnesota Public Utilities Commission, 2026-05-05; Minnesota Public Utilities Commission, accessed 2026-07-17).
  • Hermantown Google/Minnesota Power ESA, E-015/M-26-159. Minnesota Power filed a 15-year ESA on March 26 under its Large Power schedule. The filing places transmission-upgrade costs in a Facilities Construction Agreement and ties the load to 300 MW of wind, 400 MW of storage, and a $5 million Google contribution; Minnesota Power estimates $600 million-$800 million in benefits to existing customers over 15 years. The matter remained pending as of July 17 (Minnesota Public Utilities Commission, 2026-04-07; Minnesota Public Utilities Commission, accessed 2026-07-17).
  • Minnesota Power tariff proposal, E-015/M-26-126. Minnesota Power initially proposed serving very large customers through its existing Large Power class without underlying rate-design changes, then asked to withdraw the petition without prejudice. The PUC placed the withdrawal request on its June 25 decision agenda; because published online minutes and an action result were unavailable as of July 17, the original filing should not be treated as an approved tariff (Minnesota Public Utilities Commission, 2026-03-03; Minnesota Public Utilities Commission, 2026-06-25).
  • Other utility filings. Otter Tail Power’s proposed Very Large Customer Class, E-017/M-26-211, and Dakota Electric’s proposed Very Large Member Contract, E-111/M-26-243, were both pending as of July 17; initial comments closed July 16 for Otter Tail and run through July 30 for Dakota Electric (Minnesota Public Utilities Commission, accessed 2026-07-17).
  • The PUC’s September 2025 approval of Meta service agreements remains relevant background, but the major February-July 2026 change is the new statutory tariff framework and the still-pending Google ESAs (Minnesota Public Utilities Commission press-release index, 2025-09-11).

4) Generation adequacy and clean-resource pairing

  • Xcel and Google announced that the Pine Island/Project Skyway service arrangement would be paired with work to bring 1,400 MW of wind, 200 MW of solar, and 300 MW of long-duration storage to the grid; Xcel separately describes the storage component as a 300 MW/30 GWh Form Energy iron-air battery installation and says Google will invest $50 million in Xcel’s Capacity*Connect program. These are proposed resource commitments associated with a still-pending ESA, not completed capacity (Xcel Energy, 2026-02-24; Minnesota Public Utilities Commission, accessed 2026-07-17).
  • Minnesota Power and Google announced a Hermantown ESA framework that would enable 700 MW of new clean-energy resources, consisting of 300 MW of wind and 400 MW of battery storage, plus a $5 million Google contribution for Minnesota Power energy affordability and efficiency programs (Minnesota Power, 2026-03-03).
  • Minnesota’s statutory clean-energy requirements continue to constrain utility planning for large new loads; proposed 2026 bills would have exempted certain data center electricity sales from utility solar-standard calculations, but those bills did not pass before adjournment (Minnesota Revisor HF4153, 2026-03-10; Minnesota Revisor HF4990, 2026-04-16; Minnesota House Session Daily, 2026-05-18).
  • The 2026 policy record does not support treating new Minnesota data center demand as generation-neutral: public materials repeatedly tie approvals to utility service agreements, resource additions, backup-power questions, and ratepayer-protection proceedings (Minnesota Public Utilities Commission, 2026-05-18; City of Pine Island, 2026-05-18; City of Hermantown, 2026-05-15).

5) Utility load forecasts and project-driven load

  • Xcel’s Project Skyway work and the May 2026 very-large-customer tariff proceeding show that hyperscale load is now material to Xcel’s Minnesota retail planning and PUC oversight (Minnesota Public Utilities Commission, 2026-05-18; City of Pine Island, 2026-05-18).
  • Minnesota Power’s Hermantown work shows similar large-load planning in northern Minnesota; the city describes Minnesota Power’s load-interconnection study process and the utility’s March 2026 presentation on an electric-service agreement with Google, and Minnesota Power’s petition asks the PUC to approve tariff/rider changes tied to the new Google load (City of Hermantown, 2026-05-15; Minnesota Power public filing, 2026-03-26).
  • An environmental-advocacy case update characterizes the Hermantown proposal as requiring at least 700 MW, but Minnesota Power’s public PUC materials keep total contract demand confidential. The 700 MW load figure should therefore be treated as a public-case estimate, distinct from the separately announced 700 MW clean-resource package (Minnesota Center for Environmental Advocacy, 2026-05-15; Minnesota Public Utilities Commission, 2026-04-07).
  • A February 2026 Fresh Energy analysis reported 13 operating Minnesota data centers with 43 MW of capacity and 12 publicly planned projects totaling 1,120 MW of additional capacity; because this is an advocacy analysis rather than a utility filing, it should be treated as a project-pipeline indicator rather than an approved utility load forecast (Fresh Energy, 2026-02-05).
  • Farmington’s technology-park concept illustrates the gap between project claims and utility forecasts: public reporting describes a proposed 708 MW, 2.5-million-square-foot buildout, but the city distinguishes its land-use and development-contract actions from approval of a specific data center application. The 708 MW figure should therefore be treated as proposed demand, not committed utility load (CBS Minnesota, 2026-02-11; City of Farmington, accessed 2026-07-17).
  • Great River Energy’s 2026 integrated resource plan, docket ET-2/RP-26-145, proposes by 2032 to add 1,355 MW of wind, 561.5 MW of battery storage, and 390 MW of gas generation while retiring or removing several existing contracts and resources. The plan was open for comment through August 3; the public filing does not establish that all of these changes are caused by data centers, so it should not be treated as a data-center-only forecast (Minnesota Public Utilities Commission, 2026-05-05; Minnesota Public Utilities Commission, accessed 2026-07-17).
  • Existing-load growth also occurred in Minneapolis: investors placed $7 million into the operating 21 MW facility at 1001 Third Avenue South, whose owners plan an expansion to 31 MW (Data Center Dynamics, 2026-03-25).
  • Mountain Lake’s approved C-MN Data Centers/AAIM project would be served by the city’s municipal electric utility; as of July 16, the public report did not disclose a reliable MW figure, so it should be tracked as an approved local load without assigning speculative capacity (KEYC, 2026-07-16).
  • Local moratorium materials show that electricity demand and who pays for grid upgrades have become central local-government concerns in Minnesota data center permitting during 2026 (Wright County, 2026-05-21; Finance & Commerce, 2026-05-22).

6) Behind-the-meter generation and backup power

7) Water-energy interaction

  • Minnesota’s energy regulation is increasingly tied to water review because hyperscale facilities can combine large electric load with significant cooling or operational water questions; the DNR preapplication statute and local project records are now part of the same policy record as utility service agreements (Minnesota Statutes 103G.265, accessed 2026-07-17; City of Pine Island, 2026-05-18; Wright County, 2026-05-21).
  • Pine Island states that the Project Skyway data center would be air cooled, would not use water-cooling towers, and would not exceed the city’s total annual DNR water appropriation limit; those representations are project-specific and should not be generalized to all Minnesota proposals (City of Pine Island, 2026-05-18).
  • Hermantown’s updated project materials likewise state that Google’s proposed facility would not use water for cooling and would use no more than 50,000 gallons per day of municipal water; those figures remained part of an AUAR under review, not statewide operating standards (City of Hermantown, 2026-07-14).
  • Farmington residents cited court documents estimating that the proposed technology park would more than double the city’s roughly 2.14 million gallons per day of existing water use, making water supply a continuing energy-siting and litigation issue there (CBS Minnesota, 2026-02-11).

8) 2026 status watchlist