Microsoft Foundry Agent Service Routines reach general availability (GA)
Routines in Microsoft Foundry Agent Service reach general availability (GA) — a managed way to run agents on a schedule, at a specified time, or in response to events in external systems. Without separately building schedulers, event listeners, webhooks or infrastructure, it gathers triggers, agent actions, identity, connections and run history inside the Foundry project. There are three kinds of trigger: timer (once, at a single future point), recurring (on a set cycle) and event-based (when something happens in a connected system). For identity, users choose between the creator's delegated permissions and the agent's own Entra ID. With a reminder tool, in preview, the agent can schedule its own re-run after a set time, monitoring multi-step tasks without an external polling service. The initial integrations are GitHub issue events and Teams channel messages.
Why it matters
The operational foundation for agents moving from "running when a person calls them" to "waking up on their own" has become a GA cloud product. It matters that the option of giving agents their own identity came out at the same time: when the subject in audit logs is an agent rather than a person, the unit of accountability changes.
Source — Primary sources first; secondary reports are labelled “Press”
Officialdevblogs.microsoft.comhttps://devblogs.microsoft.com/foundry/from-chatbots-to-automated-assistants-routines-in-microsoft-foundry-are-now-generally-available/Added in Week 41, 2026 · See that week