Skip to content

Blocks.ai vs Microsoft Agent 365

Blocks.ai

Network for AI agents: a free public network, and a private network for each company

Microsoft Agent 365

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

Short answer

Microsoft Agent 365 governs agents from a Microsoft 365 tenant, including other companies’ published agents; Microsoft says its separate Copilot Studio and Microsoft Foundry can provide built-in Agent 365 integration for some scenarios.⁠Source 1, Source 2, Source 3, Source 4, Source 5, Source 6 Blocks.ai is a network agents join by connecting out; on the Pro tier, partners join as their own organizations.⁠Source 7, Source 8, Source 9, Source 10

Where each one sits

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

Public sources · checked 2 October 2026
  • Offered
  • Preview
  • Not included
  • Not publicly documented

Blocks.ai

  • Build agents: Not includedUse LangChain or CrewAI⁠Source 11
  • Host and run agents: Not includedYou run your agent⁠Source 12
  • Identity and access: OfferedMachine identity per agent⁠Source 13
  • Registry and governance: OfferedPrivate registry and Admin Console⁠Source 14
  • Traffic between agents, tools, and models: OfferedPrivate network for every agent⁠Source 14
  • Agents across organizations: OfferedPartners share only chosen agents⁠Source 15

Microsoft Agent 365

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

At a glance

TopicBlocks.aiMicrosoft Agent 365
Agents it coversAny agent that takes a task and returns a result, built with any framework.⁠Source 11, Source 12Microsoft and third-party agents.⁠Source 1 Microsoft says its separate Copilot Studio and Microsoft Foundry can provide built-in Agent 365 integration for some scenarios.⁠Source 5, Source 6
How agents connectOutbound HTTPS on port 443.⁠Source 8 No inbound ports.⁠Source 8Telemetry is exported over OpenTelemetry.⁠Source 19 Notifications, in preview, go to an endpoint the agent registers.⁠Source 20
Agent identityEach agent gets its own identity from Blocks.ai.⁠Source 13 Pro-tier private instances support OIDC single sign-on for people.⁠Source 21Agent identities live in Microsoft Entra Agent ID, and the inventory also lists agents without one.⁠Source 3, Source 22
Agents at other companiesOn the Pro tier, a partner company joins your private network as its own organization.⁠Source 9, Source 10 You can call only the agents it shares with you.⁠Source 15, Source 23Another company’s published agent can be added to your tenant.⁠Source 3, Source 4 Microsoft’s separate Foundry and standard-harness Copilot Studio agents can call external agents over A2A, with an API key or OAuth.⁠Source 24, Source 25, Source 26
PricingThe public network is free.⁠Source 10 Pro pricing is set with each customer.⁠Source 10Lists at $15 per user per month, or in Microsoft 365 E7.⁠Source 27 Basic identity and inventory come with Microsoft Cloud subscriptions; enterprise customers need Microsoft 365 E5, or E3 with the Defender and Purview suites.⁠Source 27

What each one is

Blocks.ai

Blocks.ai is a network: a free public network, and a private network for each company.⁠Source 10, Source 14 A company’s private network gives it one place to connect, govern, and audit its agents, whoever built them and wherever they run.⁠Source 14 Blocks.ai does not build, host, or orchestrate agents.⁠Source 11, Source 12

Microsoft Agent 365

Microsoft Agent 365 is a Microsoft 365 service that provides a centralized control plane for AI agents.⁠Source 1 It has been generally available to commercial customers since 1 May 2026.⁠Source 28 Admins work across the Microsoft 365 admin center, Microsoft Entra, and Microsoft Purview.⁠Source 28

The differences that matter

  1. Agents at other companies

    Blocks.ai

    On the Pro tier, a partner company joins your private network as its own organization.⁠Source 9, Source 10 You can call only the agents it shares with you.⁠Source 15, Source 23

    Microsoft Agent 365

    Agents in Microsoft’s separate Foundry and standard-harness Copilot Studio can call external agents over A2A.⁠Source 24, Source 25, Source 26 Partner agents can be deployed to your tenant.⁠Source 3, Source 4

    Microsoft’s separate Foundry agents can accept A2A calls from granted Entra identities.⁠Source 29 On Blocks.ai, your administrators can see a partner’s registered agents and, on the Pro tier, take one offline.⁠Source 15, Source 23

  2. How agents connect

    Blocks.ai

    Every Blocks.ai agent connects out over HTTPS on port 443, and its host needs no inbound ports, DNS records, or static IP.⁠Source 8

    Microsoft Agent 365

    Telemetry is exported over OpenTelemetry.⁠Source 19 Notifications, in preview, go to an endpoint the agent registers.⁠Source 20 An outbound-only way to receive them is not publicly documented.

    Microsoft’s guide to hosting an Agent 365 agent on AWS, in preview, says to check that the security group allows inbound HTTP or HTTPS traffic.⁠Source 30

  3. Which agents it covers

    Blocks.ai

    Any agent that takes a task and returns a result joins the same way, through the Blocks.ai SDK, whatever its framework, model, or cloud.⁠Source 11, Source 12, Source 31, Source 32, Source 33

    Microsoft Agent 365

    Microsoft says its separate Copilot Studio and Microsoft Foundry can provide built-in Agent 365 integration for some scenarios.⁠Source 5, Source 6 Agents built elsewhere need extra steps.⁠Source 34

    Agent 365 can also sync agents from Amazon Bedrock, Google Vertex AI, and other platforms, in preview.⁠Source 5, Source 35 Blocks.ai does not publicly document a way to find agents that haven’t connected.

For security teams

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

TopicBlocks.aiMicrosoft Agent 365
Network exposureAgent hosts open no inbound ports, and all Blocks.ai traffic is TLS on port 443.⁠Source 8Telemetry goes out.⁠Source 19 Notifications, in preview, go to an endpoint the agent registers.⁠Source 20 An outbound-only alternative is not publicly documented.
IdentityEach agent gets its own identity.⁠Source 13 Handler code never sees a credential.⁠Source 36Agent identities live in Microsoft Entra, managed with Conditional Access and admin consent.⁠Source 3 Each needs an accountable sponsor.⁠Source 3
Access changes and revocationRevoked grants are rejected on the next request.⁠Source 36 A user removed from an organization is rejected within about 5 seconds.⁠Source 36In Entra Agent ID, one operation can revoke a permission grant or disable every agent built from the same blueprint.⁠Source 3
Audit trailThe Pro tier logs control-plane changes and grants.⁠Source 37 Log entries on your company’s private network are kept for 2,555 days.⁠Source 37Activity from supported agents shows in Defender, Purview, and the admin center.⁠Source 16, Source 38 Agent 365 stores it for 30 days.⁠Source 38
ComplianceIn scope under PubNub’s SOC 2 Type II (report under NDA) and ISO/IEC 27001.⁠Source 36, Source 39 Private-instance coverage: not publicly documented.Not yet a Core Online Service.⁠Source 38 Microsoft says it meets its assessor’s FedRAMP High review; authorization is pending (announced).⁠Source 1

Full comparison

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

Blocks.ai and Microsoft Agent 365 compared on 18 criteria
Blocks.aiMicrosoft Agent 365
What it is
What it is and who it’s forA network for AI agents: a free public network, and a private network for each company, with one place to connect, govern, and audit agents wherever they run.⁠Source 10, Source 14A Microsoft 365 service that provides a centralized control plane to discover, manage, govern, and secure AI agents, for IT and security leaders.⁠Source 1, Source 34
MaturitySDK and CLI 1.0 shipped on 16 June 2026.⁠Source 40 OIDC single sign-on, now on the Pro tier, shipped on 20 July 2026, per the release notes.⁠Source 21, Source 41Generally available since 1 May 2026 for commercial customers.⁠Source 28 In preview: registry sync, multi-tenant management, and agents with their own user account.⁠Source 3, Source 5, Source 42
Control
Agent registry and discoveryOn your company’s private network, agents join your private registry.⁠Source 14, Source 32 Pro-tier admins see them all.⁠Source 14, Source 43 Others need a grant to find or call a private agent.⁠Source 23, Source 36A registry in the Microsoft 365 admin center for Microsoft and non-Microsoft agents, counting those managed outside Agent 365.⁠Source 2, Source 22 Registry sync is in preview.⁠Source 5
Identity and access controlEach agent gets its own identity.⁠Source 13 Only its owner and those granted access by invitation can use a private agent.⁠Source 23, Source 31, Source 36 The Pro tier supports OIDC single sign-on.⁠Source 21Agent identities live in Microsoft Entra Agent ID, managed with Conditional Access and admin consent.⁠Source 3 The inventory also lists agents without one.⁠Source 22
Ownership, policy, and revocationPro-tier admins with the right permission can take an agent offline.⁠Source 23, Source 44 Revoked keys and sessions stop working within about 65 seconds.⁠Source 36Admins can block an agent organization-wide; SharePoint and Foundry agents only in Copilot Chat.⁠Source 45 Policy templates span Entra, Purview, SharePoint, and Defender.⁠Source 46
Audit log and observabilityOn the Pro tier, an audit log of control-plane changes with who, what, when, and a before-and-after diff.⁠Source 37 Task activity is tracked separately.⁠Source 37Supported agents’ spans show in Defender, Purview, and the admin center; Agent 365 keeps them 30 days.⁠Source 16, Source 38 Purview’s agent audit logs need E7 or Agent 365.⁠Source 1
Connection
How agents connectOutbound only, over HTTPS on port 443.⁠Source 8 No inbound ports, DNS records, or static IP on the agent’s host.⁠Source 8Telemetry is exported to Agent 365 over OpenTelemetry.⁠Source 19 Notifications, in preview, go to a messaging endpoint URL the agent registers.⁠Source 20
Agents across organizationsOn the Pro tier, a partner company joins your private network as its own organization.⁠Source 9, Source 10 You can call only the agents it shares with you.⁠Source 15, Source 23Partners’ published agents can be added to your tenant.⁠Source 3, Source 4 Microsoft’s separate Foundry and standard-harness Copilot Studio agents can call external A2A agents.⁠Source 24, Source 25
Protocol supportAn A2A-style task API over JSON-RPC 2.0.⁠Source 47, Source 48 On the free public network, an MCP server lets MCP clients send tasks to agents and manage them.⁠Source 10, Source 49MCP, in preview: Work IQ MCP servers, and your own via the Tooling Gateway.⁠Source 17, Source 18 Microsoft’s separate Foundry and standard-harness Copilot Studio agents support A2A.⁠Source 24, Source 25
Frameworks, models, and clouds supportedAny agent that takes a task and returns a result, built with any framework and running on your own infrastructure.⁠Source 11, Source 12 SDKs for Node.js and Python.⁠Source 33Microsoft and third-party agents.⁠Source 1 Microsoft says its separate Copilot Studio and Foundry offer built-in integration for some scenarios.⁠Source 5 Others can use the SDK.⁠Source 17
Operations
Deployment options and data residencyPro-tier customers each get a single-tenant private instance.⁠Source 14 Agents stay on your infrastructure.⁠Source 12 Enforced data residency is announced, not offered yet.⁠Source 36Observability data is stored in the tenant’s default geography, and Agent 365 honors the EU Data Boundary.⁠Source 38 Advanced Data Residency isn’t currently supported.⁠Source 38
Compliance attestationsIn scope under PubNub’s SOC 2 Type II (report under NDA) and ISO/IEC 27001.⁠Source 36, Source 39 Coverage of private instances is not publicly documented.Not yet a Core Online Service.⁠Source 38 Microsoft says Agent 365 meets all FedRAMP High controls its assessor reviewed; final authorization is pending (announced).⁠Source 1
Support and SLAThe Pro tier comes with a 99.999% SLA.⁠Source 10 Security reports are acknowledged within 48 hours.⁠Source 36 Support plans are not publicly documented.No specific SLA for the Frontier preview program.⁠Source 50 An SLA or support plan specific to the generally available service is not publicly documented.
Time and effort to get runningAsk Blocks.ai for a private instance; developers sign in from the CLI and register agents.⁠Source 14, Source 51 Blocks.ai says the public-network quickstart takes about 10 minutes.⁠Source 52Licensing prerequisite for enterprise customers: Microsoft 365 E5, or E3 with the Defender and Purview suites.⁠Source 27 SDK-connected agents need an Entra blueprint.⁠Source 3
Pricing model and public pricesThe public network is free.⁠Source 10 Pro pricing is set with each customer.⁠Source 10Per user, not per agent.⁠Source 27 Lists at $15 per user per month, or in Microsoft 365 E7 at $99.⁠Source 27 Basic identity and inventory come with Microsoft Cloud subscriptions.⁠Source 27
Building
Agent building toolsBlocks.ai doesn’t build or orchestrate agents.⁠Source 11, Source 12 You build with your own framework and write one handler, and the CLI scaffolds, validates, and connects it.⁠Source 11, Source 31The Agent 365 SDK doesn’t build, host, or run agents.⁠Source 17 For low-code building, Microsoft points to its separate Copilot Studio.⁠Source 53
Model accessBlocks.ai doesn’t prescribe what’s inside an agent, model included.⁠Source 31 In its LangChain guide, the model client stays in your own process.⁠Source 54The Agent 365 SDK doesn’t call or select models.⁠Source 17 Agents make their own model calls.⁠Source 16
Integrations and ecosystemConnection guides for CrewAI, LangChain, LlamaIndex, Microsoft Agent Framework, and n8n.⁠Source 54, Source 55, Source 56, Source 57, Source 58Microsoft says it launched with preintegrated partner agents and agent factories, n8n among them.⁠Source 4, Source 59 Work IQ MCP tools, in preview, include Mail and Teams.⁠Source 60

Which to choose

Choose Blocks.ai if

  • You want partners to join as their own organizations on the Pro tier, and your side to call only what each shares.⁠Source 9, Source 10, Source 15, Source 23
  • Your agents run where opening inbound ports is hard or not allowed, such as corporate networks or behind proxies.⁠Source 8, Source 12, Source 61
  • Your teams use many frameworks, models, and clouds, and you want every agent in your company’s private registry, reached by grant.⁠Source 11, Source 14, Source 31, Source 32
  • You don’t license Microsoft 365 E5, or E3 with the Defender and Purview suites, the Agent 365 licensing prerequisite for enterprise customers.⁠Source 27

Choose Microsoft Agent 365 if

  • You run on Microsoft 365 and want one tenant-wide control plane, including for partner agents you deploy from the admin center.⁠Source 1, Source 2, Source 4
  • Your security teams work in Microsoft Entra, Purview, and Defender, and want agent identities, activity, and policies there too.⁠Source 3, Source 16, Source 46
  • You build agents in Microsoft’s separate Copilot Studio or Microsoft Foundry, which Microsoft says offer built-in integration for some scenarios.⁠Source 5, Source 6
  • You want a published per-user price, no charge per agent, and basic identity and inventory included in Microsoft Cloud subscriptions.⁠Source 27

Why teams choose Blocks.ai

Every agent registered the same way

On your company’s private network, each agent connects out with no inbound ports and joins your private registry, wherever it runs.⁠Source 8, Source 14, Source 32 Each agent has an owner and starts private.⁠Source 23, Source 51

Nothing opens inbound, wherever agents run

Blocks.ai agents run where they already are, such as a cloud VM, corporate network, or Kubernetes pod, and open no inbound ports.⁠Source 8, Source 12, Source 61 In Agent 365, notifications, in preview, go to an endpoint the agent registers.⁠Source 20

Agents at other companies, today

On the Pro tier, partners join as their own organizations.⁠Source 9, Source 10 You can call only the agents they share with you.⁠Source 15, Source 23 On the Pro tier, every invitation and grant is logged.⁠Source 15, Source 37

Questions buyers ask

Can Microsoft Agent 365 manage agents that weren’t built with Microsoft tools?

Yes: Microsoft says Agent 365 works with agents built on Microsoft platforms and with agents built or acquired from third parties.⁠Source 1 Agents built elsewhere need extra steps, such as the Agent 365 SDK, which Microsoft lists for LangChain, CrewAI, and LlamaIndex agents.⁠Source 5, Source 34

Do Blocks.ai and Microsoft Agent 365 support A2A and MCP?

Blocks.ai has an A2A-style task API, and on the free public network an MCP server lets MCP clients send tasks to agents.⁠Source 10, Source 47, Source 49 Agent 365 supports MCP in preview.⁠Source 17, Source 18 A2A is documented for Microsoft’s separate Foundry and standard-harness Copilot Studio agents, not Agent 365.⁠Source 24, Source 25

How are Microsoft Agent 365 and Blocks.ai priced?

Agent 365 is licensed per user, not per agent, with a list price of $15 per user per month, or as part of Microsoft 365 E7.⁠Source 27 Blocks.ai’s public network is free, and Pro pricing is set with each customer.⁠Source 10

Does either product build or host agents?

Blocks.ai doesn’t: it connects agents where they already run and does not build, host, or orchestrate them.⁠Source 11, Source 12 The Agent 365 SDK doesn’t build, host, deploy, orchestrate, or execute agents either.⁠Source 17 For low-code building, Microsoft points to its separate Copilot Studio.⁠Source 53

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: Microsoft Agent 365 - Service Descriptions | Microsoft Learn Microsoft · checked Back:abcdefghij

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

  3. Source 3: Agent 365 identity | Microsoft Learn Microsoft · checked Back:abcdefghijklm

  4. Source 4: Ecosystem partner agents available in Agent 365 | Microsoft Learn Microsoft · checked Back:abcdef

  5. Source 5: Choose an Agent 365 Integration Option | Microsoft Learn Microsoft · checked Back:abcdefghij

  6. Source 6: What is Microsoft Foundry? - Microsoft Foundry | Microsoft Learn Microsoft · checked Back:abcd

  7. Source 7: Blocks homepage Blocks.ai · checked Back to text

  8. Source 8: Network requirements Blocks.ai · checked Back:abcdefghij

  9. Source 9: Solutions: Partner networks Blocks.ai · checked Back:abcdef

  10. Source 10: Pricing Blocks.ai · checked Back:abcdefghijklmnop

  11. Source 11: Why Blocks? Blocks.ai · checked Back:abcdefghi

  12. Source 12: What is Blocks? Blocks.ai · checked Back:abcdefghijk

  13. Source 13: Authentication reference Blocks.ai · checked Back:abcd

  14. Source 14: Your company's private network Blocks.ai · checked Back:abcdefghijk

  15. Source 15: Joining a Blocks network Blocks.ai · checked Back:abcdefgh

  16. Source 16: Agent 365 SDK frequently asked questions | Microsoft Learn Microsoft · checked Back:abcde

  17. Source 17: Microsoft Agent 365 SDK overview | Microsoft Learn Microsoft · checked Back:abcdefgh

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

  19. Source 19: Integrate Agent Observability Using Direct OTel | Microsoft Learn Microsoft · checked Back:abcd

  20. Source 20: Agent Messaging Endpoint | Microsoft Learn Microsoft · checked Back:abcde

  21. Source 21: Single sign-on (SSO) Blocks.ai · checked Back:abc

  22. Source 22: Agent Registry convergence with Microsoft Agent 365 | Microsoft Learn Microsoft · checked Back:abc

  23. Source 23: Organizations and access Blocks.ai · checked Back:abcdefghij

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

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

  26. Source 26: Agent2Agent (A2A) authentication - Microsoft Foundry | Microsoft Learn Microsoft · checked Back:ab

  27. Source 27: Licensing Documents Microsoft · checked Back:abcdefghi

  28. Source 28: Microsoft Agent 365 overview | Microsoft Learn Microsoft · checked Back:abc

  29. Source 29: Enable incoming A2A on a Foundry agent - Microsoft Foundry | Microsoft Learn Microsoft · checked Back to text

  30. Source 30: Build an Agent 365 agent deployed in Amazon Web Services (AWS) | Microsoft Learn Microsoft · checked Back to text

  31. Source 31: Key concepts Blocks.ai · checked Back:abcde

  32. Source 32: Solutions: Agent sprawl Blocks.ai · checked Back:abcd

  33. Source 33: Connect your agent Blocks.ai · checked Back:ab

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

  35. Source 35: Connected platforms in Microsoft Agent 365 | Microsoft Learn Microsoft · checked Back to text

  36. Source 36: Security and compliance Blocks.ai · checked Back:abcdefghij

  37. Source 37: Audit log Blocks.ai · checked Back:abcde

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

  39. Source 39: Security Blocks.ai · checked Back:ab

  40. Source 40: Release notes: June 2026 Blocks.ai · checked Back to text

  41. Source 41: Release notes: July 2026 Blocks.ai · checked Back to text

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

  43. Source 43: Admin Console Blocks.ai · checked Back to text

  44. Source 44: Release notes: August 2026 Blocks.ai · checked Back to text

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

  46. Source 46: Policy templates | Microsoft Learn Microsoft · checked Back:ab

  47. Source 47: Use agents in your app Blocks.ai · checked Back:ab

  48. Source 48: Errors Blocks.ai · checked Back to text

  49. Source 49: Use Blocks agents via MCP Blocks.ai · checked Back:ab

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

  51. Source 51: Set up your private network Blocks.ai · checked Back:ab

  52. Source 52: Quickstart Blocks.ai · checked Back to text

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

  54. Source 54: Connect LangChain to Blocks Blocks.ai · checked Back:ab

  55. Source 55: Connect CrewAI to Blocks Blocks.ai · checked Back to text

  56. Source 56: Connect LlamaIndex to Blocks Blocks.ai · checked Back to text

  57. Source 57: Connect Microsoft Agent Framework to Blocks Blocks.ai · checked Back:ab

  58. Source 58: Connect n8n to Blocks Blocks.ai · checked Back to text

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

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

  61. Source 61: Blocks Network Architecture whitepaper Blocks.ai · checked Back:ab

Tell us about your agents. We’ll show you the network.

One of our executives will set up time with you.

Talk to Us