Blocks.ai publishes this comparison and sells in this market. Every claim about another product links to a public source.
Cloudflare MCP server portals vs Microsoft Agent 365
Cloudflare MCP server portals
Cloudflare One feature that puts MCP servers behind one governed endpoint
Microsoft Agent 365
Microsoft 365 control plane to discover, manage, govern, and secure AI agents
Short answer
Cloudflare says its MCP server portals, part of Cloudflare One, put MCP servers behind one governed endpoint; Microsoft Agent 365 is a Microsoft 365 control plane for AI agents.Source 1, Source 2, Source 3, Source 4 Portals govern the MCP servers and tools reached through them; Agent 365 keeps an agent registry, uses Entra agent identities, and is licensed per user.Source 2, Source 3, Source 5, Source 6, Source 7
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
Cloudflare MCP server portals
- Build agents: Not publicly documented
- Host and run agents: Not publicly documented
- Agents across organizations: Not publicly documented
Microsoft Agent 365
- Agents across organizations: Not publicly documented
At a glance
What each one is
Cloudflare MCP server portals
Cloudflare says MCP server portals are part of Cloudflare One, its SASE platform.Source 1 A portal centralizes multiple MCP servers on one HTTP endpoint and proxies each tool call.Source 2 Cloudflare Access policies decide who can connect to it, and Access logs each tool request.Source 2
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 4 Admins can work across its agent registry in the Microsoft 365 admin center, Microsoft Entra for agent identity, and Microsoft Purview.Source 6, Source 16
The differences that matter
What gets registered
Cloudflare MCP server portalsMCP servers and their tools: admins add servers to Access and choose which tools and prompt templates each portal exposes.Source 2
Microsoft Agent 365Agents: the registry lists Microsoft and non-Microsoft agents, and agent identities live in Microsoft Entra Agent ID.Source 6, Source 13
Agent 365 can also control which tools agents can access tenant-wide, and registering your own MCP servers with it is in preview.Source 4, Source 12
How agents are identified
Cloudflare MCP server portalsThrough the user’s identity provider login in Cloudflare Access; autonomous agents can use an Access service token instead.Source 2, Source 8
Microsoft Agent 365Each agent identity is a Microsoft Entra service principal, managed with Conditional Access, permission grants, consent, and lifecycle operations.Source 6
Service token sessions can’t use per-user OAuth with upstream servers; the portal uses the admin credential for every upstream request they make.Source 2
Where policy is enforced
Cloudflare MCP server portalsAt the portal, which attaches credentials and proxies each tool call; Access policies decide who can connect to it.Source 2
Microsoft Agent 365Through Microsoft 365 and Entra controls: organization-wide blocks, policy templates, and Conditional Access on agent identities.Source 6, Source 17, Source 18
Portals can reach MCP servers on a private network through Cloudflare Tunnel, with Gateway routing on.Source 2, Source 19 Agent 365’s bring-your-own MCP servers, in preview, need a publicly accessible endpoint.Source 12
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.
| Cloudflare MCP server portals | Microsoft Agent 365 | |
|---|---|---|
| What it is | ||
| What it is and who it’s for | Cloudflare says portals are part of Cloudflare One, its SASE platform.Source 1 A portal puts multiple MCP servers behind one HTTP endpoint, governed through Access.Source 2, Source 3 | A Microsoft 365 service that provides a centralized control plane to discover, manage, govern, and secure AI agents, for IT and security leaders.Source 4, Source 24 |
| Maturity | GA since 24 September 2026, after an open beta announced 26 August 2025.Source 14, Source 15 Previously called Agents Gateway in some contexts.Source 2 | Generally available since 1 May 2026 for the Commercial segment.Source 16 Registry sync and multi-tenant management are in preview.Source 25, Source 26 |
| Control | ||
| Agent registry and discovery | Admins add third-party and internal MCP servers to Cloudflare Access, up to 80 per portal.Source 2, Source 3 A registry of agents is not publicly documented. | Agent registry in the Microsoft 365 admin center: one inventory of Microsoft and non-Microsoft agents, including agents without an Entra agent identity.Source 5, Source 13 |
| Identity and access control | Sign-in through Access with an identity provider, or an Access service token for agents.Source 2, Source 8 Policies can match emails, groups, country, and device posture.Source 2 | Agent identities live in Microsoft Entra Agent ID, managed with Conditional Access, permission grants, and consent.Source 6 The inventory also lists agents without one.Source 13 |
| Ownership, policy, and revocation | Admins pick each portal’s tools and prompt templates; turned-off tools can’t be called through it.Source 2 Only users an Allow policy matches see a server in a portal.Source 2 | A required sponsor per Entra agent identity, organization-wide block, 30-day soft delete, and new owners for shared Agent Builder and Copilot Studio agents.Source 6, Source 17 |
| Audit log and observability | Access logs each tool request, viewable per portal or per server.Source 2 Logpush exports, on Enterprise plans only, record the user’s email and tool called.Source 2, Source 27 | Purview audit logs and eDiscovery of agent activities need E7 or Agent 365; not in GCC.Source 4 Observability data appears in Defender and Purview, kept 30 days.Source 9, Source 10 |
| Connection | ||
| How agents connect | MCP clients connect to the portal’s HTTPS URL, and it proxies each tool call.Source 2 Private servers join via Cloudflare Tunnel, with Gateway routing on.Source 2, Source 19 | The SDK works with agents on Azure, AWS, Google Cloud, or on premises.Source 10 Notifications, in preview, need a messaging endpoint URL that Agent 365 sends to.Source 21 |
| Agents across organizations | Cloudflare One can use several identity providers at once, for partners or contractors.Source 28 Federating other organizations’ agents is not publicly documented. | Partners’ published agents can join a tenant.Source 6, Source 29 Agents in Microsoft’s separate Foundry and Copilot Studio can call A2A agents; Foundry’s can take A2A calls.Source 30, Source 31, Source 32 |
| Protocol support | Stateless MCP 2026-07-28 and earlier 2025 Streamable HTTP clients and servers; upstream over Streamable HTTP or SSE.Source 2 A2A support: not publicly documented. | Tenant-wide tool control; your own MCP servers in preview.Source 4, Source 12 A2A is documented for Microsoft’s separate Foundry and Copilot Studio, not Agent 365.Source 30, Source 31 |
| Frameworks, models, and clouds supported | Works with MCP clients that support remote servers.Source 2 Stdio-only servers can’t be added, and some servers reject proxy-based clients like portals.Source 2 | Microsoft and third-party agents.Source 4 SDK docs name frameworks such as LangChain, CrewAI, and the OpenAI Agents SDK, and agents keep their own host.Source 11, Source 25 |
| Operations | ||
| Deployment options and data residency | A portal’s hostname is a proxied CNAME record pointing to gateway.agents.cloudflare.com.Source 2 Self-hosting a portal is not publicly documented. | Honors the EU Data Boundary; the observability service stores customer content in the tenant’s default geography.Source 9 Self-hosting it is not publicly documented. |
| Compliance attestations | Company-wide, Super Administrators can get PCI, SOC 2, ISO, and other documents in the dashboard.Source 23 Portal-specific scope is not publicly documented. | Microsoft says Agent 365 meets all FedRAMP High controls its assessor reviewed, with authorization pending (announced).Source 4 Not yet a Core Online Service.Source 9 |
| Support and SLA | Support options vary by Zero Trust plan; professional services are Contract add-ons.Source 33 Cloudflare advertises SLAs for paid Zero Trust plans with 100% uptime.Source 33 | No specific SLA for the Frontier preview program.Source 34 An SLA or support plan specific to the generally available service is not publicly documented. |
| Time and effort to get running | Needs a domain on Cloudflare and an identity provider in Zero Trust.Source 2 Then add MCP servers, create a portal with tools and policies, and connect clients.Source 2 | Enterprise customers need Microsoft 365 E5, or E3 with Defender Suite and Purview Suite, and at least one user with an Agent 365 license.Source 7, Source 16 |
| Pricing model and public prices | Cloudflare says MCP server portals are available to all Cloudflare customers.Source 14 A separate price for portals is not publicly documented. | Per user, not per agent: lists at $15 a month standalone, or in Microsoft 365 E7.Source 7 Microsoft Cloud subscribers get foundational capabilities at no extra cost.Source 7 |
| Building | ||
| Agent building tools | Separately from portals, Cloudflare’s Agents docs cover building and hosting agents on Cloudflare, and remote MCP servers can be built on Workers.Source 3, Source 35 | Microsoft says the Agent 365 SDK isn’t an agent-building framework.Source 10 For low-code building, the docs point to Microsoft’s separate Copilot Studio.Source 36 |
| Model access | Not publicly documented for portals. Cloudflare says its separate AI Gateway manages model traffic across AI providers.Source 37 | Microsoft says the SDK doesn’t call or select models; the agent keeps making its own model calls.Source 10, Source 11 |
| Integrations and ecosystem | Portals can be managed with Terraform.Source 2 On Enterprise plans, Logpush can send logs to storage or SIEM tools.Source 2 An MCP server marketplace: not publicly documented. | Microsoft says it launched with partner agents and agents built on partner agent factories.Source 29, Source 38 Work IQ MCP tools for Mail, Teams, and more are in preview.Source 39 |
Which to choose
Choose Cloudflare MCP server portals if
- You use Cloudflare One, which Cloudflare says includes portals, and want many MCP servers behind one endpoint for clients like Claude Desktop.Source 1, Source 2
- You want Access policies on portal use, matching emails, groups, country, and device posture, plus per-portal control of which tools appear.Source 2
- Your MCP servers sit on a private network: portals reach them through Cloudflare Tunnel or another connector, with Gateway routing on.Source 2, Source 19
- You want each tool request logged, viewable per portal or per server, and exportable to a SIEM on Enterprise plans.Source 2
Choose Microsoft Agent 365 if
- You build agents in Microsoft’s separate Copilot Studio or Foundry, which Microsoft says can provide built-in Agent 365 integration for some scenarios.Source 25, Source 40
- You want one registry of your Microsoft and non-Microsoft agents, with a required sponsor for each Entra agent identity.Source 6, Source 13
- You want agent identities in Entra, managed with the same Conditional Access, consent, and lifecycle controls as the rest of your tenant.Source 6
- You want activity from supported agents to show up in Defender, Purview, and the Microsoft 365 admin center.Source 9, Source 10
Questions buyers ask
Does either one keep a registry of agents?
Do they support MCP and A2A?
Portals support MCP, including stateless MCP 2026-07-28; A2A support is not publicly documented.Source 2 Agent 365 can control tool access tenant-wide, including Microsoft MCP servers; registering your own is in preview.Source 4, Source 12 A2A is documented for Microsoft’s separate Foundry and Copilot Studio, not Agent 365 itself.Source 30, Source 31
Which identity providers do they work with?
Portals sign users in through Cloudflare Access; Cloudflare One supports all SAML and OIDC providers and most OAuth providers, several at once.Source 2, Source 28 Agent 365 agent identities live in Entra; agents can authenticate users with Entra ID, which can federate to another provider.Source 6, Source 41
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
46 public sources, each with the date we checked it. Every one opens in a new tab.
Source 1: Securing the AI Revolution: Introducing Cloudflare MCP Server Portals Back:abcd
Source 2: MCP server portals · Cloudflare One docs Back:abcdefghijklmnopqrstuvwxyz27282930313233343536373839404142434445464748495051
Source 3: MCP governance · Cloudflare Agents docs Back:abcde
Source 4: Microsoft Agent 365 - Service Descriptions | Microsoft Learn Back:abcdefghijklmn
Source 5: Agent Registry in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back:abcdef
Source 6: Agent 365 identity | Microsoft Learn Back:abcdefghijklmnop
Source 8: Service token support for MCP server portals · Changelog Back:abcde
Source 9: Data handling, data residency, and compliance in Agent 365 observability | Microsoft Learn Back:abcdefg
Source 10: Agent 365 SDK frequently asked questions | Microsoft Learn Back:abcdefgh
Source 11: Microsoft Agent 365 SDK overview | Microsoft Learn Back:abcd
Source 12: Bring your own (BYO) MCP server in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back:abcde
Source 13: Agent Registry convergence with Microsoft Agent 365 | Microsoft Learn Back:abcdefgh
Source 14: MCP server portals are now generally available · Changelog Back:abcde
Source 16: Microsoft Agent 365 overview | Microsoft Learn Back:abcd
Source 17: Governance and Lifecycle actions for agents available in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back:abc
Source 19: Private MCP server support for MCP server portals · Changelog Back:abc
Source 20: Cloudflare Tunnel · Cloudflare One docs Back to text
Source 21: Agent Messaging Endpoint | Microsoft Learn Back:ab
Source 22: Service tokens · Cloudflare One docs Back to text
Source 23: Compliance documentation · Cloudflare Fundamentals docs Back:ab
Source 24: Microsoft Agent 365: The Control Plane for Agents Back to text
Source 25: Choose an Agent 365 Integration Option | Microsoft Learn Back:abc
Source 26: Manage agents across multiple tenants in the Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back to text
Source 27: MCP Portal Logs · Cloudflare Logs docs Back to text
Source 29: Ecosystem partner agents available in Agent 365 | Microsoft Learn Back:ab
Source 30: Connect to an agent over the Agent2Agent (A2A) protocol - Microsoft Copilot Studio | Microsoft Learn Back:abc
Source 31: Connect to an A2A agent endpoint from Foundry Agent Service - Microsoft Foundry | Microsoft Learn Back:abc
Source 32: Enable incoming A2A on a Foundry agent - Microsoft Foundry | Microsoft Learn Back to text
Source 33: Cloudflare Access | Zero Trust Network Access (ZTNA) Back:ab
Source 34: Preview Agent 365 features through the Frontier program | Microsoft Learn Back to text
Source 35: Build Agents on Cloudflare · Cloudflare Agents docs Back to text
Source 36: Get started with Microsoft Agent 365 | Microsoft Learn Back to text
Source 38: Microsoft Agent 365, now generally available, expands capabilities and integrations | Microsoft Security Blog Back to text
Source 39: Connect existing agents to Microsoft Agent 365 | Microsoft Learn Back to text
Source 40: What is Microsoft Foundry? - Microsoft Foundry | Microsoft Learn Back to text
Source 41: Integrate Microsoft Entra Agent ID with third-party identity providers | Microsoft Learn Back to text