Microsoft’s Virginia Challenge Raises A Bigger Question: Who Should Pay For The AI Grid?

Blog
Digital Grid Technologies
23 Sep, 2026

Microsoft has appealed to the Supreme Court of Virginia over a new state rule requiring data centre developers to pay upfront for the transmission infrastructure needed to connect them to the grid. The dispute comes despite Microsoft and other technology firms signing a pledge to cover the energy and infrastructure costs associated with their data centres in March 2026. Regulators in Virginia introduced the new approach after growing concern that data centre expansion was shifting costs onto other electricity customers.

The scale of the issue is substantial. In Virginia, regulators have identified billions of dollars of transmission investment associated with data centre growth, and the State Corporation Commission has created a dedicated rate class for large-load customers. From 2027, new large customers will face a minimum charge equivalent to 85% of their transmission and distribution costs, alongside minimum contract obligations and other safeguards intended to prevent cost shifting.

The core principle is straightforward: data centre developers should pay for the new power-delivery infrastructure their projects require. Though utilities may own the resulting assets and benefit from higher electricity sales, those wider gains do not justify transferring project-specific connection risk to households and other businesses. Contracts can account for any genuinely shared value, but the default should still be that the customer triggering the investment funds it.

Google offers a useful proof point for our 2026 prediction that hyperscalers will increasingly turn flexible computing load into a grid resource. In a recent announcement, Google said it has embedded 1GW of data centre demand response into long-term contracts with five US utilities, allowing selected machine-learning workloads to be shifted or reduced when the grid is constrained.

Such a model can reduce the firm capacity required to serve a facility and help utilities use existing assets more efficiently. It supports differentiated connection terms for flexible and inflexible loads and may allow a committed developer to connect sooner. However, flexibility does not answer the prior financing question: developers should still fund the infrastructure directly attributable to their projects.

Moreover, tougher cost obligations should not automatically create longer queues. Rather, they mainly filter out developers unwilling or unable to pay, reducing speculative requests and preserving scarce capacity for credible projects. Some AI facilities may be delayed or cancelled as a result, but slowing the build-out at the margin is not inherently a problem if the alternative is asking other electricity customers to subsidize it.

Digital grid technologies become most valuable when a connection is being designed or once it is operational. Better load forecasting, network modelling, monitoring and flexibility management can help utilities assess not just how much electricity a data centre wants, but when it needs it and how much of that demand can be managed. These technologies can lower the capacity ultimately required and improve operation of the connected asset, but they do not solve the upfront question of who finances the connection.

The Virginia debate should therefore start with a clear allocation of responsibility: developers pay for the infrastructure their projects trigger. Regulators can then use contractual commitments, queue milestones and differentiated operating requirements to distinguish serious projects from speculative ones and flexible loads from inflexible ones.

Google’s approach shows how the two issues can fit together. Developers should pay their own way into the grid, and once connected, flexible operations can reduce system costs and ease constraints. This provides a more defensible framework than subsidizing rapid AI expansion: utilities should protect existing customers first, reward credible flexibility next, and accept that projects unwilling to meet those terms may have to wait.

For more on grid developments, check out the Verdantix Insights page.

Discover more Digital Grid Technologies content
See More