LangGraph vs Microsoft Agent Framework · Reviewed Nov 2026

LangGraph vs Microsoft Agent Framework

Choose LangGraph when you want direct control of stateful agent orchestration in your application. Choose Microsoft Agent Framework when its agent, workflow, session, and integration abstractions fit your existing development stack.

Reviewed Nov 2026Graph frameworkWorkflow framework

Quick answer

Choose LangGraph when you want direct control of stateful agent orchestration in your application. Choose Microsoft Agent Framework when its agent, workflow, session, and integration abstractions fit your existing development stack.

LangGraphMicrosoft Agent Framework

This is not a comparison between a graph framework and a framework without graphs. Microsoft Agent Framework documents explicit graph-based workflows, while LangGraph offers both graph and functional APIs. The useful distinction is which runtime model, message contracts, and integration surfaces your team wants to standardize on. Microsoft workflow concepts LangGraph Functional API

LangGraph describes itself as a low-level runtime for long-running, stateful agents. Microsoft presents agents, workflows, and integrations together with sessions, context providers, middleware, and model clients. Compare those application boundaries before comparing individual orchestration examples. A short tutorial is unlikely to exercise the recovery and approval paths that determine operational fit. LangGraph overview Microsoft Agent Framework overview

How do LangGraph and Microsoft Agent Framework compare on specs?

SpecLangGraphMicrosoft Agent Framework
Control flowGraph API and Functional APIGraph workflows across SDKs; experimental Python functional workflows
Persistent executionCheckpointers and thread-associated stateWorkflow checkpoints and SDK-specific checkpoint configuration
External inputDynamic interrupts resumed through CommandWorkflow request and response mechanisms
Agent architectureNot prescribed by the runtimeAgent abstractions alongside workflow and integration components
Migration contextEvaluate against the application you needMicrosoft provides an AutoGen migration guide
LanguagesPython and JavaScript/TypeScriptPython, .NET; Go preview
LicenseMITMIT
TracingLangSmithOpenTelemetry
A2ALangSmith Agent ServerHosting samples; Foundry Agent Service A2A v1.0 generally available

How do LangGraph and Microsoft Agent Framework coordinate agents?

In LangGraph, the Graph API puts shared state and transitions at the center. The Functional API instead uses ordinary control flow with entrypoints and tasks. Both use the same underlying runtime, but their checkpoint and visualization behavior differs. Pick an API according to how you want developers to inspect dependencies and replay work, not because a diagram looks simpler. LangGraph Functional API

Microsoft workflows coordinate executors through explicit paths. Its workflow concepts distinguish graph execution from the experimental Python functional API, including differences in event granularity and checkpointing. Those are materially different development contracts inside one framework, so confirm the API and language of every example you intend to adopt. Microsoft workflow concepts

When should you choose LangGraph, and when Microsoft Agent Framework?

Choose LangGraph if

  • Choose LangGraph when an existing Python or JavaScript application needs a stateful orchestration component rather than a broader agent programming model. Keep application interfaces separate from any optional deployment platform.
  • Choose LangGraph when developers need to decide exactly where deterministic checks sit between model calls. Document state updates and ownership so that parallel branches cannot accidentally overwrite each other.
  • Choose LangGraph when your evaluation depends on thread-specific interruptions and checkpoint inspection. Design the approval interface and persistence lifecycle as part of the same feature.

Choose Microsoft Agent Framework if

  • Choose Microsoft Agent Framework when your team wants to work with its model clients, sessions, middleware, and workflow APIs as a coordinated application surface. Confirm each required integration in the selected language.
  • Choose Microsoft Agent Framework when a .NET application needs framework-supported agent and workflow abstractions. Compare concrete executor and message contracts rather than translating a Python sample mechanically.
  • Choose Microsoft Agent Framework when moving an AutoGen application toward Microsoft’s documented successor. Use the migration guide as a mapping exercise, then test the behavior of your actual agents and tools.

Can you use LangGraph and Microsoft Agent Framework together?

Using both runtimes is justified when separate teams already own services with stable interfaces. Keep each runtime’s internal checkpoints private and exchange explicit requests, results, and cancellation signals instead of sharing mutable execution state. If those services and people need a common interaction surface, BAND (band.ai) provides rooms and timelines around their existing loops. Its integration paths include A2A adapter or gateway connections, ACP server or client connections, and MCP tooling; those paths do not make runtime state interchangeable. BAND integrations

How much do LangGraph and Microsoft Agent Framework cost?

PlanPriceWhat you get
LangGraph applicationDeployment dependentSeparate model consumption, checkpoint storage, application hosting, and any optional hosted tracing or deployment service.
Microsoft Agent Framework applicationDeployment dependentSeparate SDK selection from model-provider usage, cloud resources, persistence, telemetry, and engineering operations. No hosted-service amount is assumed here.

Prices from vendor pages, November 2026

What do each framework's checkpoints actually preserve?

Microsoft documents graph-workflow checkpoints at superstep boundaries, capturing executor state, pending messages, requests, and shared state. Its Python checkpoint documentation also describes version-specific entry checkpoints. Pin the package version and verify which events are present when an operator resumes or inspects a run. Microsoft workflow checkpoints

LangGraph interrupts save state and wait for external input, with thread_id identifying the persisted execution context. An approval service must carry the right identifier and authenticate the person supplying the decision. Persistence does not, by itself, establish permission to resume a customer’s workflow. LangGraph interrupts

How should you map execution state during migration?

A node, executor, session, and thread are not interchangeable just because each carries information between model calls. Write down what is persisted, what can be reconstructed, and which process owns the next action. During migration, preserve user-visible outcomes first: when approval is requested, which tool arguments are approved, and what happens if the worker exits after an external write.

What should a meaningful workflow prototype include?

Build a document-review workflow with parallel evidence collection, a deterministic completeness check, a human correction, and a final publication action. Stop the process before and after approval and inspect the recovery path. Compare the implementation and operator effort of each version, without presenting the exercise as a published benchmark or assuming either runtime guarantees exactly-once external effects.

What else do people ask about LangGraph vs Microsoft Agent Framework?

Does Microsoft Agent Framework support graphs?

Yes. Its workflow documentation describes graph-based workflows and explicit execution paths. Python also has an experimental functional workflow API, so verify the API status for the language you choose. Microsoft workflow concepts

Is LangGraph limited to graph declarations?

No. The Functional API adds persistence, interrupts, and streaming to ordinary functions using entrypoints and tasks. It has different visualization and state conventions from the Graph API. LangGraph Functional API

Can either framework pause for a person?

Both document mechanisms for external human input. LangGraph uses interrupts; Microsoft workflows expose request and response mechanisms. Your application still needs an authenticated approval surface and a durable way to correlate the response.

Should an AutoGen team automatically choose Microsoft?

Microsoft supplies a migration guide and directs AutoGen users toward Agent Framework. That makes it an important candidate, not a substitute for checking your tools, termination rules, state model, and operational requirements. AutoGen migration guide

Which comparisons should you read next?

BAND vs LangGraph

Not either/or. LangGraph builds the agent; BAND lets it work with agents from other frameworks and with people.

Shared interaction infrastructureGraph framework
Read comparison

LangGraph vs Google ADK (Agent Development Kit)

LangGraph for deep control in Python or TypeScript; ADK for five languages and Google Cloud. BAND connects both.

Graph frameworkMulti-language framework
Read comparison

Microsoft Agent Framework vs AutoGen

Agent Framework is AutoGen's successor. Start new work there and plan the migration for existing code.

Workflow frameworkArchived
Read comparison