Blocks.ai publishes this comparison and sells in this market. Every claim about another product links to a public source.
Gemini Enterprise Agent Platform vs Microsoft Agent 365
Gemini Enterprise Agent Platform
Google Cloud platform to build, deploy, govern, and optimize AI agents
Microsoft Agent 365
Microsoft 365 control plane to discover, manage, govern, and secure AI agents
Short answer
Gemini Enterprise Agent Platform is Google Cloud’s platform to build, deploy, and govern agents, while Microsoft Agent 365 is a Microsoft 365 control plane for agents built and run elsewhere.Source 1, Source 2, Source 3, Source 4 Agent Platform’s registry is per project and its runtime is billed by use; Agent 365 has an organization-wide registry and is licensed per user.Source 5, Source 6, 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.
These aren’t the same kind of product
Gemini Enterprise Agent Platform
Microsoft Agent 365
- Agents across organizations: Not publicly documented
At a glance
What each one is
Gemini Enterprise Agent Platform
Gemini Enterprise Agent Platform is Google Cloud’s platform to build, deploy, and govern agents, described as an evolution of Vertex AI.Source 1 Agent Registry catalogs agents; Agent Identity can give agents on supported runtimes an identity; and Agent Gateway applies policy checks to agent traffic.Source 9, Source 10, Source 11
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 It is administered across several Microsoft products: the agent registry in the Microsoft 365 admin center, Microsoft Entra, and Microsoft Purview.Source 21
The differences that matter
Building and running agents
How far each registry reaches
Where policy is enforced
Gemini Enterprise Agent PlatformBy default, Agent Gateway blocks an agent’s outbound connections without an IAM policy grant; Model Armor filters can scan prompts and tool responses.Source 11
Microsoft Agent 365Agent 365 uses Microsoft 365 and Entra controls: Conditional Access and permission grants on agent identities, policy templates, and an organization-wide block.Source 12, Source 26, Source 27
Google says Agent Gateway’s IAM access policies aren’t available for inbound calls; Microsoft says blocking a SharePoint or Microsoft Foundry agent only affects its availability in Microsoft Copilot Chat.Source 11, Source 27
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.
| Gemini Enterprise Agent Platform | Microsoft Agent 365 | |
|---|---|---|
| What it is | ||
| What it is and who it’s for | Google Cloud platform to build, deploy, govern, and optimize AI agents, described as an evolution of Vertex AI, for developers and technical teams.Source 1, Source 34 | Microsoft 365 service that provides a centralized control plane to discover, manage, govern, and secure AI agents, for IT and security leaders.Source 2, Source 25 |
| Maturity | Launched 22 April 2026.Source 35 Agent Registry and Agent Gateway generally available since 18 June 2026.Source 20 Agent Identity is generally available; its API is in preview.Source 20 | Generally available since 1 May 2026 for the Commercial segment.Source 21 Registry sync and multi-tenant management are in preview.Source 36, Source 37 |
| Control | ||
| Agent registry and discovery | Agent Registry catalogs agents, MCP servers, and tools in a Google Cloud project.Source 5, Source 9 Agents on supported Google Cloud runtimes can be registered automatically.Source 23 | Agent registry in the Microsoft 365 admin center: one inventory of Microsoft and non-Microsoft agents, including agents without an Entra agent identity.Source 7, Source 18 |
| Identity and access control | Agents on supported runtimes can have SPIFFE-based Agent Identity.Source 10 Policies link it to approved tools; other outbound gateway calls are blocked by default.Source 11 | Agent identities live in Microsoft Entra Agent ID, managed with Conditional Access, permission grants, and consent.Source 12 The inventory also lists agents without one.Source 18 |
| Ownership, policy, and revocation | Allow and deny access policies (deny overrides allow), enforce and dry-run modes, and Model Armor filters.Source 11, Source 29 An agent owner field is not publicly documented. | A required sponsor per agent identity, organization-wide block, 30-day soft delete, and owner reassignment for Agent Builder and Copilot Studio agents.Source 12, Source 27 |
| Audit log and observability | Registry admin changes get Admin Activity audit logs; other calls need Data Access logs turned on.Source 30, Source 31 Gateway traffic goes to Cloud Logging.Source 11 | Supported agents’ spans show in Defender, Purview, and the admin center; Agent 365 keeps them 30 days.Source 3, Source 13 Purview’s agent audit logs need E7 or Agent 365.Source 2 |
| Connection | ||
| How agents connect | Agent Gateway can govern calls into and out of Agent Runtime, and out of the Gemini Enterprise app.Source 11 Outside agents can be registered by URL or agent card.Source 15 | The SDK works with agents on Azure, AWS, Google Cloud, or on premises.Source 3 Notifications, in preview, need a messaging endpoint URL that Agent 365 sends to.Source 28 |
| Agents across organizations | Agent Runtime agents can call agents anywhere through Agent Gateway.Source 11 A2A agents on Agent Runtime, in preview, can accept calls from identities granted access.Source 17, Source 38, Source 39 | Partners’ published agents can be added to your tenant.Source 12, Source 40 Microsoft’s separate Foundry and standard-harness Copilot Studio agents can call external A2A agents.Source 41, Source 42 |
| Protocol support | Agent Registry catalogs MCP servers and A2A agents; Agent Gateway carries MCP and A2A traffic.Source 11, Source 24, Source 43 A2A agents on Agent Runtime and ADK’s A2A support are in preview.Source 38, Source 44 | Bring-your-own MCP servers are in preview.Source 16 A2A is documented for Microsoft’s separate Foundry and standard-harness Copilot Studio agents, not Agent 365.Source 41, Source 42 |
| Frameworks, models, and clouds supported | Agent Development Kit or any open-source framework, with Gemini or other Model Garden models.Source 14 Agents hosted outside Google Cloud can be registered manually.Source 15 | Microsoft and third-party agents.Source 2 The SDK names frameworks such as LangChain, CrewAI, and the OpenAI Agents SDK, and agents keep their own host.Source 4, Source 36 |
| Operations | ||
| Deployment options and data residency | Agent Gateway is managed and regional.Source 45 Agent data at rest stays in a supported location you pick.Source 46 Self-hosting the registry or gateway: not publicly documented. | Honors the EU Data Boundary; its observability service stores customer content in the tenant’s default geography.Source 13 Self-hosting it is not publicly documented. |
| Compliance attestations | Google lists Agent Platform in scope for ISO 27001, 27017, and 27018, SOC 1, 2, and 3, and PCI DSS, and among products the Google Cloud HIPAA BAA includes.Source 32, Source 33 | Not yet a Core Online Service.Source 13 Microsoft says Agent 365 meets all FedRAMP High controls its assessor reviewed; final authorization is pending (announced).Source 2 |
| Support and SLA | Google Cloud support packages, including 24/7 coverage.Source 47 An uptime SLA naming Agent Registry, Gateway, Identity, or Runtime is not publicly documented. | No specific SLA for the Frontier preview program.Source 48 An SLA or support plan specific to the generally available service is not publicly documented. |
| Time and effort to get running | A Google Cloud project with the Agent Registry API enabled, plus the Identity-Aware Proxy API for gateway policy.Source 5 Google recommends dry-run mode in staging.Source 29 | 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 8, Source 21 |
| Pricing model and public prices | Agent Registry is free; skill scanning is billed from January 2027.Source 19 Agent Gateway egress costs $0.085 per 15,000 requests.Source 6 | Per user, not per agent: lists at $15 per user per month standalone, or in Microsoft 365 E7.Source 8 Microsoft Cloud subscriptions get foundational capabilities free.Source 8 |
| Building | ||
| Agent building tools | Agent Studio (low-code canvas), the open-source Agent Development Kit, and Agent Garden prebuilt agents and templates.Source 1, Source 14 A Managed Agents API is in preview.Source 1 | Microsoft says the Agent 365 SDK isn’t an agent-building framework.Source 3 For low-code building, the docs point to Microsoft’s separate Copilot Studio.Source 22 |
| Model access | More than 200 models through Model Garden, including Gemini, third-party models such as Anthropic’s Claude, and open-source models.Source 1, Source 35 | Microsoft says the SDK doesn’t call or select models; the agent keeps making its own model calls.Source 3, Source 4 |
| Integrations and ecosystem | Agents in Agent Registry can be made available in Google’s Gemini Enterprise app.Source 45 Google’s own remote MCP servers are registered automatically.Source 43 | Launched with preintegrated partner agents and agents built on partner agent factories.Source 40, Source 49 Work IQ MCP tools for Mail, Calendar, Teams, and more are in preview.Source 50 |
Which to choose
Choose Gemini Enterprise Agent Platform if
- You want to build, run, and govern agents on one platform, with Agent Studio and the open-source Agent Development Kit.Source 1, Source 14
- Your agents run on Google Cloud, where agents on supported runtimes, such as Google Kubernetes Engine, can be registered automatically.Source 23, Source 24
- You want policy enforced at a gateway, with outbound connections blocked by default and Model Armor scanning prompts and tool responses.Source 11
- You want a wide choice of models: Google says Model Garden offers more than 200, including Anthropic’s Claude.Source 35
Choose Microsoft Agent 365 if
- You build agents in Microsoft’s separate Copilot Studio or Microsoft Foundry, which Microsoft says offer built-in integration for some scenarios.Source 36, Source 51
- You want agent identities in Entra, managed with the same Conditional Access, consent, and lifecycle controls as the rest of your tenant.Source 12
- Your agents run across clouds or on premises and should stay there: the Agent 365 SDK doesn’t change where they run.Source 3
- You want named accountability: each agent identity needs a sponsor, and admins can block or delete agents without owners.Source 7, Source 12
Questions buyers ask
Is Gemini Enterprise Agent Platform the same as Gemini Enterprise?
How is each one priced?
Do they support MCP and A2A?
Agent Registry and Agent Gateway handle MCP and A2A; Agent Runtime hosts A2A agents in preview.Source 11, Source 24, Source 38, Source 43 Agent 365 controls tool access tenant-wide; registering your own MCP servers is in preview.Source 2, Source 16 A2A is documented for Microsoft’s separate Foundry and standard-harness Copilot Studio agents, not Agent 365.Source 41, Source 42
Can either one connect agents across organizations?
On Agent Runtime, agents can call agents anywhere through Agent Gateway, and A2A agents, in preview, accept calls from identities granted access.Source 11, Source 17, Source 38, Source 39 Microsoft’s separate Foundry and standard-harness Copilot Studio agents can call A2A agents, and Foundry agents can accept calls from Entra identities granted access.Source 41, Source 42, Source 53
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.
Source 2: Microsoft Agent 365 - Service Descriptions | Microsoft Learn Back:abcdefghij
Source 3: Agent 365 SDK frequently asked questions | Microsoft Learn Back:abcdefghij
Source 4: Microsoft Agent 365 SDK overview | Microsoft Learn Back:abcdefg
Source 6: Gemini Enterprise Agent Platform pricing Back:abcde
Source 7: Agent Registry in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back:abcdef
Source 12: Agent 365 identity | Microsoft Learn Back:abcdefghijk
Source 13: Data handling, data residency, and compliance in Agent 365 observability | Microsoft Learn Back:abcdef
Source 14: Build with Gemini Enterprise Agent Platform Back:abcd
Source 16: Bring your own (BYO) MCP server in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back:abcd
Source 18: Agent Registry convergence with Microsoft Agent 365 | Microsoft Learn Back:abcd
Source 20: Gemini Enterprise Agent Platform release notes Back:abcd
Source 21: Microsoft Agent 365 overview | Microsoft Learn Back:abcd
Source 22: Get started with Microsoft Agent 365 | Microsoft Learn Back:ab
Source 25: Microsoft Agent 365: The Control Plane for Agents Back:ab
Source 27: Governance and Lifecycle actions for agents available in Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back:abcd
Source 28: Agent Messaging Endpoint | Microsoft Learn Back:ab
Source 32: Google Cloud Platform Services in Scope by Compliance Program Back:ab
Source 34: Gemini Enterprise Agent Platform (formerly Vertex AI) Back to text
Source 35: Introducing Gemini Enterprise Agent Platform, powering the next wave of agents Back:abc
Source 36: Choose an Agent 365 Integration Option | Microsoft Learn Back:abcd
Source 37: Manage agents across multiple tenants in the Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn Back to text
Source 40: Ecosystem partner agents available in Agent 365 | Microsoft Learn Back:ab
Source 41: Connect to an agent over the Agent2Agent (A2A) protocol - Microsoft Copilot Studio | Microsoft Learn Back:abcd
Source 42: Connect to an A2A agent endpoint from Foundry Agent Service - Microsoft Foundry | Microsoft Learn Back:abcd
Source 46: Supported locations for agents in Agent Platform Back to text
Source 48: Preview Agent 365 features through the Frontier program | Microsoft Learn Back to text
Source 49: Microsoft Agent 365, now generally available, expands capabilities and integrations | Microsoft Security Blog Back to text
Source 50: Connect existing agents to Microsoft Agent 365 | Microsoft Learn Back to text
Source 51: What is Microsoft Foundry? - Microsoft Foundry | Microsoft Learn Back to text
Source 52: Connected platforms in Microsoft Agent 365 | Microsoft Learn Back to text
Source 53: Enable incoming A2A on a Foundry agent - Microsoft Foundry | Microsoft Learn Back to text