Microsoft’s Agent Framework 1.20 adds native computer-use support, new vector-store connectors and changes to how Foundry hosts agent workflows. For developers, the headline is a broader set of building blocks, with some breaking changes to check before upgrading.
Microsoft AI Watch analysis
What happened
The Python release, dated 2 October, adds native computer-use support to Responses clients and Foundry project embeddings. New integrations include DuckDB and SQL Server vector-store connectors, plus a TypeSafe AI connector. Developers also get response-stream gates and buffering, session-scoped file-access isolation, and an optional way to inject function-invocation context into skill scripts.
The release redesigns Foundry hosting around request-scoped agent factories and persistent, sandbox-isolated sessions. It also adds durable invocation runs and configurable response history and background execution. Microsoft marks that hosting redesign as a breaking change. The release notes flag other breaking changes, including Gemini embedding options and changes to the experimental declarative workflow package. Read the Python release notes.
Why it matters
This is more than a connector top-up. The new hosting design changes how agent sessions and runs are managed, while session-scoped file isolation and changes to approval handling reach into the boundaries around what an agent can access and do. The new integrations and computer-use support also give teams more routes for connecting agents to data and tools.
That makes the upgrade potentially useful, but not a casual swap for every existing deployment. Teams using Foundry hosting or the affected experimental workflow and Gemini integrations should read the breaking-change notes and test their migration before rolling forward.
Our read
There is plenty here for developers building agents, especially if they need durable runs, isolated sessions or a wider choice of data connectors. The catch is that version numbers do not migrate production systems for you. Treat this as a substantial framework update: pick out the changes your stack needs, then give the breaking bits a proper test run.
What to watch
- How existing Foundry-hosted workflows adapt to the redesigned hosting model.
- Whether session-scoped file isolation and approval changes fit teams’ security requirements.
- Which connectors and computer-use capabilities developers adopt in real projects.
- Follow-up fixes or migration guidance for the breaking changes.
Discussion spark: Which change is most useful for agent developers: computer-use support, durable isolated sessions, or the new data connectors, and which breaking change would make you pause before upgrading?
Sources and evidence
- python-1.20.0 (2 October 2026, 14:54 UTC)
not affiliated with or endorsed by Microsoft