Microsoft gives Azure Logic Apps a controlled place to run agent-written code

Microsoft has added the piece that enterprise integration platforms need before agent workflows become more than a demo: a place where a model can generate and run code inside a controlled execution boundary. According to InfoQ, Azure Logic Apps now supports sandboxed code interpreters for agent workflows, with Python, JavaScript, C# and PowerShell in scope.

That matters because Azure Logic Apps already sits in the practical layer of cloud automation: triggers, connectors, conditions, branches and calls into external systems. It is not primarily a research playground or a chat surface. It is where companies wire services together. Adding code execution to agent workflows changes the role of the platform from deterministic orchestration alone toward workflows that can inspect an input, decide what needs to be calculated or transformed, and then execute a small piece of generated logic as part of the run.

The important word is not only code. It is isolation. InfoQ reports that the interpreters run in Hyper-V isolated sessions. That distinction is what separates an attractive agent demo from something architects can seriously evaluate. If an agent writes a Python script, a JavaScript transformation, a C# helper or a PowerShell task, the first operational questions are blunt: where does it run, what can it touch, and how is damage contained when the generated code is wrong?

Microsoft is trying to close the gap between agent ambition and integration discipline. Hyper-V isolation does not remove the need for careful workflow design, permissions and review, but it shows the right default assumption: generated code is an operational risk surface, not magic text. In a business process, an agent has to be useful without escaping the boundaries of the process that invoked it.

Another notable detail is model selection per workflow. Architects get control over which model is used in a given flow instead of treating one central model as the answer for every integration. One workflow might prioritize speed or cost. Another might need a stronger model for a more complex transformation. A third might need a stricter setup because it touches a sensitive process. That is closer to how integration platforms are used in the real world, where different workflows carry different risk, latency and cost profiles.

The positioning is also deliberate. Microsoft already has Azure AI Foundry for building and managing AI applications, and Copilot Studio for creating copilots and agent experiences. Logic Apps is being pushed into a different role: the operational layer where an agent is not necessarily a chat interface, but a step inside a workflow that retrieves data, calls a service, transforms a record and passes the result onward.

The most interesting part of the announcement is not a broad claim that agents will automate everything. It is more grounded than that. Microsoft is putting agent logic into a familiar integration frame, with explicit model choice and sandboxed execution. If the pattern proves reliable, Logic Apps could become one of the places where AI in companies is less visible as a standalone app and more visible as a controlled step inside existing business machinery.