Skip to content
Talk to Us

Blocks.ai publishes this comparison and sells in this market. Every claim about another product links to a public source.

LangSmith vs Microsoft Agent 365

LangSmith

Platform for observing, evaluating, and deploying agents

Microsoft Agent 365

Microsoft 365 control plane to discover, manage, govern, and secure AI agents

Short answer

LangChain calls LangSmith a platform for observing, evaluating, and deploying agents; Microsoft Agent 365 is a Microsoft 365 control plane for agents built and run elsewhere.⁠Source 1, Source 2, Source 3, Source 4 LangSmith can host agents on Plus or above and prices per seat plus usage; Agent 365 is licensed per user, with agent identities in Microsoft Entra Agent ID.⁠Source 5, Source 6, Source 7, Source 8

By Blocks.ai teamLast checked

Where each one sits

Six layers of running AI agents at a company, and what each product’s own public sources say it covers.

These aren’t the same kind of product

Where they overlap
Both keep a list of agents, control who can use an agent, and record agent activity.⁠Source 9, Source 10, Source 11, Source 12, Source 13, Source 14
Where they differ
LangSmith is also where teams can build agents and run them.⁠Source 5, Source 15 Microsoft says the Agent 365 SDK doesn’t build, host, deploy, or execute agents.⁠Source 4
Running both
Microsoft names LangChain among the frameworks whose agents connect through the Agent 365 SDK, and LangSmith’s docs say it can trace agents hosted outside LangSmith.⁠Source 16, Source 17
Public sources · checked 2 October 2026
  • Offered
  • Preview
  • Not included
  • Not publicly documented

LangSmith

  • Build agents: OfferedFleet agent builder⁠Source 15
  • Host and run agents: OfferedLangSmith Deployment runtime⁠Source 5
  • Identity and access: OfferedFleet per-agent permissions⁠Source 10
  • Registry and governance: OfferedCentralized registry in Deployment⁠Source 9
  • Traffic between agents, tools, and models: OfferedFleet forwards MCP tool calls⁠Source 18
  • Agents across organizations: Not publicly documented

Microsoft Agent 365

  • Build agents: Not includedUse your chosen framework⁠Source 3
  • Host and run agents: Not includedYou host your agent⁠Source 4
  • Identity and access: OfferedEntra Agent ID⁠Source 7
  • Registry and governance: OfferedAgent registry in admin center⁠Source 12
  • Traffic between agents, tools, and models: PreviewTooling Gateway for MCP servers⁠Source 19
  • Agents across organizations: Not publicly documented

At a glance

TopicLangSmithMicrosoft Agent 365
Builds and runs agentsFleet builds agents without code, and LangSmith Deployment runs agents in production, on the Plus plan or above.⁠Source 5, Source 15Microsoft says the Agent 365 SDK doesn’t build, host, deploy, or execute agents; they keep running where they are, such as Azure, AWS, or on premises.⁠Source 4
Agents it coversAgents on LangSmith Deployment, which also runs other frameworks, and Fleet agents.⁠Source 15, Source 20 Agents hosted elsewhere can send traces.⁠Source 17Microsoft and third-party agents; Microsoft names LangChain, CrewAI, and the OpenAI Agents SDK among frameworks for SDK integration.⁠Source 2, Source 16
Identity and accessHosted agents require a LangSmith API key by default, or use your own auth handler.⁠Source 21 Fleet has per-agent Clone, Run, and Edit sharing permissions.⁠Source 10Agent identities live in Microsoft Entra Agent ID; each is a Microsoft Entra service principal.⁠Source 7
Pricing modelPer seat plus usage: one free Developer seat, Plus at $39 per seat a month, and usage metered in LangChain Standard Units (LSUs) at $1 each.⁠Source 6 Enterprise pricing is through sales.⁠Source 6Lists at $15 per user per month, or in Microsoft 365 E7.⁠Source 8 Basic identity and inventory come with Microsoft Cloud subscriptions; enterprise customers need Microsoft 365 E5, or E3 with the Defender and Purview suites.⁠Source 8
MaturityLangChain announced GA of LangGraph Platform (now Deployment) in May 2025 and Agent Builder (now Fleet) in January 2026.⁠Source 9, Source 22, Source 23, Source 24Generally available since 1 May 2026 for the Commercial segment.⁠Source 25

What each one is

LangSmith

LangChain describes LangSmith as a framework-agnostic platform for observing, evaluating, and deploying agents.⁠Source 1 LangSmith Deployment runs agents in production, and LangSmith Fleet is for creating and managing agents without code.⁠Source 5, Source 15 Workspace role-based access control and audit logs are Enterprise features.⁠Source 26, Source 27

Microsoft Agent 365

Microsoft Agent 365 is a Microsoft 365 service that provides a centralized control plane to discover, manage, govern, and secure AI agents.⁠Source 2 Admins can manage agents through its registry in the Microsoft 365 admin center, Microsoft Entra, and Microsoft Purview.⁠Source 25

The differences that matter

  1. Building and running agents

    LangSmith

    Fleet builds agents without code; LangSmith Deployment runs agents built with many frameworks, in LangChain’s cloud on Plus or above, or yours on Enterprise.⁠Source 5, Source 15, Source 17, Source 20

    Microsoft Agent 365

    Agent 365 governs agents built elsewhere, such as in your chosen framework or, for low-code, in Microsoft’s separate Copilot Studio.⁠Source 2, Source 3, Source 28

    Microsoft says the Agent 365 SDK doesn’t change where an agent runs; it works with agents on Azure, AWS, Google Cloud, or on premises.⁠Source 3

  2. Which agents each one lists

    LangSmith

    LangChain says Deployment manages agents in a centralized registry; listing agents hosted elsewhere is not publicly documented, though they can send traces.⁠Source 9, Source 17

    Microsoft Agent 365

    One registry lists Microsoft and non-Microsoft agents; agents built outside Microsoft 365 channels and Entra Agent ID need additional steps to appear.⁠Source 29, Source 30

  3. Identity and access

    LangSmith

    Hosted Agent Servers check a caller’s LangSmith API key, or run your own auth handler, on every request; Fleet has per-agent sharing permissions.⁠Source 10, Source 21

    Microsoft Agent 365

    Agent identities live in Microsoft Entra Agent ID, managed with Conditional Access, permission grants, and consent.⁠Source 7

    Self-hosted Agent Servers have no default authentication; Agent 365’s inventory also lists agents without an Entra agent identity.⁠Source 21, Source 29

For security teams

What a security review asks, answered from each vendor’s public documentation.

TopicLangSmithMicrosoft Agent 365
Network exposureEnterprise can reach LangSmith Cloud privately; on self-hosted LangSmith with Deployment, agents run behind an ingress you configure.⁠Source 31, Source 32Notifications (preview) need an endpoint Agent 365 sends to.⁠Source 33 Agent 365’s private networking is not publicly documented.
IdentityHosted agents require a LangSmith API key by default, or your auth handler; Cloud Enterprise adds SAML SSO and SCIM.⁠Source 21, Source 34Agent identities are Microsoft Entra service principals, managed with Conditional Access and consent; the inventory also lists agents without one.⁠Source 7, Source 29
Access changes and revocationFleet sharing can be revoked at any time; organization admins can deactivate or delete any member’s personal access token.⁠Source 11, Source 35Block agents organization-wide (only in Copilot Chat for SharePoint and Foundry agents), or disable all agents sharing an Entra blueprint.⁠Source 7, Source 13
Audit trailEnterprise audit logs record admin and configuration actions, kept up to 400 days; Fleet agent actions are traced.⁠Source 11, Source 27Supported agents’ activity shows in Defender, Purview, and the admin center; Purview’s agent audit logs need E7 or Agent 365.⁠Source 2, Source 3, Source 14
ComplianceLangChain’s Trust Center lists SOC 2 Type II, ISO 27001:2022, GDPR, and HIPAA for LangSmith.⁠Source 36Not yet a Core Online Service; runs on SOC- and ISO-audited services.⁠Source 14 Microsoft announced FedRAMP High authorization is pending.⁠Source 2

Full comparison

18 criteria in five groups. Every cell links to its source, or says no public source answers it.

LangSmith and Microsoft Agent 365 compared on 18 criteria
LangSmithMicrosoft Agent 365
What it is
What it is and who it’s forLangChain calls it a framework-agnostic platform for observing, evaluating, and deploying agents.⁠Source 1 Fleet, its no-code part, is for creating and managing agents.⁠Source 15Microsoft 365 service that provides a centralized control plane to discover, manage, govern, and secure AI agents, for IT and security leaders.⁠Source 2, Source 30
MaturityLangChain announced GA of LangGraph Platform (now Deployment) on 14 May 2025 and Agent Builder (now Fleet) on 13 January 2026.⁠Source 9, Source 22, Source 23, Source 24Generally available since 1 May 2026 for the Commercial segment.⁠Source 25 Registry sync and multi-tenant management are in preview.⁠Source 16, Source 37
Control
Agent registry and discoveryLangChain says Deployment manages agents in a centralized registry with versioning and rollbacks.⁠Source 9, Source 38 Fleet agents can be private or shared.⁠Source 39Agent registry in the Microsoft 365 admin center: one inventory of Microsoft and non-Microsoft agents, including agents without an Entra agent identity.⁠Source 12, Source 29
Identity and access controlHosted agents require a LangSmith API key by default, or use your own auth handler.⁠Source 21 Fleet has per-agent Clone, Run, and Edit sharing permissions.⁠Source 10Agent identities live in Microsoft Entra Agent ID, managed with Conditional Access, permission grants, and consent.⁠Source 7 The inventory also lists agents without one.⁠Source 29
Ownership, policy, and revocationFleet shows each agent’s owner, sharing can be revoked at any time, and agents can be set to pause for approval.⁠Source 11, Source 24 Enterprise adds custom roles.⁠Source 26Entra agent identities need a sponsor.⁠Source 7 Admins can block agents (SharePoint and Foundry ones only in Copilot Chat), approve activations, and apply templates.⁠Source 13, Source 40
Audit log and observabilityEnterprise audit logs record admin and configuration actions, kept up to 400 days.⁠Source 27 Each deployment gets a tracing project.⁠Source 41Supported agents’ activity shows in Defender, Purview, and the admin center.⁠Source 3, Source 14 Agent 365 keeps it 30 days; Purview’s agent audit logs need E7 or Agent 365.⁠Source 2, Source 14
Connection
How agents connectOn self-hosted LangSmith with Deployment, agents run behind an ingress you configure.⁠Source 32 Enterprise customers can reach LangSmith Cloud privately.⁠Source 31The SDK works with agents on Azure, AWS, Google Cloud, or on premises.⁠Source 3 Agent 365’s private networking is not publicly documented.
Agents across organizationsAgent Server agents can talk to other A2A-compatible agents.⁠Source 42 Access for agents owned by other organizations is not publicly documented.A published agent can join a customer tenant with tenant-local Entra identities.⁠Source 7 Cross-organization agent calls via Agent 365 are not publicly documented.
Protocol supportAgent Server supports A2A over JSON-RPC, with documented gaps, and can expose agents as MCP tools.⁠Source 42, Source 43 Fleet discovers tools from remote MCP servers.⁠Source 18Tenant-wide tool control; your own MCP servers in preview.⁠Source 2, Source 19 Microsoft documents A2A for its separate Foundry and standard-harness Copilot Studio, not Agent 365.⁠Source 44, Source 45
Frameworks, models, and clouds supportedLangSmith Deployment runs agents built with other frameworks, such as Google ADK, CrewAI, and AutoGen.⁠Source 20 Agents hosted elsewhere can send traces.⁠Source 17Microsoft and third-party agents; SDK docs name LangChain, CrewAI, and the OpenAI Agents SDK.⁠Source 2, Source 16 Premium capabilities may vary by agent type and platform.⁠Source 8
Operations
Deployment options and data residencyCloud on GCP (US, EU, APAC) or AWS (US).⁠Source 31 BYOC on AWS, or self-hosted or hybrid, on Enterprise.⁠Source 6, Source 17, Source 46Microsoft 365 service honoring the EU Data Boundary; observability content lives in the tenant’s default geography.⁠Source 2, Source 14 Self-hosting it is not publicly documented.
Compliance attestationsLangChain’s Trust Center lists SOC 2 Type II, ISO 27001:2022, GDPR, and HIPAA.⁠Source 36 SaaS data is encrypted with AES-256 at rest and TLS 1.2 or higher in transit.⁠Source 47Not yet a Core Online Service; runs on SOC- and ISO-audited services.⁠Source 14 Microsoft announced FedRAMP High authorization is pending.⁠Source 2
Support and SLABase, Standard, and Premium support plans.⁠Source 48 LangChain will use reasonable commercial efforts to provide 99.5% SaaS API uptime.⁠Source 48No specific SLA for the Frontier preview program.⁠Source 49 An SLA or support plan specific to the generally available service is not publicly documented.
Time and effort to get runningCloud deployment needs a Plus plan or above and an API key.⁠Source 50 Self-hosting the Deployment control plane needs Kubernetes, self-hosted LangSmith, and Enterprise.⁠Source 5Enterprise customers need Microsoft 365 E5, or E3 with Defender Suite and Purview Suite, and at least one user with an Agent 365 license.⁠Source 8, Source 25
Pricing model and public pricesOne free Developer seat; Plus is $39 per seat a month; Enterprise pricing is through sales.⁠Source 6 Usage is metered in LSUs, $1 each.⁠Source 6Per user, not per agent: lists at $15 a month standalone, or in Microsoft 365 E7.⁠Source 8 Microsoft Cloud subscribers get foundational capabilities at no extra cost.⁠Source 8
Building
Agent building toolsFleet builds agents from a description or a template, without code; code-first agents can be deployed with the LangGraph CLI.⁠Source 5, Source 15Microsoft says the Agent 365 SDK isn’t an agent-building framework.⁠Source 3 For low-code building, its docs point to Microsoft’s separate Copilot Studio.⁠Source 28
Model accessLangChain says LangSmith works with closed or open models.⁠Source 1 Fleet’s managed picker offers Fast, Pro, and Max tiers, not custom models.⁠Source 51Microsoft says the SDK doesn’t call or select models; the agent keeps making its own model calls.⁠Source 3, Source 4
Integrations and ecosystemFleet has built-in tools for Gmail, Slack, Google Calendar, and GitHub; LangChain says Fleet agents work in Slack, Teams, and Gmail.⁠Source 51, Source 52Launched with preintegrated partner agents and agents built on partner agent factories.⁠Source 53, Source 54 Work IQ MCP tools, in preview, cover Mail, Calendar, Teams, and more.⁠Source 55

Which to choose

Choose LangSmith if

  • You want one platform to build agents without code, run agents in production, and trace what they do.⁠Source 1, Source 5, Source 11, Source 15, Source 41
  • You need LangSmith’s control plane and Agent Servers in your own infrastructure, for full data residency or air-gapped use, on Enterprise.⁠Source 5
  • You want one runtime for agents from several frameworks: LangSmith Deployment runs agents built with Google ADK, CrewAI, AutoGen, and more.⁠Source 5, Source 20
  • You want other agents to call yours over A2A, which Agent Server supports with documented gaps, or use them as MCP tools.⁠Source 42, Source 43

Choose Microsoft Agent 365 if

  • You want agent identities in Microsoft Entra, managed with the same Conditional Access, consent, and lifecycle controls used elsewhere in Entra.⁠Source 7
  • You want one registry for Microsoft and non-Microsoft agents that also counts agents created or managed outside Agent 365.⁠Source 12, Source 29
  • You want to govern agents where they already run, such as Azure, AWS, Google Cloud, or on premises, without moving them.⁠Source 2, Source 3, Source 4
  • You use Microsoft’s separate Copilot Studio or Microsoft Foundry, which Microsoft says can provide built-in Agent 365 integration for some scenarios.⁠Source 16, Source 56

Questions buyers ask

Can Microsoft Agent 365 govern agents built with LangChain?

Microsoft says Agent 365 works with third-party agents and names LangChain among the frameworks whose agents connect through its SDK.⁠Source 2, Source 16 Agents built outside Microsoft 365 channels and Entra Agent ID need additional steps to appear in the inventory.⁠Source 30

Can LangSmith manage agents that run somewhere else?

It can trace them: agents run wherever you already run apps and send traces to LangSmith.⁠Source 17 Listing them in a LangSmith registry is not publicly documented. LangSmith Deployment can also run agents built with other frameworks.⁠Source 20

Do they support MCP and A2A?

LangSmith’s Agent Server supports A2A, with documented gaps, and can expose agents as MCP tools.⁠Source 42, Source 43 Agent 365 can control tool access tenant-wide, with your own MCP servers in preview.⁠Source 2, Source 19 Microsoft documents A2A for its separate Foundry and standard-harness Copilot Studio, not Agent 365.⁠Source 44, Source 45

How is each one priced?

LangSmith has one free Developer seat, Plus at $39 per seat a month, and Enterprise through sales; usage is metered in LSUs, $1 each.⁠Source 6 Agent 365 lists at $15 per user a month or in Microsoft 365 E7; foundational capabilities come with Microsoft Cloud subscriptions.⁠Source 8

How we compare

Read the full method

Every claim on this page links to a public source. Where none answers a question, the page says so.

We re-check every fact at least every 90 days. This page was last checked .

Something wrong or out of date? Tell us and we’ll correct it.

Sources

61 public sources, each with the date we checked it. Every one opens in a new tab.

  1. Source 1: LangSmith: The Agent Engineering Platform LangChain · checked Back:abcde

  2. Source 2: Microsoft Agent 365 - Service Descriptions | Microsoft Learn Microsoft · checked Back:abcdefghijklmno

  3. Source 3: Agent 365 SDK frequently asked questions | Microsoft Learn Microsoft · checked Back:abcdefghij

  4. Source 4: Microsoft Agent 365 SDK overview | Microsoft Learn Microsoft · checked Back:abcdef

  5. Source 5: LangSmith Deployment LangChain · checked Back:abcdefghijk

  6. Source 6: LangSmith Plans and Pricing LangChain · checked Back:abcdefg

  7. Source 7: Agent 365 identity | Microsoft Learn Microsoft · checked Back:abcdefghijk

  8. Source 8: Licensing Documents Microsoft · checked Back:abcdefgh

  9. Source 9: LangSmith Deployment LangChain · checked Back:abcdef

  10. Source 10: Agent platform comparison LangChain · checked Back:abcde

  11. Source 11: Access & oversight LangChain · checked Back:abcde

  12. Source 12: Agent Registry in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Microsoft · checked Back:abcd

  13. Source 13: Governance and Lifecycle actions for agents available in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Microsoft · checked Back:abc

  14. Source 14: Data handling, data residency, and compliance in Agent 365 observability | Microsoft Learn Microsoft · checked Back:abcdefg

  15. Source 15: No-code agents with LangSmith Fleet LangChain · checked Back:abcdefghi

  16. Source 16: Choose an Agent 365 Integration Option | Microsoft Learn Microsoft · checked Back:abcdefg

  17. Source 17: Set up LangSmith LangChain · checked Back:abcdefgh

  18. Source 18: Remote MCP servers LangChain · checked Back:ab

  19. Source 19: Bring your own (BYO) MCP server in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Microsoft · checked Back:abc

  20. Source 20: Deploy other frameworks LangChain · checked Back:abcde

  21. Source 21: Authentication & access control LangChain · checked Back:abcde

  22. Source 22: LangGraph Platform is now Generally Available: Deploy & manage long-running, stateful Agents LangChain · checked Back:ab

  23. Source 23: Now GA: LangSmith Agent Builder LangChain · checked Back:ab

  24. Source 24: LangSmith Fleet changelog LangChain · checked Back:abc

  25. Source 25: Microsoft Agent 365 overview | Microsoft Learn Microsoft · checked Back:abcd

  26. Source 26: Role-based access control LangChain · checked Back:ab

  27. Source 27: Audit logs LangChain · checked Back:abc

  28. Source 28: Get started with Microsoft Agent 365 | Microsoft Learn Microsoft · checked Back:ab

  29. Source 29: Agent Registry convergence with Microsoft Agent 365 | Microsoft Learn Microsoft · checked Back:abcdef

  30. Source 30: Microsoft Agent 365: The Control Plane for Agents Microsoft · checked Back:abc

  31. Source 31: Cloud (SaaS) LangChain · checked Back:abc

  32. Source 32: Enable additional LangSmith features LangChain · checked Back:ab

  33. Source 33: Agent Messaging Endpoint | Microsoft Learn Microsoft · checked Back to text

  34. Source 34: Authentication methods LangChain · checked Back to text

  35. Source 35: Overview (administration) LangChain · checked Back to text

  36. Source 36: Trust Center - LangChain LangChain · checked Back:ab

  37. Source 37: Manage agents across multiple tenants in the Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Microsoft · checked Back to text

  38. Source 38: Assistants LangChain · checked Back to text

  39. Source 39: Manage agent settings LangChain · checked Back to text

  40. Source 40: Policy templates | Microsoft Learn Microsoft · checked Back to text

  41. Source 41: LangSmith control plane LangChain · checked Back:ab

  42. Source 42: A2A endpoint in Agent Server LangChain · checked Back:abcd

  43. Source 43: MCP endpoint in Agent Server LangChain · checked Back:abc

  44. Source 44: Connect to an agent over the Agent2Agent (A2A) protocol - Microsoft Copilot Studio | Microsoft Learn Microsoft · checked Back:ab

  45. Source 45: Connect to an A2A agent endpoint from Foundry Agent Service - Microsoft Foundry | Microsoft Learn Microsoft · checked Back:ab

  46. Source 46: Bring Your Own Cloud (BYOC) LangChain · checked Back to text

  47. Source 47: LangSmith shared responsibility model LangChain · checked Back to text

  48. Source 48: Support Plans LangChain · checked Back:ab

  49. Source 49: Preview Agent 365 features through the Frontier program | Microsoft Learn Microsoft · checked Back to text

  50. Source 50: Deploy your app to cloud LangChain · checked Back to text

  51. Source 51: Essentials LangChain · checked Back:ab

  52. Source 52: LangSmith Fleet LangChain · checked Back to text

  53. Source 53: Ecosystem partner agents available in Agent 365 | Microsoft Learn Microsoft · checked Back to text

  54. Source 54: Microsoft Agent 365, now generally available, expands capabilities and integrations | Microsoft Security Blog Microsoft · checked Back to text

  55. Source 55: Connect existing agents to Microsoft Agent 365 | Microsoft Learn Microsoft · checked Back to text

  56. Source 56: What is Microsoft Foundry? - Microsoft Foundry | Microsoft Learn Microsoft · checked Back to text

  57. Source 57: Your company's private network Blocks.ai · checked Back to text

  58. Source 58: Network requirements Blocks.ai · checked Back to text

  59. Source 59: Solutions: Agent sprawl Blocks.ai · checked Back to text

  60. Source 60: Solutions: Partner networks Blocks.ai · checked Back to text

  61. Source 61: Pricing Blocks.ai · checked Back to text