Workflow scope isolation and runtime boundaries
Microsoft Agent Framework python-1.25.0 introduces architectural isolation rules across workflow instances. The framework binds live workflow executors and their associated sessions to a single authorization scope, blocking cross-scope execution attempts before model calls occur. When callers attempt cross-scope reuse, the runtime returns a scope conflict error code, and workflow agents configured as tools inside AG-UI endpoints are now rejected outright.
To accommodate these execution rules, developers must supply a factory that instantiates distinct workflows, executors, and sessions for each caller, unless an application explicitly restricts traffic to a single principal. The release also drops Python 3.10 support across the project, making Python 3.11 the minimum required interpreter version.
Tightened tool discovery and session handling
The update stops cross-workflow state leakage across Model Context Protocol components. The declarative package now establishes and terminates a separate protocol session for every handler call, including discovery listing, rather than reusing cached sessions. Consequently, implicit session continuity does not survive subsequent steps, approval delays, or checkpoint recoveries without explicit custom handles.
Catalog discovery receives strict protective boundaries in the core and declarative layers. Built-in discovery processes are constrained to 100 pages and 1,000 items per catalog, accompanied by a 30-second default timeout on framework-managed requests. Core security handling also fails closed whenever an invalid FIDES tool policy or altered invocation authority is detected.
External integrations receive corresponding privilege restrictions. In the GitHub Copilot module, bare session approvals for URL prompts drop back to one-time grants rather than inferring an entire hostname scope, requiring callers to declare explicit domain parameters for persistent access. Meanwhile, sandbox execution environments redact host-tool exception details before generated code continues running.
Our assessment
Teams running multi-tenant workflow services should audit whether their setups share executors across incoming requests, as this release immediately halts cross-scope execution. Engineering groups using MCP handlers must also verify if any multistep agent interactions depend on implicit session persistence across turns, switching to explicit session state handles if continuity fails.
Source: Microsoft original publication.
Read the original material
Microsoft (opens in a new tab)The article date belongs to Agentic Horizon. The source publication date is listed separately. Vendor claims remain attributed; we have not independently tested the reported capability.





