Last Update: 09/29/2026 at 4:34 PM EST

Morning Briefing: Data Centers

Thursday, August 6, 2026

August 6, 2026

Virginia Moves Transmission Costs To Data Centers

Yesterday brought little new construction or power-procurement activity, but it made the terms of development more consequential. A Virginia regulatory order, an AWS project withdrawal in Maryland, and disputes over local moratoria all pointed to the same practical reality: a data center is no longer defined simply by its site and projected load. It must also survive a clearer accounting of who pays, who has authority, and which applications were filed soon enough to avoid new rules.

This was not a broad retreat from data-center investment. It was a day in which the legal and financial conditions surrounding projects became more visible—and, in some places, more binding.

Virginia’s State Corporation Commission directed Dominion Energy to place more of the cost of planned transmission upgrades on large-load customers, including data centers. Virginia Business reported that the decision shifts recovery of roughly $1.539 billion in planned costs toward those customers, reducing the typical residential surcharge from $2.90 to $0.94 per month. The order does not eliminate the need for new grid infrastructure; it changes the economics of building it for the customers driving demand.

AWS formally withdrew its Calvert Technology Center application in Calvert County, Maryland, ending active county review of a proposed campus near the Calvert Cliffs Nuclear Power Plant. The county’s notice did not explain the decision, so it should not be attributed to local opposition, power access, or permitting without further disclosure. Still, the withdrawal removes a proposed 2.4-million-square-foot development from the near-term pipeline as county officials consider a six-month pause on site-plan approvals on August 18.

Local governments continued to choose very different forms of control. In Hillsboro, Oregon, OregonLive reported that Stack Infrastructure and Aligned Data Centers filed applications before the city’s July 27 permit moratorium and will be reviewed under the earlier rules. Laredo, Texas, declined a temporary pause but directed staff to prepare permanent standards covering water, power, cooling, environmental effects, and infrastructure capacity. The difference matters: one jurisdiction is managing an inherited pipeline, while another is trying to set the rules before one arrives.

Key Points

  • The Virginia decision advances a policy question that has moved quickly from public debate into utility regulation: whether households should finance transmission built primarily to serve exceptionally large new loads. The important change is not rhetorical. A separate tariff and cost-allocation structure can affect project underwriting, customer contracts, and the willingness of utilities to commit capital ahead of confirmed demand.
  • Hillsboro illustrates the limits of a moratorium as a reset button. Filing timing can preserve an earlier approval path even when a city is reconsidering tax incentives, land use, and power availability. For developers, application status is becoming a strategic asset; for local governments, it is a reminder that policy changes often govern the next wave rather than the projects already at the door.
  • The Federal Communications Commission is also considering a restriction on imports of new Chinese optical-transceiver models, according to reporting published by Arkansas Online. Zhongji Innolight accounts for an estimated 27% of the global data-center transceiver market. The proposal is not yet a rule, but it introduces a separate execution risk: network equipment sourcing may become more expensive or less flexible even where land, power, and permits are in place.
  • Opposition remains politically potent but procedurally uneven. In Yellowstone County, Montana, organizers seeking a vote on Quantica’s proposed 5,000-acre campus learned that roughly 10,000 signatures may have been gathered after the applicable deadline. That does not settle the dispute, which may reach court, but it shows how quickly a campaign’s leverage can turn on statutory timing rather than public sentiment alone.

Implications

For large-load projects in Virginia and potentially other closely watched power markets, the question is increasingly not whether a utility can build the necessary transmission, but whether the project can absorb the resulting payment obligations. Cost responsibility is becoming part of the project’s core commercial design rather than an external policy risk.

The Calvert withdrawal is a useful corrective to treating an active development application as a committed buildout. A site near major generation may be attractive, but it remains vulnerable to unresolved commercial, regulatory, and local conditions. Until AWS gives a reason or proposes a replacement plan, the withdrawal is best understood as a project-specific exit, not proof that nuclear-adjacent data-center development is broadly failing.

Local restrictions are becoming less uniform, not more. Some places are imposing pauses, others are writing permanent standards, and still others are processing pre-moratorium applications. That fragmentation raises the value of early local diligence: the applicable rules may depend as much on filing sequence and local code language as on a project’s technical design.

The prospective transceiver restriction widens the definition of infrastructure risk. AI facilities depend on power systems and construction materials, but they also depend on dense optical networking. A security-driven supplier shift could add cost and procurement lead-time pressure without changing a single land-use rule.

Watchpoints

Watch

Dominion Energy’s proposed tariff and the specific thresholds, commitments, and transmission costs assigned to large-load customers under the Virginia order.

Watch

Whether AWS explains its Calvert County withdrawal, submits a revised proposal, or shifts its Maryland strategy as the county considers an August 18 moratorium vote.

Watch

Clackamas County’s expected vote on a proposed moratorium, and whether Laredo’s August 11 town hall produces more defined standards for water, cooling, utility capacity, and site compatibility.

Watch

Publication of the Federal Communications Commission’s proposed transceiver restrictions, including their scope, implementation timetable, and cloud-provider response.

Watch

Whether Montana officials, the secretary of state, or a court clarify the Yellowstone County petition deadline and the status of the Quantica ballot effort.

Fallout

Yesterday saw meaningful movement in two connected areas: the allocation of grid-expansion costs to very large customers, and the increasingly consequential local rules that determine which data-center proposals can proceed. Both affect project feasibility before a facility reaches construction.

Who Pays For Grid Expansion

Utilities and regulators are increasingly confronting the risk that transmission, generation, and delivery investments made for large data-center loads could be paid for by existing customers if projects are delayed, downsized, or withdrawn.

Fresh developments

Virginia’s State Corporation Commission directed Dominion to develop a policy that assigns more transmission-cost recovery to large-load customers. The reported result lowers the typical residential effect of Dominion’s planned $1.539 billion recovery from $2.90 to $0.94 per month.

Why we noticed

This is a concrete move from broad ratepayer-protection promises toward a financial rule that can alter the economics of a project. Large-load customers may face higher direct obligations, while utilities gain a clearer basis for building infrastructure without placing as much exposure on households.

Watch for:

  • Dominion’s tariff design and the facilities covered by it
  • Financial-security, minimum-bill, or load-commitment requirements for large customers
  • Whether other state commissions adopt comparable transmission cost rules

Local Rules Turn Timing Into A Project Advantage

Cities and counties are moving beyond generic industrial zoning toward moratoria, specialized standards, and more discretionary review of large facilities. Yet those changes often leave earlier applicants on a different path from later ones.

Fresh developments

AWS withdrew its Calvert County application, while Hillsboro confirmed that two applications filed before its moratorium will remain subject to the previous land-use rules. Laredo rejected a temporary pause but began drafting permanent standards for high-water and high-power uses. Together, these developments show several local responses operating at once: withdrawal, grandfathering, and rulemaking.

Why we noticed

The development risk is no longer captured by a simple question of whether a jurisdiction supports data centers. Project timing, the completeness of an application, and the exact scope of a moratorium can materially affect approvals, design requirements, and schedule certainty.

Watch for:

  • Calvert County’s August 18 moratorium discussion and any further statement from AWS
  • Hillsboro’s review of the Stack Infrastructure and Aligned Data Centers applications
  • Laredo’s proposed permanent standards and their treatment of water, cooling, and power capacity

Final Thought

The data-center buildout is not being decided only by where power can be found. It is increasingly being decided by whether the cost, timing, and local consequences of delivering that power can withstand scrutiny.