Amazon Web Services and Microsoft have published nearly simultaneous updates that change the way AI agents interact with already deployed business logic. Instead of rewriting flows or embedding rules in the model, both platforms expose existing orchestration engines —Step Functions and Logic Apps— as agent-invokable tools, keeping deterministic control outside the LLM.
AWS: Step Functions as agent tools via AgentCore Gateway and MCP
AWS announces that Standard and Express Step Functions flows —which already coordinate more than 220 services— can be delivered to the agent as tools through Amazon Bedrock AgentCore Gateway, which speaks Model Context Protocol (MCP). The agent decides when to execute a flow and what input to pass; Step Functions guarantees the order and exactly‑once semantics as defined, without the model manipulating credentials or step sequence.
Compatibility is immediate: any existing flow qualifies as a connector target in all regions where AgentCore Gateway is available, with standard pricing. MoEngage exposed approximately 400 internal REST APIs as agent tools via this gateway, saving about six months of platform engineering; agents discover tools by describing the task, not by receiving full catalogs, avoiding more than 20,000 tokens per connection according to the official AWS blog.
As additional context, OpenAI GPT‑6.1 Terra arrives on Bedrock with pricing at least 50% lower than GPT‑6.1 Sol and GPT‑5.6 Terra, 1 million input tokens, and, according to OpenAI data, three times faster on Agents’ Last Exam; validation on a proprietary evaluation set is recommended before production.
Microsoft: Logic Apps Automation orchestrates Foundry agents (Prompt and Hosted)
Microsoft introduces Logic Apps Automation as a deterministic control plane around Foundry agents —configured Prompt Agents and container‑based Hosted Agents with custom code—. API calls, schedules, and connector events trigger the agent, while Logic Apps provides branching, retries, timeouts, parallel execution, and execution history around the invocation.
The documented security pattern shows a Foundry agent invoking Logic Apps via an OpenAPI tool with managed identity and Entra ID, eliminating SAS keys. Additionally, a mandatory migration path before December 1, 2026 is detailed, the date when Foundry workflows are retired, to move interactive agents to traceable, event‑driven business processes according to the Azure Integration Services bulletin.
In public preview, the monthly grants per Azure subscription include 108,000 flow execution seconds, 1 GB of retention, 1,000 Standard connector calls and 500 Enterprise, knowledge storage, and AI usage; the managed environment is free only for the first 60 days. A local CLI extension for Logic Apps Standard development is also released, with project creation, connector discovery, validation, and diagnostics from the terminal.
Paradigm comparison: Bring your own workflow vs. Native orchestration
AWS adopts a ‘bring your own workflow’ approach: existing flows are exposed as MCP tools without rewriting, and the gateway manages the agent-tool contract with semantic search that reduces token bloat. Microsoft opts for ‘native orchestration’: Logic Apps becomes the control plane that wraps Foundry agents, providing deterministic governance (branching, retries, timeouts) around the non-deterministic call.
In both cases the attack surface is reduced: in AWS the tenant identity never reaches the model (MoEngage case); in Azure business rules remain in the audited workflow and the agent only converses and delegates. Cost governance differs: AWS charges standard Step Functions rates plus AgentCore Gateway; Azure offers generous preview grants but the free managed environment expires after 60 days.
Developer experience also diverges: AWS provides a dynamic per-task tool catalog and MCP 2025-11-25 for on-behalf-of token exchange with Entra ID; Microsoft releases local CLI (preview), typed C# SDK, Connector Namespace, and Copilot skill for validation and diagnostics, complementing the visual designer.
Security and governance: attack surface reduction and cost control
The strict separation between agent decision and flow execution eliminates the need to embed secrets in agent code. In AWS, AgentCore Gateway mediates access via MCP and manages identities without exposing credentials to the model. In Azure, the community article ‘Don’t Rebuild Your Workflows Inside Agents’ demonstrates secure invocation with managed identity and Entra ID, without SAS keys or secrets in the agent.
Traceability improves because each flow execution is recorded in the orchestration engine (Step Functions or Logic Apps) with full history, inputs, outputs, and timings, facilitating audit and compliance. Costs are predictable: AWS uses per-state-transition fees and gateway calls; Azure publishes monthly grants and base pricing plus compute scale-to-zero, with optional capabilities billed separately.
Both platforms require validating that the exposed business logic is deterministic and does not require model improvisation. Only Standard/Express flows (AWS) or Standard (Azure) qualify; flows with non-deterministic behavior or dependent on extensive conversational context must be redesigned before exposing them as tools.
Urgent migration and practical recommendations
The December 1, 2026 deadline for Foundry workflows forces Azure teams to migrate to Logic Apps Automation in less than 30 days; the official guide and the Form-to-Action reference repository must be used, validating end-to-end correlation via correlation ID. In AWS, there is no forced migration, but inventorying candidate flows and adopting MCP as a standard contract is recommended, which requires AgentCore Gateway or a custom MCP server implementation version 2025-11-25 for OBO token exchange.
To avoid token bloat, implement semantic tool search (MoEngage pattern): the agent describes the task and the gateway returns the relevant tool, reducing from >20k tokens to a few hundred per connection. Evaluate GPT-6.1 Terra on Bedrock for everyday cost/latency-sensitive workloads, validating on your own eval set because benchmarks are OpenAI figures, not independent tests.
Enable local CLI and typed SDK for Logic Apps Standard (preview) CI/CD, integrating them with GitHub Actions or Azure DevOps for policy-as-code and pre-deployment validation. Leverage the free Logic Apps Automation grants (108k exec-sec/month, 1 GB retention, 1k/500 Std/Ent connector calls) to validate agent-orchestrated architecture, remembering that the free managed environment lasts only 60 days and is not recurring.
Structured reference for readers and AI agents
{
"format": "rafael-fuentes-article/1.0",
"language": "en",
"title": "AWS and Microsoft enable native AI agent orchestration over enterprise flows",
"summary": "AWS and Microsoft expose Step Functions and Logic Apps as AI agent-invokable tools, preserving deterministic execution and reducing attack surface.",
"author": "Rafael Fuentes",
"publicationDate": "2026-11-04T06:01:35.096+01:00",
"eventDate": "2026-11-02",
"url": "https://falifuentes.com/rafael-fuentes-2026-11-04-am-en/",
"translation": {
"language": "es",
"url": "https://falifuentes.com/rafael-fuentes-2026-11-04-am-es/"
},
"topics": [
"AI",
"Artificial Intelligence",
"Automation and Robotics",
"Compliance and Regulations",
"English",
"OpenAI"
],
"sources": [
"https://aws.amazon.com/blogs/aws/aws-weekly-roundup-gpt-6-1-terra-on-bedrock-step-functions-as-agent-tools-and-more-november-2-2026",
"https://techcommunity.microsoft.com/blog/integrationsonazureblog/logic-apps-aviators-newsletter---november-2026/4569378"
]
}