Claude Lands in Azure and Slack: Foundry Goes GA, Claude Tag Launches in Beta

TL;DR: Claude is now a first-class Azure service (Foundry GA, June 29) and a persistent Slack agent (Claude Tag, now in beta) — two deployments that change where Claude lives in your stack.

Claude in Microsoft Foundry — GA. As of June 29, Claude Opus 4.8 and Haiku 4.5 are generally available in Microsoft Foundry (Claude Sonnet 5 followed on July 1). Enterprise teams get single-invoice Azure billing, Entra ID authentication, VNet integration, and an optional US data zone — no separate Anthropic account required. For Azure shops that have been prototyping with the Anthropic API and waiting for governance controls before going to production, this removes the last blocker. The Claude on Foundry starter kit (azd up) stands up the full stack — Foundry account, project, and deployment — in one command.

Claude Tag — persistent Slack agent, now in beta. Launched June 23 for Claude Team and Enterprise, Claude Tag is a Slack member with its own identity, credentials, and audit trail — not just a chatbot. Summon it with @Claude for async tasks (draft a PR, pull metrics, run an analysis) or enable ambient mode and it monitors channels proactively. It connects to GitHub, data warehouses, and external services via its own service accounts. The existing Claude in Slack app is retiring August 3 — affected teams should opt in via their admin settings now.

Why it matters: Both moves signal the same shift — Claude moving from "API you explicitly call" to "service that lives where your infrastructure already is." Foundry closes the enterprise procurement gap; Claude Tag demonstrates the agentic patterns (ambient context, cross-tool identity, persistent memory) you can build yourself with the Agents API.

Sources: Claude in Microsoft Foundry is now generally available — Microsoft Azure Blog · Introducing Claude Tag — Anthropic · VentureBeat coverage