Home›Agents›Microsoft Foundry Agent Service

AgentenCode evidence profileAutomation

✓ Editorially reviewedChecked: October 1, 2026

Agent profile · Automation

Microsoft Foundry Agent Service

Microsoft Foundry Agent Service is classified by AgentenCode as a managed agent platform from Microsoft. It belongs to the Automation category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

MicrosoftAutomationDevelopers & businesses

View profile ↓Check sources ↓

ECOSYSTEM ASSOCIATION

This agent profile links to a curated provider view. Security controls are not inherited across products.

Microsoft · Copilot & Foundry ↗

Automationeditorial classification

Microsoftprovider

8 primary sourcessource status

October 1, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Microsoft Foundry Agent Service

Direct answer: AgentenCode currently documents 5 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data2 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access3 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability0 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

API · Auth · Api Key

No — explicitly documented

This negative value is explicit and scoped only to inbound authentication on the agent endpoint.

Scope: agent_endpoint_inbound · verified 2026-10-01 · Primary source ↗

High confidence

API · Auth · Entra Id

Yes — documented

Microsoft Entra ID is a supported inbound authorization scheme.

Scope: agent_endpoint_inbound · verified 2026-10-01 · Primary source ↗

High confidence

API · Openai Responses

Yes — documented

Foundry agents expose a Responses protocol endpoint.

Scope: agent_endpoint · verified 2026-10-01 · Primary source ↗

High confidence

API · Rest

Yes — documented

Agent endpoint configuration is available through a REST API.

Scope: agent_management · verified 2026-10-01 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

Azure RBAC is part of Agent Service access control.

Scope: foundry_project · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Byo Vnet

Yes — documented

BYO VNet is documented.

Scope: standard_networking · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Customer Managed Storage

Yes — documented

Customer-managed data resources are supported.

Scope: standard_setup · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Managed Vnet

Yes — documented

Managed VNet isolation is supported.

Scope: standard_networking · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Managed

Yes — documented

Managed hosting is a core service property.

Scope: foundry_agent_service · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Private Network

Yes — documented

Private networking is supported.

Scope: foundry_account_and_project · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

Agent Service data residency follows the Azure resource geography.

Scope: agent_service_state · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Customer Region Selectable

Yes — documented

The customer selects the Azure region when creating the Foundry resource/endpoint, determining agent-data residency.

Scope: foundry_agent_service_resource_region · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · A2A · Client

Yes — documented

Outbound A2A is documented.

Scope: foundry_agents · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · A2A · Server

Yes — documented

Incoming A2A is documented.

Scope: prompt_agents · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Server

Yes — documented

Foundry agents can expose an MCP endpoint in preview.

Scope: agent_endpoint_preview · verified 2026-10-01 · Primary source ↗

High confidence

Security · Customer-managed keys

Yes — documented

CMK support is documented with preview caveats.

Scope: supported_non_preview_features · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · At rest

AES-256

AES-256 at-rest encryption is documented.

Scope: stored_agent_data · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Microsoft Foundry Agent Service?

Product-specific evidence for Microsoft Foundry Agent Service

This profile links 8 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Automatisierung.

Data Residency

Yes · Scope: agent_service_state · verified 2026-10-01.

Primary source ↗

Region auswählbar

Yes · Scope: foundry_agent_service_resource_region · verified 2026-10-01.

Primary source ↗

Customer-Managed Keys

Yes · Scope: supported_non_preview_features · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

AES-256 · Scope: stored_agent_data · verified 2026-10-01.

Primary source ↗

RBAC

Yes · Scope: foundry_project · verified 2026-10-01.

Primary source ↗

protocols · a2a · client

Yes · Scope: foundry_agents · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

1primary source

17field-level evidence claims

5documented trust controls

3history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Microsoft Foundry Agent Service is documented under Automation and is associated with Microsoft. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on October 1, 2026.

Trust coverage

5 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Microsoft Foundry Agent Service

Microsoft Foundry Agent Service is classified as Managed Agent Platform from Microsoft. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Enterprise-Agenten bauen

This use case is part of the stored profile for Microsoft Foundry Agent Service. The related strength is “Managed Service”. In a production evaluation, the practical boundary to verify is: Azure-Rollen und Datenzugriff nach Least-Privilege konfigurieren.

Tools und Daten anbinden

This use case is part of the stored profile for Microsoft Foundry Agent Service. The related strength is “Azure-Integration”. In a production evaluation, the practical boundary to verify is: Regionen und Datenresidenz prüfen.

Agenten bereitstellen

This use case is part of the stored profile for Microsoft Foundry Agent Service. The related strength is “Enterprise-Identität und Governance”. In a production evaluation, the practical boundary to verify is: Kosten- und Observability-Grenzen setzen.

Governance und Monitoring

This use case is part of the stored profile for Microsoft Foundry Agent Service. The related strength is “Unterstützung mehrerer Agenten- und Toolmuster”. In a production evaluation, the practical boundary to verify is: Azure-Rollen und Datenzugriff nach Least-Privilege konfigurieren.

What to verify before adoption

Azure-Rollen und Datenzugriff nach Least-Privilege konfigurieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Regionen und Datenresidenz prüfen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Kosten- und Observability-Grenzen setzen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

October 1, 2026 · Source Maintenance
October 1, 2026 · Source Maintenance
September 30, 2026 · New profile

Official sources

This profile links 8 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Microsoft Foundry Agent Service?

Microsoft Foundry Agent Service is listed by AgentenCode as an automation agent or agentic product from Microsoft.

How much trust evidence is documented for Microsoft Foundry Agent Service?

The current trust layer documents 5 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is October 1, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.