Claude 4 Retires June 15, Microsoft Work IQ Goes Live June 16

<p><strong>Claude Sonnet 4 and Opus 4 retire June 15</strong> — production apps calling the <code>-20250514</code> model IDs will break, so migrate to Sonnet&nbsp;4.6 or Opus&nbsp;4.8 now before the deadline. Microsoft Work&nbsp;IQ APIs go GA June&nbsp;16 with audited access to Microsoft&nbsp;365 org intelligence for agents, and LangGraph Platform gains n...

Highlights

4 items
  • Claude Sonnet 4 (claude-sonnet-4-20250514) and Opus 4 (claude-opus-4-20250514) retire June 15 — production apps calling those model IDs will return errors; migrate to Sonnet 4.6 or Opus 4.8 now (Anthropic)
  • Claude Agent SDK billing model also changes June 15, with a migration playbook now published for teams running SDK-managed agent workflows (ThePlanetTools)
  • Microsoft Work IQ APIs reach general availability June 16, giving agents programmatic access to Microsoft 365 org intelligence — calendar, email, org graph — with a full audit trail on every call (Microsoft Blog)
  • LangGraph Platform now connects to any MCP server natively, letting graph-based agents swap tool providers without adapter code — just as the MCP stateless HTTP release candidate hardens (LangChain Changelog)

Key Signals

ranked scan
  1. 1

    7-Day Countdown: Claude Sonnet 4 + Opus 4 Retire June 15

    Anthropic deprecation notice, ~June 5

    claude-sonnet-4-20250514 and claude-opus-4-20250514 go dark in seven days; any service still pointing at those IDs will start returning errors on the 16th. The migration is a one-line model-ID change — Anthropic recommends Sonnet 4.6 for latency-sensitive workloads and Opus 4.8 for complex or long-horizon agentic tasks — and several third-party guides confirm the per-token cost at the new targets is comparable or lower. (Anthropic, MindStudio)

    urgent
  2. 2

    Microsoft Work IQ APIs + Windows Agent Policy Framework

    Microsoft Build 2026, June 2–3

    Work IQ (GA June 16) gives agents a single authenticated layer into Microsoft 365 — calendar, email, org graph — and logs every call for audit. Paired with the new Windows Agent Policy Framework, managed via Intune, IT admins can define fine-grained rules governing agent installation, network scope, and data-sensitivity handling at the device level. Both capabilities land within 48 hours of the Claude 4 cutover, making this one of the busiest governance weeks enterprise operators have seen this year. (Microsoft Blog, Windows Forum)

    governance
  3. 3

    LangGraph Platform Goes MCP-Native

    LangChain changelog, late May 2026

    LangGraph's managed platform now treats any MCP server as a first-class tool source — graph nodes call MCP-hosted tools the same way they call built-in LangChain tools, with no custom adapter code. The change lands as the MCP stateless HTTP release candidate removes sticky-routing requirements for scaled deployments, meaning the whole stack — stateless protocol, native framework connectivity — is now more production-ready than it was two weeks ago. (LangChain Changelog)

    MCP

Why It Matters / What To Watch

operator signals
  1. The Claude 4 → 4.x migration is not optional this week
    • Audit every service calling the -20250514 model strings before June 15; Agent SDK users should also check the June 15 billing model change to avoid a compounded disruption. (ThePlanetTools)
    • Opus 4.8 — the Glasswing-era flagship — is the natural landing spot for long-context and agentic workloads; the deprecation deadline effectively makes it the new production baseline. (Anthropic, MindStudio)
  2. Enterprise context and governance rails are converging this week
    • Work IQ's org-intelligence APIs close one of the biggest grounding gaps for enterprise agents; the Windows Agent Policy Framework closes the policy enforcement gap for device-level deployments. Watch whether Copilot Studio and Azure AI Foundry wire these together in coming releases. (Microsoft Blog, Windows Forum)
    • LangGraph's MCP-native move signals that framework-level MCP support is now a baseline expectation, not a differentiator — builders who delayed MCP integration should revisit adoption timelines. (LangChain Changelog)

Quick Links

sources