Regulated electric, gas, and water utilities carry a Microsoft estate sized against a grid modernization ambition, a NERC CIP perimeter regulators care about every audit cycle, and a customer information system that has to clear public utility commission scrutiny. The renewal moves where the regulatory frame and the actual consumption diverge. $420M+ recovered. 340+ engagements. Buyer side only.
Utilities sit between state public utility commission rate review, NERC CIP at every bulk electric system asset, customer privacy regulation, and a grid modernization program that touches every part of the Microsoft estate. Every dollar of IT and Microsoft cost is potentially recoverable through the rate case and potentially challenged by intervenors.
NERC CIP across the bulk electric system facing IT estate, state PUC rate review on the recovered IT cost stack, FERC market participation rules where applicable, and SOC 2 across the customer facing systems. Microsoft prices the security and compliance bundles as if every meter and every endpoint needs the same control surface.
Microsoft 365 across corporate. F3 across field crews, meter readers, and dispatch staff. Azure for AMI analytics, outage management, and grid modernization workloads. Power BI Premium across regulatory reporting. Dynamics 365 for customer service and field service. SQL Server inside the customer information and meter data management estate. Defender for IoT and Sentinel across the OT and IT perimeter.
Volume tiers exist that withstand intervenor scrutiny. Microsoft does not pre offer them. We negotiate them in and document the prudence narrative.
We negotiate the corporate workforce, the field and OT estate, and the customer facing stack against a prudence test the rate case will survive. Microsoft does not run that test. We do.
The renewal calendar should align with the rate case calendar. When it does not, we structure the contract to align with the next case.
We advise across the utility map. Investor owned utilities on rate case prudence and global EA structure. Public power agencies on cooperative purchasing leverage. Cooperatives on member economics and right sized field stacks. Municipal utilities on public sector contract instruments and the right Microsoft channel. Same discipline, scaled to the contract.
The pattern that fails: a procurement led negotiation that wins headline price and produces a contract that intervenors challenge in the next rate case. The pattern that works: a posture led negotiation built for rate case defensibility, where every dollar of Microsoft spend is mapped to a prudence narrative the PUC has seen before.
Microsoft anchors utility renewals on a grid modernization ambition that has not yet been approved in the integrated resource plan and a NERC CIP scope that includes assets outside the bulk electric system. F3 is licensed against a field roster that includes contractor populations covered elsewhere. Azure AMI analytics is committed against an outage management roadmap that the operations group is still phasing. Sentinel OT ingest is sized against a SCADA inventory that includes assets already retired.
The most common pattern we see: an investor owned utility paying Azure analytics against a personalization ambition the customer experience group has rescoped, Defender for IoT across an AMI meter count that includes the retirement program, and a Sentinel commit that the SOC never ratified. The rate case team inherits a number they cannot fully defend.
We start with the regulatory reality. Most recent rate case order, current IRP, current NERC CIP scope, current AMI rollout, current SOC ingest plan, and the funded grid modernization roadmap. From those we rebuild the Microsoft consumption profile against the prudence test.
We do not opine on utility strategy. That is the work of the operator and the commission. We translate the regulatory reality into commercial terms and run the deal desk negotiation against the prudence frame the rate case will face.
Anonymized but verifiable on reference call. Drawn from active engagements in the trailing twelve months across the practice.
The opening quote sized Defender for IoT against an AMI program that included the retirement schedule, committed Azure analytics to a personalization roadmap the customer experience group had rescoped, and proposed Sentinel OT ingest against a SOC forecast that had not been ratified. We rebuilt from the active AMI rollout plan, the ratified SOC ingest baseline, and the approved IRP.
They produced the deal for the grid we are planning to build. We needed the deal for the grid we operate and the rate case we have to defend.Vice President of Information Technology · Investor owned utility
Every utilities engagement produces written deliverables your CFO, CIO, operations leader, and audit committee can read directly. Nothing lives only in our heads.
Board ready narrative of where the contract sits, what leverage exists, and what the disciplined ask is. Signed off jointly with internal stakeholders.
Concession data from signed contracts in your sector, your spend tier, and your renewal quarter. Sourced from active practice engagements.
Calendar of milestones, internal alignment checkpoints, Microsoft engagement touch points, and decision dates from posture through signature.
Live tracker of every ask, every counter, every Microsoft concession landed, and every term we have not yet closed. Updated through signature.
Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is for a regulated utility, and whether we are the right firm for this engagement.