Network boundaries and code execution controls
Microsoft Agent Framework dotnet-1.27.0 introduces changes to network boundaries and runtime security. The release adjusts the default HTTP request handler to prevent client swapping during redirects. If a callback returns a custom client for a redirect destination, the handler now throws an exception before sending the redirected request. Developers must update callbacks to return null for allowed redirects or throw to block them entirely.
In addition to network restrictions, the release hardens provenance and process capability checks inside LocalCodeAct. The project also introduces a .NET consumer skill designed to help developers build agents with the framework.
Breaking storage and dependency upgrades
The release notes outline breaking changes in AgentServer dependencies. Applications hosted in Foundry must update their setup calls to ensure task and response storage share an identity and endpoint. Code using underlying SDKs directly must update several types, including changing string storage entity tags to Azure entity tags.
Durable response storage changes structure in this release, shifting state files to a new partitions directory. The release notes explicitly document that existing local response state files from earlier versions will not be read after updating, and the associated pull request supplies no migration tool for those files.
Workflow lifecycle and tool approval corrections
The release corrects multiple runtime execution bugs across core modules. In the Toolbox component, the engine now applies the configured tool approval policy as intended. Workflows also receive stability fixes, including the prompt release of workflow resources when an executor fails initialization and the preservation of pending Magentic plan reviews.
Memory state management also receives boundary protections. When restoring session state through the Mem0 integration, the framework now validates scopes before execution resumes.
Our assessment
Teams deploying Agent Framework dotnet-1.27.0 should audit redirect handlers to verify that custom client callbacks do not cause unexpected exceptions during web requests. Because pre-upgrade response state files are ignored without a migration path, developers relying on durable local sessions must plan for state resets or export critical data before upgrading. Operators should also verify whether previously ignored tool approval policies alter automated workflows.
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.
