Head to head · Agent frameworks · October 2026 research run

Microsoft Agent Framework vs Strands Agents

Strands Agents and Microsoft Agent Framework score within a point of each other on agent readiness, 80 (A) and 79.4 (A). Microsoft Agent Framework leads on transparency & trust. Both do agent frameworks.

Best agent frameworks and SDKs · All 171 frameworks comparisons

Which one, for what

Microsoft Agent Framework A

Best for Teams on Azure or .NET, and for teams moving off AutoGen or Semantic Kernel, that want MCP, approval, checkpointed workflows and OpenTelemetry in one SDK.

Ahead on

  • Transparency & trust, 85 against 72

Also in its favour

  • Free to start without a card

Watch for

Changes marked [BREAKING] shipped in minor releases of released packages, including agent-framework-core in 1.22.0 on 15 October and 1.23.0 on 22 October 2026

Strands Agents A

Best for Python or TypeScript teams, especially on AWS, who want a model-driven loop with MCP, multi-agent patterns and approval gates.

Ahead on

  • Reliability, 87 against 78

Watch for

Three advisories in October 2026 on A2A session sharing and world-readable default session files, fixed in 1.43.0 and 1.48.0

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust Microsoft Agent Framework +13

Microsoft Agent Framework 85

MIT (30). The core README says what the User-Agent and feature token are, and a design spec in the repository says the token goes only to Foundry and Azure OpenAI pipelines and not to third-party providers. That spec is still marked proposed on 1 November, and we found no statement of how long Microsoft keeps the data and no privacy document for the framework (22). Package lifecycle states are published per package, experimental APIs raise warnings, breaking changes are dated in the Python changelog and there are upgrade guides, but we found no written support window (14). Telemetry is disclosed with two opt-out variables (20).

Strands Agents 72

Apache-2.0 (30). A library that stores session state where the developer configures it. The default FileSessionManager kept sessions world-readable in /tmp until 1.48.0, which the October advisories record and fix (20). A written deprecation policy with warnings and removal at majors, without a dated support window (16). Telemetry is opt-in and documented (20). 30+20+16+20 = 86.

Reliability Strands Agents +9

Microsoft Agent Framework 78

Read with the local-software lines. Official packages on PyPI (Requires-Python >=3.10 in the repository, though 1.24.0 makes Python 3.11 the supported baseline and says the next release drops 3.10) and NuGet (net8.0 to net10.0, netstandard2.0, net472) (20). Of the 15 most recent .NET build and test runs on 1 November 2026, 10 passed, 2 were cancelled and 4 wait for approval on a pull request, with none failed, and the scheduled runs on main passed on 31 October and 1 November (25). 610 open issues and 229 open pull requests on 1 November, up from 575 and 201 on 8 October. Closures and bug labels weren't re-counted (10). The Python changelog follows Keep a Changelog and states semantic versioning, and marks breaking changes, but they keep shipping in minor releases of released packages, such as agent-framework-core in 1.22.0 on 15 October and 1.23.0 on 22 October 2026 (8). Python 1.24.0 and .NET 1.27.0, with the root and core packages classed 5 - Production/Stable (15).

Strands Agents 87

Local-package reading. Official PyPI and npm packages with Python 3.10 and Node 22 stated (20). A public CI workflow runs lint, type checks, unit and integration tests for each package on pull requests to main, plus security-audit workflows, and the latest Python, TypeScript, harness and MCP runs on main passed on 6 November (25). 664 open issues and 1,151 open issues and pull requests on 6 November, with 545 issues opened in the 90 days to 3 November. Of the 50 newest, 12 had a comment and 15 were closed, and 9 of the 40 newest open items carry a bug label. An issue-responder workflow runs on new issues (12). A written semantic versioning policy, experimental APIs kept apart, and deprecations removed only at a major (15). 1.0 since 15 July 2025 (15). 20+25+12+15+15 = 87.

Score by category

CategoryWeight this runMicrosoft Agent FrameworkStrands AgentsEdge
Reliability16%207887Strands Agents +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29595even
Agent ergonomics13%16.28787even
Security & auth14%17.59389Microsoft Agent Framework +4
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89187Microsoft Agent Framework +4
Transparency & trust7%8.88572Microsoft Agent Framework +13
Negative events≤15-5-4
TotalA 79.4/100A 80/100

Facts side by side

FactMicrosoft Agent FrameworkStrands Agents
KindAgent frameworkAgent framework
VendorMicrosoftAmazon Web Services
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-302026-11-04
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Popularity14k stars, 48k PyPI/wk9.1k stars, 698k npm/wk, 8.9M PyPI/wk
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Microsoft Agent Framework

Python 1.24.0 and .NET 1.27.0 are MIT, past 1.0 and released about weekly, with an MCP client, tool approval, checkpointed graph workflows and OpenTelemetry. Breaking changes ship in minor releases, a version User-Agent and a feature-usage token are sent by default, and a high-severity advisory in the .NET declarative workflows package was published on 7 October 2026.

Strands Agents

An Apache-2.0 agent SDK for Python and TypeScript with a managed MCP client, multi-agent patterns, interrupts and Cedar policies for approval, opt-in OpenTelemetry and no usage analytics. Bedrock is the default model, the default sandbox is the local host, and three session-isolation advisories were fixed in October 2026.

Before you call either

Microsoft Agent Framework

  1. Pin exact versions. Minor releases have carried [BREAKING] changes, 1.23.0 moved MCP to the 2.x SDK, and 1.22.0 writes stored state older runtimes can't read, so read python/CHANGELOG.md first
  2. Set approval_mode="always_require" on tools and MCP servers that write. Tools run without approval unless set, and 1.24.0 warns when the MCP default is left implicit
  3. Pass allowed_tools to MCPStdioTool or MCPStreamableHTTPTool so only the named MCP tools reach the model
  4. Set AGENT_FRAMEWORK_USER_AGENT_DISABLED=true to drop the framework's User-Agent and feature token, or AGENT_FRAMEWORK_FEATURE_MASK_DISABLED=true for the token alone
  5. On .NET, use Microsoft.Agents.AI.Workflows.Declarative 1.24.0 or later. Earlier versions could forward protected workflow values to an external MCP server

Strands Agents

  1. Upgrade to strands-agents 1.48.0 or later, and set a private session directory rather than the /tmp default
  2. Pass a model explicitly when AWS credentials aren't configured, since Bedrock is the default
  3. Use interrupts or the harness's interventions for tools that write, send or pay
  4. Run shell and file tools in the Docker or SSH sandbox when the agent runs untrusted code
  5. Pin a minor version when using A2A, MCP or experimental modules

Questions

Which is better for AI agents, Microsoft Agent Framework or Strands Agents?

Strands Agents and Microsoft Agent Framework score within a point of each other on agent readiness, 80 (A) and 79.4 (A). Microsoft Agent Framework leads on transparency & trust.

Are Microsoft Agent Framework and Strands Agents open source?

Yes. Microsoft Agent Framework is open source (MIT). Strands Agents is open source (Apache-2.0).

Other comparisons with Microsoft Agent Framework or Strands Agents

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.