NiSource announced a long-term electricity agreement with Microsoft on October 16 for its previously announced northwest Indiana campus. Service is expected to start in 2028 under a 20-year term. For infrastructure teams, the accompanying battery contract makes this worth reading beyond the headline capacity figure.
The company announcement describes an approximately 1,100 MW expansion of GenCo's owned pool portfolio. NiSource says Microsoft fully funds the generation and transmission required for its load. It also identifies a 600 MW battery resource intended to join a pool serving multiple large-load customers.
Those statements describe a supply arrangement and planned infrastructure. They do not establish how much IT equipment can run on a particular day.
The battery filing adds the missing energy dimension
NiSource's October 16 SEC filing reports that GenCo entered a tolling agreement on October 15 with Atlas Storage 1, an AGP Group subsidiary. The planned stand-alone system is rated at 600 MW AC and 2,400 MWh and will connect to the MISO transmission system.
AGP Group is to develop, construct, own and operate it. GenCo supplies charging electricity at its expense and has the right to instruct dispatch and receive the economic benefits of available capacity, discharged energy and other services.
The filing expects first-phase commercial operation by December 1, 2027. Effectiveness of the agreement depends on satisfactory engineering, procurement and construction and interconnection agreements being executed by January 31, 2027.
These are disclosed contractual terms and expectations, rather than evidence of an operating battery.
Operational analysis: read power, energy and dispatch together
Dividing 2,400 MWh by 600 MW gives a nominal four-hour duration. That arithmetic is useful for understanding the rating. It is insufficient for assigning four hours of guaranteed campus backup.
A reliability review should ask how much usable energy is available at the required moment, who can dispatch it, what other obligations apply and how the resource recharges. It should also examine whether the battery can deliver power through the relevant network during the failure being considered.
A transmission-connected resource can support a supply portfolio while the campus still needs its own continuity arrangements. Operators should request the electrical boundary, protection assumptions and tested failure scenarios before crediting external storage in a site availability model. A shared resource deserves particular attention to allocation and dispatch priority.
None of those questions alleges a defect in this project. They are the information needed to translate a resource contract into a defensible operating assumption.
Build the load ramp around verifiable milestones
For a project team considering a similar agreement, I would maintain a delivery register linking each planned load increase to the infrastructure that enables it.
For the first server hall, that register should identify the required service capacity, the enabling transmission work, commissioning evidence and the party responsible for accepting each milestone. Later halls need their own dependencies. A target year alone leaves too much ambiguity for equipment installation and customer commitments.
The register should also distinguish first energization from sustained service at the intended load. Temporary commissioning arrangements, partial capacity and full contracted service can support different activities. Treating them as interchangeable can put procurement and operations on conflicting schedules.
The battery's contractual conditions provide concrete milestones to monitor. Meeting a condition would be progress; it would still leave construction, testing and commercial operation to verify. The same discipline should apply to the wider supply portfolio.
Keep portfolio capacity separate from campus demand
The approximately 1,100 MW figure belongs to the announced portfolio expansion. It should not be copied into a campus specification as a verified IT-load requirement. Nor should the battery's rating be added to that figure without a disclosed resource accounting basis.
For technical B2B readers, this changes the questions worth asking suppliers. Which capacity definition appears in the proposal? Where is it measured? Which resource and network assumptions support it? What evidence permits the next load increment?
NiSource also projects savings for existing NIPSCO customers. Those remain company expectations, rather than measured bill outcomes. Tracking those outcomes requires a different evidence trail from tracking electrical readiness.
The agreement provides a clearer view of who funds infrastructure and who controls the planned storage resource. Operators can use those details to build a delivery and reliability review with named responsibilities, dated dependencies and evidence required before each load increase.
