Azure’s agentic application platform brings together hosting, isolated execution, integrations and durable orchestration so developers can build applications that use agents without treating every task as a chat interaction. It matters to Azure developers and platform teams that need to run agent tools, connect business systems or keep long-running workflows recoverable. Microsoft Events demonstrates how these pieces fit together in a Microsoft Ignite session.
The platform is not presented as a single new service. Instead, it combines Azure App Service, Azure Container Apps and Azure Functions with building blocks for agent execution, workflow state and integrations. The aim is to let teams add agent capabilities to applications on Azure rather than requiring a move to a separate hosting platform.
Each service has a different role in the design. App Service can remain part of an existing application, Container Apps provides a place for container-based workloads and isolated sandboxes, and Functions can host event-driven skills. Durable Task Scheduler addresses a different problem: keeping progress in workflows that run for a long time, pause or need to recover.
That distinction matters because an agent may call tools or run code, not just return text. The session’s design principles include giving each agent its own identity, isolating code execution, monitoring and controlling network egress outside the sandbox, and preventing sandboxed code from accessing secrets directly.
The components are aimed at developers building agent-enabled applications and platform teams providing secure execution for them. They are also relevant to teams extending existing event-driven applications with agent behavior, or connecting agents to business systems through reusable integrations.
The session describes Azure Container Apps Sandboxes as generally available. It describes hosted skills in Azure Functions as available now. Durable Task Scheduler is presented as a managed workflow engine supported across Azure Functions, Azure App Service, Azure Container Apps and Azure Kubernetes Service.
The approach is composable: the speakers describe using the capabilities with existing Azure services and Microsoft Foundry. The discussion also describes sandboxes as a foundation used by Microsoft Foundry-hosted agents, Copilot Studio, GitHub Copilot workspace, Azure SRE Agent and Azure Container Apps Express.
For teams evaluating the Azure compute services, the practical starting point is to identify the workload’s needs: does it need isolated code execution, event-based activation, durable state, or access to business-system connectors? The services address different parts of that application rather than replacing one another.
There is also a connection between hosted skills and durable workflows. The presenters describe a capability that reads a skill’s Markdown and generates a coded Durable Task version. The stated goal is to turn non-deterministic instructions into a deterministic workflow graph and reduce token use on subsequent runs.
For operators, the scheduler includes telemetry and a dashboard that shows workflow progress. At the execution boundary, the design calls for monitoring network access outside the sandbox, where restrictions can be applied without trusting the code running inside it.
These building blocks address different requirements, so teams should choose based on the work an agent must perform. A hosted skill responds to events and can be added to an existing Functions app; it is not the same thing as a persistent agent service or a durable orchestration engine. A sandbox supplies an isolated place to execute code, while Durable Task Scheduler manages workflow progress.
Security also depends on how the components are used. The design described in the session avoids giving sandboxed code direct access to secrets and puts egress monitoring outside the sandbox. Teams should account for identity, permitted network access and the actions an agent is allowed to take when designing their own implementation.
The speakers emphasize that these capabilities can be composed with existing Azure services rather than requiring an application migration. The session does not provide a universal setup recipe or configuration values; implementation choices depend on the application’s hosting, integration and workflow needs.
They are hardware-isolated microVMs for running agent code and tools. The session describes short-lived and long-running workloads with preserved context.
A hosted skill uses Markdown instructions and can be triggered by events such as a queue message, timer, webhook, alert or email. Functions triggers and bindings connect it to inputs and actions.
It persists workflow progress and can recover execution after a crash or resume after infrastructure scales to zero. It also supports long-running transactions and human-in-the-loop steps.