Microsoft has made Routines in Foundry Agent Service generally available, allowing an agent to start at a chosen time, repeat on a schedule or react to an outside event. Foundry keeps the trigger, instructions, connections and execution history together, reducing the need for teams to assemble schedulers, queues, webhooks and monitoring around the agent.
Initial event integrations cover new GitHub issues and Microsoft Teams channel messages. A GitHub routine, for example, can receive an issue payload, classify it and recommend an owner as soon as the issue arrives. Timer and recurring triggers suit release tasks, daily summaries, compliance checks and operational monitoring.
Developers can choose whether a routine uses its creator’s delegated identity or the agent’s own Microsoft Entra ID identity. That distinction helps limit unattended actions to the appropriate permissions and leaves an audit trail. Routines can be managed through the Foundry portal, REST API, Azure Developer CLI, or Python, JavaScript and .NET SDKs.
A separate reminder tool, still in preview, lets hosted agents schedule a later run on the same conversation. It is intended for jobs that must wait for an approval, deployment or long-running API without a custom polling service.