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 connects AI agents where they already run and lets you decide who can reach each one, including other companies.Source 7, Source 8
Where each one sits
Six layers of running AI agents at a company, and what each product’s own public sources say it covers.
Blocks.ai
Microsoft Agent 365
- Agents across organizations: Not publicly documented
At a glance
What each one is
Blocks.ai
Blocks.ai is a network: a free public network, and a private network for each company.Source 11, Source 22 A company’s private network gives it one place to connect, govern, and audit its agents, whoever built them and wherever they run.Source 11 Blocks.ai does not build, host, or orchestrate agents.Source 7, Source 9
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
Agents at other companies
Blocks.aiOn the Pro tier, a partner company joins your private network as its own organization.Source 21, Source 22 You can call only the agents it shares with you.Source 12, Source 23
Microsoft Agent 365Agents 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 12, Source 23
How agents connect
Blocks.aiEvery Blocks.ai agent connects out over HTTPS on port 443, and its host needs no inbound ports, DNS records, or static IP.Source 16
Microsoft Agent 365Telemetry is exported over OpenTelemetry.Source 17 Notifications, in preview, go to an endpoint the agent registers.Source 18 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
Which agents it covers
Blocks.aiAny 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 7, Source 8, Source 9, Source 31, Source 32
Microsoft Agent 365Microsoft 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 33
Agent 365 can also sync agents from Amazon Bedrock, Google Vertex AI, and other platforms, in preview.Source 5, Source 34 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.
Full comparison
18 criteria in five groups. Every cell links to its source, or says no public source answers it.
| Blocks.ai | Microsoft Agent 365 | |
|---|---|---|
| What it is | ||
| What it is and who it’s for | A 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 11, Source 22 | A 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 33 |
| Maturity | SDK and CLI 1.0 shipped on 16 June 2026.Source 39 OIDC single sign-on, now on the Pro tier, shipped on 20 July 2026, per the release notes.Source 19, Source 40 | Generally 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 41 |
| Control | ||
| Agent registry and discovery | On your company’s private network, agents join your private registry.Source 11, Source 31 Pro-tier admins see them all.Source 11, Source 42 Others need a grant to find or call a private agent.Source 23, Source 35 | A registry in the Microsoft 365 admin center for Microsoft and non-Microsoft agents, counting those managed outside Agent 365.Source 2, Source 20 Registry sync is in preview.Source 5 |
| Identity and access control | Each agent gets its own identity.Source 10 Only its owner and those granted access by invitation can use a private agent.Source 8, Source 23, Source 35 The Pro tier supports OIDC single sign-on.Source 19 | Agent identities live in Microsoft Entra Agent ID, managed with Conditional Access and admin consent.Source 3 The inventory also lists agents without one.Source 20 |
| Ownership, policy, and revocation | Pro-tier admins with the right permission can take an agent offline.Source 23, Source 43 Revoked keys and sessions stop working within about 65 seconds.Source 35 | Admins can block an agent organization-wide; SharePoint and Foundry agents only in Copilot Chat.Source 44 Policy templates span Entra, Purview, SharePoint, and Defender.Source 45 |
| Audit log and observability | On the Pro tier, an audit log of control-plane changes with who, what, when, and a before-and-after diff.Source 36 Task activity is tracked separately.Source 36 | Supported agents’ spans show in Defender, Purview, and the admin center; Agent 365 keeps them 30 days.Source 13, Source 37 Purview’s agent audit logs need E7 or Agent 365.Source 1 |
| Connection | ||
| How agents connect | Outbound only, over HTTPS on port 443.Source 16 No inbound ports, DNS records, or static IP on the agent’s host.Source 16 | Telemetry is exported to Agent 365 over OpenTelemetry.Source 17 Notifications, in preview, go to a messaging endpoint URL the agent registers.Source 18 |
| Agents across organizations | On the Pro tier, a partner company joins your private network as its own organization.Source 21, Source 22 You can call only the agents it shares with you.Source 12, Source 23 | Partners’ 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 support | An A2A-style task API over JSON-RPC 2.0.Source 46, Source 47 On the free public network, an MCP server lets MCP clients send tasks to agents and manage them.Source 22, Source 48 | MCP, in preview: Work IQ MCP servers, and your own via the Tooling Gateway.Source 14, Source 15 Microsoft’s separate Foundry and standard-harness Copilot Studio agents support A2A.Source 24, Source 25 |
| Frameworks, models, and clouds supported | Any agent that takes a task and returns a result, built with any framework and running on your own infrastructure.Source 7, Source 9 SDKs for Node.js and Python.Source 32 | Microsoft 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 14 |
| Operations | ||
| Deployment options and data residency | Pro-tier customers each get a single-tenant private instance.Source 11 Agents stay on your infrastructure.Source 7 Enforced data residency is announced, not offered yet.Source 35 | Observability data is stored in the tenant’s default geography, and Agent 365 honors the EU Data Boundary.Source 37 Advanced Data Residency isn’t currently supported.Source 37 |
| Compliance attestations | In scope under PubNub’s SOC 2 Type II (report under NDA) and ISO/IEC 27001.Source 35, Source 38 Coverage of private instances is not publicly documented. | Not yet a Core Online Service.Source 37 Microsoft says Agent 365 meets all FedRAMP High controls its assessor reviewed; final authorization is pending (announced).Source 1 |
| Support and SLA | The Pro tier comes with a 99.999% SLA.Source 22 Security reports are acknowledged within 48 hours.Source 35 Support plans are not publicly documented. | No 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 running | Ask Blocks.ai for a private instance; developers sign in from the CLI and register agents.Source 11, Source 50 Blocks.ai says the public-network quickstart takes about 10 minutes.Source 51 | Licensing 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 prices | The public network is free.Source 22 Pro pricing is set with each customer.Source 22 | Per 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 tools | Blocks.ai doesn’t build or orchestrate agents.Source 7, Source 9 You build with your own framework and write one handler, and the CLI scaffolds, validates, and connects it.Source 8, Source 9 | The Agent 365 SDK doesn’t build, host, or run agents.Source 14 For low-code building, Microsoft points to its separate Copilot Studio.Source 52 |
| Model access | Blocks.ai doesn’t prescribe what’s inside an agent, model included.Source 8 In its LangChain guide, the model client stays in your own process.Source 53 | The Agent 365 SDK doesn’t call or select models.Source 14 Agents make their own model calls.Source 13 |
| Integrations and ecosystem | Connection guides for CrewAI, LangChain, LlamaIndex, Microsoft Agent Framework, and n8n.Source 53, Source 54, Source 55, Source 56, Source 57 | Microsoft says it launched with preintegrated partner agents and agent factories, n8n among them.Source 4, Source 58 Work IQ MCP tools, in preview, include Mail and Teams.Source 59 |
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 12, Source 21, Source 22, Source 23
- Your agents run where opening inbound ports is hard or not allowed, such as corporate networks or behind proxies.Source 7, Source 16, Source 60
- Your teams use many frameworks, models, and clouds, and you want every agent in your company’s private registry, reached by grant.Source 8, Source 9, Source 11, Source 31
- 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 13, Source 45
- 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 11, Source 16, Source 31 Each agent has an owner and starts private.Source 23, Source 50
Questions buyers ask
Can Microsoft Agent 365 manage agents that weren’t built with Microsoft tools?
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 22, Source 46, Source 48 Agent 365 supports MCP in preview.Source 14, Source 15 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?
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 7, Source 9 The Agent 365 SDK doesn’t build, host, deploy, orchestrate, or execute agents either.Source 14 For low-code building, Microsoft points to its separate Copilot Studio.Source 52
How we compare
Read the full methodEvery 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
60 public sources, each with the date we checked it. Every one opens in a new tab.
Show all 60 sourcesHide sources
Source 1: Microsoft Agent 365 - Service Descriptions | Microsoft Learn Back:abcdefghij
Source 2: Agent Registry in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back:abcd
Source 3: Agent 365 identity | Microsoft Learn Back:abcdefghijklm
Source 4: Ecosystem partner agents available in Agent 365 | Microsoft Learn Back:abcdef
Source 5: Choose an Agent 365 Integration Option | Microsoft Learn Back:abcdefghij
Source 6: What is Microsoft Foundry? - Microsoft Foundry | Microsoft Learn Back:abcd
Source 13: Agent 365 SDK frequently asked questions | Microsoft Learn Back:abcde
Source 14: Microsoft Agent 365 SDK overview | Microsoft Learn Back:abcdefgh
Source 15: Bring your own (BYO) MCP server in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back:abc
Source 17: Integrate Agent Observability Using Direct OTel | Microsoft Learn Back:abcd
Source 18: Agent Messaging Endpoint | Microsoft Learn Back:abcde
Source 20: Agent Registry convergence with Microsoft Agent 365 | Microsoft Learn Back:abc
Source 24: Connect to an agent over the Agent2Agent (A2A) protocol - Microsoft Copilot Studio | Microsoft Learn Back:abcde
Source 25: Connect to an A2A agent endpoint from Foundry Agent Service - Microsoft Foundry | Microsoft Learn Back:abcde
Source 26: Agent2Agent (A2A) authentication - Microsoft Foundry | Microsoft Learn Back:ab
Source 28: Microsoft Agent 365 overview | Microsoft Learn Back:abc
Source 29: Enable incoming A2A on a Foundry agent - Microsoft Foundry | Microsoft Learn Back to text
Source 30: Build an Agent 365 agent deployed in Amazon Web Services (AWS) | Microsoft Learn Back to text
Source 33: Microsoft Agent 365: The Control Plane for Agents Back:abc
Source 34: Connected platforms in Microsoft Agent 365 | Microsoft Learn Back to text
Source 37: Data handling, data residency, and compliance in Agent 365 observability | Microsoft Learn Back:abcdefg
Source 38: Security Back:ab
Source 41: Manage agents across multiple tenants in the Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back to text
Source 44: Governance and Lifecycle actions for agents available in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back to text
Source 49: Preview Agent 365 features through the Frontier program | Microsoft Learn Back to text
Source 52: Get started with Microsoft Agent 365 | Microsoft Learn Back:ab
Source 56: Connect Microsoft Agent Framework to Blocks Back:ab
Source 58: Microsoft Agent 365, now generally available, expands capabilities and integrations | Microsoft Security Blog Back to text
Source 59: Connect existing agents to Microsoft Agent 365 | Microsoft Learn Back to text