Microsoft’s Agent Framework .NET 1.28.0 release adds a GA computer tool for Foundry-hosted agents and changes how several agent and workflow features behave. The upgrade brings useful new capabilities, but teams will need to check the migration notes before moving across.
Microsoft AI Watch analysis
What happened
The release notes, dated 6 November, add FoundryAITool.CreateComputerTool() for computer-use calls and results in Foundry hosting, including batched actions. Microsoft also provides an Azure OpenAI computer-use sample. The Foundry project endpoint still requires the existing preview tool.
Several changes need attention. Built-in A2A server registration now supports message-based responses only, so applications relying on task responses, resumption or cancellation need another handler. The release also changes A2A agent identity setup to use A2AAgentOptions.
Other notable breaks include turning GitHub Copilot file hooks off by default, requiring declarative workflows to use an explicit HTTP host-and-port allowlist and application-owned handler factory, and creating a separate MCP client for each invocation. Host-tool exception details are now redacted by default in Hyperlight and LocalCodeAct; applications using trusted channels can opt in to detailed errors.
Why it matters
The computer tool is a practical addition for teams building agents that interact with a computer through Foundry. But this is not a drop-in upgrade for every application: changes to task handling, workflow HTTP access, MCP sessions and file hooks could alter existing behaviour or require code changes.
The new HTTP allowlist is particularly consequential for workflow builders. Entries must match exact hosts and ports, and the allowlist alone does not enforce HTTPS. Redirects and cookies must also be disabled in the configured handler. A security-minded default is welcome; the migration work is the price of admission.
Our read
This is a substantial framework release, not just a version-number nudge. Computer use expands what Foundry agents can do, while the breaking changes tighten defaults and reshape integration patterns. Read the migration guidance before upgrading, especially if your app depends on task-based A2A handling, file hooks, persistent MCP sessions or detailed tool errors.
What to watch
- Whether Microsoft expands computer-use support beyond the documented Foundry paths.
- How teams adapt applications that relied on task-based A2A responses or persistent MCP sessions.
- Whether the stricter workflow HTTP setup catches unsafe configurations without creating avoidable deployment friction.
Discussion spark: Are these security-conscious breaking defaults worth the migration burden, or should framework upgrades preserve existing behaviour unless teams opt in?
Sources and evidence
- dotnet-1.28.0 (9 November 2026, 11:56 UTC)
not affiliated with or endorsed by Microsoft