Microsoft Agent Framework for Python 1.17

Apply the Python 3 baseline first. These rules cover the agent-framework 1.17.0 distribution: agent and client construction, function tools, the function-invocation loop, approvals, middleware, the experimental agent_framework.security information-flow layer, MCP tools, sessions, workflows and checkpoints, hosting surfaces, and telemetry.

Version and runtime scope

• Lock agent-framework (or the matching agent-framework-core) and every provider package separately. The umbrella requires its matching core release, but core's all extra lists each provider without a version, so a resolver can choose any provider release whose own core requirement accepts that core, including releases cut for later framework versions. Lock and review the provider versions you tested. Keep MCP integrations within the declared mcp>=1.24.0,<2 range while refreshing the lockfile and following its advisories.
• Use a security-supported CPython minor that the whole deployment supports. 1.17.0 declares Python >=3.10 and its CI tests 3.10 through 3.14 on Linux and Windows, but 3.10 is end of life, so choose 3.11 through 3.14. Treat 3.15 as untested: core caps msgspec below 0.22, and no release in that range ships CPython 3.15 wheels. Core's all extra installs Hyperlight only on x86-64 Linux and AMD64 Windows below Python 3.14, and GitHub Copilot only on 3.11 or later, so confirm each integration you rely on is installed and tested on your interpreter and platform. An open-ended package requirement does not prove compatibility.
• Treat 1.17.0 as a breaking release for middleware