AI News — June 4, 2026

AI-assisted SDLC

• [2026-06-02] Microsoft — at Build, launched Microsoft IQ, a unified enterprise-intelligence layer spanning Work IQ (M365 workplace data inside the trust boundary), Foundry IQ (enterprise knowledge for agents), Fabric IQ (business-semantics ontology), and Web IQ (live web grounding), reachable across GitHub Copilot, Microsoft Foundry, and Copilot Studio. The Work IQ APIs reach GA June 16. The pitch is grounding: give agents a shared, governed view of company data instead of each tool re-inventing its own silo. (official, source, source)

  The practical hook for dev teams: rather than wiring each Copilot agent to your own retrieval stack, Work IQ becomes the supported path for agents to read M365 content under existing M365 permissions — so the grounding story and the access-control story are the same thing. Worth a look once the APIs hit GA on June 16, but it’s a Microsoft-stack bet, so weigh the lock-in against rolling your own grounding layer.

• [2026-06-03] Anthropic — formalized its three-month-old Claude Partner Network with a tiered Services Track (Select / Preferred / Global Premier, gated on counts of certified individuals, deployed joint customers, and public customer stories) and a Claude Partner Hub portal — refreshed daily — where partners track their standing and customers find qualified firms. Since March’s launch, 40,000+ firms have applied and 10,000+ consultants have earned a Claude certification. (official, source, source)

  This is less a product than a go-to-market signal: Anthropic is building a certified-integrator channel the way enterprise-software vendors always have, which matters if you’re an org that buys Claude deployments through a systems integrator rather than building in-house — the tiers and Hub are meant to tell you which firms have actually shipped Claude in production versus just badged up.

• [2026-06-01] Anthropic — confidentially filed a draft S-1 with the SEC, taking the first formal step toward an IPO and getting out ahead of OpenAI, which is reportedly readying its own filing. It follows a round that valued Anthropic at a $965B post-money valuation (topping OpenAI’s $852B) on a reported ~$47B revenue run-rate, up from ~$10B a year ago. (official, source, source)

  For teams standardizing their SDLC on Claude Code, this is a vendor-durability signal more than a product change: a public-company filing brings disclosure and capital that argue for longevity, but it also adds the usual quarterly-earnings pressure on pricing — so it cuts both ways when you’re betting a toolchain on a single vendor’s roadmap. (Carried over from the weekend; it slipped through the Build-heavy briefings and is the biggest uncovered industry story of the window.)

Watch list

• Microsoft Work IQ APIs GA (June 16) and Foundry hosted agents GA (early July): the dates that turn Build’s keynote slides into something you can actually provision against. Watch for real auth/permission docs on Work IQ — the “agents read M365 under existing permissions” claim is the whole value proposition and the whole risk.

• Gemini 3.5 Pro rollout (this month): at I/O (May 19), Google said 3.5 Pro was already in internal use and would roll out “the following month” — i.e. June. The Flash tier already leads some agentic/coding benchmarks, so the Pro drop is the one to watch for a model card and independent numbers. (source)

• OpenAI confidential IPO filing: reported to be readying its own draft S-1 in Anthropic’s wake — no filing confirmed yet. Worth watching for how the two listings are timed against each other. (source) (unconfirmed)

• Anthropic developer billing split (June 15): Claude Agent SDK, claude -p, and GitHub Actions usage reportedly move off subscriptions onto a separate monthly credit pool (~$20–$200); Anthropic still hasn’t detailed it on an official page. If real, it changes the cost model for anyone running Claude in CI or automation — worth pricing out ahead of the date. (source) (unconfirmed)

• MCP spec 2026-07-28 final: stateless core, Tasks, and MCP Apps move to stable, and clients must validate the iss parameter per RFC 9207 (SEP-2468). Server operators relying on sticky sessions will need to migrate — worth auditing deployments before the date. (source)