AI ECOSYSTEM · PRIMARY SOURCES

Microsoft – Copilot & Foundry: AI agents explained

Microsoft ships agentic products across multiple enterprise stacks. Researcher and Analyst serve Microsoft 365 Copilot workflows; Security Copilot Agents target security operations. Copilot Studio, Foundry Agent Service and Agent Framework occupy separate builder and runtime layers.

ECOSYSTEM PROFILE07

linked profiles

Reviewed: 8 October 2026
Individual product facts, not a provider rating

DIRECT ANSWER

Which AI agents belong to Microsoft?

Microsoft ships agentic products across multiple enterprise stacks. Researcher and Analyst serve Microsoft 365 Copilot workflows; Security Copilot Agents target security operations. Copilot Studio, Foundry Agent Service and Agent Framework occupy separate builder and runtime layers.

This table links existing agent profiles. These are not duplicate copies and trust claims are never inherited automatically.

What product distinctions matter most?

Copilot is an umbrella brand, not one uniform agent runtime. A Security Copilot capability cannot be transferred to Microsoft 365 Copilot Researcher. Fabric Data Agent is another distinct surface.

How does AgentenCode assess these products?

Verify licenses and tenant conditions, Microsoft 365 data access, role-based permissions, auditability and the boundary between Copilot Studio and Foundry. Cloud and enterprise security properties require product-specific evidence.

Individual profiles use the existing 36-control AgentenTrust framework. A missing signal does not mean a failed control. Vendor assertions are never presented as independent security measurements.

IN-DEPTH ANALYSIS

How do the agents in this ecosystem differ?

Microsoft 365 Copilot, Copilot Studio, Foundry and Security Copilot serve distinct administrative and data boundaries. Product family association does not imply entitlement across these services.

Product identity

Keep Researcher/Analyst in the Microsoft 365 Copilot scope.

Execution context

Distinguish Copilot Studio creation/deployment from Microsoft Foundry managed agents.

Trust boundaries

Treat Security Copilot governance evidence as security-product-specific, not global Microsoft evidence.

What matters most before adoption?

Copilot is an umbrella brand, not one uniform agent runtime. A Security Copilot capability cannot be transferred to Microsoft 365 Copilot Researcher. Fabric Data Agent is another distinct surface.

Verify licenses and tenant conditions, Microsoft 365 data access, role-based permissions, auditability and the boundary between Copilot Studio and Foundry. Cloud and enterprise security properties require product-specific evidence.

What does evidence-based assessment mean here?

AgentenCode records provider links as curated product associations. Evidence for API access, data residency, logging, approvals, hosting and model selection applies only to its verified agent and scope. The number of products in one ecosystem is not a security or quality rating.

Primary sources by product

These links do not establish shared feature support or automatically transfer Trust signals.

ALL LINKED PROFILES

Microsoft – Copilot & Foundry: agents and platforms

Each entry opens the existing centrally managed source profile.

Documented product role and trust-evidence comparison
ProductTypeCategoryAgentenTrust
Microsoft Copilot ResearcherEnterprise-Research-AgentResearch9 controls with evidence
Microsoft Copilot AnalystDatenanalyse-AgentAnalyse9 controls with evidence
Microsoft Copilot StudioEnterprise Agent BuilderAutomatisierung9 controls with evidence
Microsoft Foundry Agent ServiceManaged Agent PlatformAutomatisierung5 controls with evidence
Microsoft Agent FrameworkAgenten-FrameworkAutomatisierungTrust review pending
Microsoft Fabric Data AgentData AgentService, Sales & Daten7 controls with evidence
Microsoft Security Copilot AgentsSecurity Agent PlatformSecurity & IT1 controls with evidence
Compare with another AI ecosystem ↗

FAQ

Questions about Microsoft

Are all Microsoft agents part of Copilot Studio?

No. Microsoft 365 Copilot, Security Copilot, Fabric and Foundry are separate product surfaces.

Can Researcher be compared with Claude Research?

Yes, as research agents, while plan-specific tools and access still need separate analysis.

Editorial review: 8 October 2026. Availability and plans may change; consult the publisher for definitive terms.

Products, availability and scope

Microsoft ships agentic products across multiple enterprise stacks. Researcher and Analyst serve Microsoft 365 Copilot workflows; Security Copilot Agents target security operations. Copilot Studio, Foundry Agent Service and Agent Framework occupy separate builder and runtime layers. Copilot is an umbrella brand, not one uniform agent runtime. A Security Copilot capability cannot be transferred to Microsoft 365 Copilot Researcher. Fabric Data Agent is another distinct surface.

Linked products and their distinct scopes
ProductProduct typeDocumented usesAccess caveat
Microsoft Copilot ResearcherEnterprise research agentMarket analysis; strategy researchMicrosoft 365 Copilot; access depends on license and tenant.
Microsoft Copilot AnalystData analysis agentAnalyze data; investigate trendsMicrosoft 365 Copilot; license-dependent access.
Microsoft Copilot StudioEnterprise agent builderInternal assistants; customer serviceMicrosoft Copilot Studio; commercial licensing applies.
Microsoft Foundry Agent ServiceManaged agent platformBuild enterprise agents; connect tools and dataThrough Microsoft Foundry/Azure; costs, regions and capabilities depend on the Azure offering.
Microsoft Agent FrameworkAgent development frameworkDevelop agents; orchestrate multi-agent systemsAvailable as a developer framework; infrastructure and models depend on the selected Microsoft/cloud configuration.
Microsoft Fabric Data AgentData agentBusiness intelligence questions; Lakehouse and Warehouse dataWithin Microsoft Fabric; capacity, features and regions depend on the Fabric offering.
Microsoft Security Copilot AgentsSecurity agent platformSecurity triage; threat intelligence briefingsWithin Microsoft Security Copilot and embedded Microsoft security experiences; capacity, roles and features depend on tenant settings.

Swipe the table horizontally to see all four columns.

Security and evidence due diligence

Verify licenses and tenant conditions, Microsoft 365 data access, role-based permissions, auditability and the boundary between Copilot Studio and Foundry. Cloud and enterprise security properties require product-specific evidence. A product relationship is not capability inheritance. In a purchasing decision, verify every critical control against the precise agent, region, plan, integration and execution surface. A missing claim is Unknown; it is not a negative finding.

Source and methodology: Microsoft ↗ · AgentenCode evidence method · Compare ecosystems