What can AI agents do with Microsoft Foundry through Ferentin?

Ferentin exposes 38 Microsoft Foundry MCP tools to your AI agents, grouped as Discover (4 tools), Access (17 tools) and Manage (15 tools). Every call is checked against your Ferentin policies before it reaches Microsoft Foundry.

How does Ferentin secure Microsoft Foundry access?

Requests through the Microsoft Foundry integration are covered by entra ID OAuth, on behalf of, azure rbac and no API keys. These controls are applied by Ferentin, not by Microsoft Foundry, so they hold across every connected agent.

What permissions does the Microsoft Foundry integration require?

The Microsoft Foundry integration requests 1 OAuth 2.0 scope: https://ai.azure.com/.default

How do I connect Microsoft Foundry to Ferentin?

Open the Ferentin admin console, add Microsoft Foundry as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.

Is the Microsoft Foundry integration generally available?

The Microsoft Foundry integration is currently beta on Ferentin.

MCP Servers

Microsoft Foundry

Beta

Manage Microsoft Foundry AI resources — agents, evaluations, model catalog/deployments, and connections — via Entra ID.

MCP ServersMicrosoftAzureAI Platform

Configure Setup guide

How it works

Every agent request passes through Ferentin policy before it reaches Microsoft Foundry.

AI agentAsks for something
Ferentin policies
- Entra ID OAuth
- On behalf of
- Azure rbac
- No API keys
Microsoft Foundry MCP serverAuthorized connection
Governed resultMasked, logged, returned

What you can do with Microsoft Foundry

Discover
Search and browse what exists, without opening the content itself.
4 tools
Access
Read content and metadata, subject to masking policy.
17 tools
Manage
Create, update, organise and remove items.
15 tools

Technical capabilities38 tools

Discover

model_catalog_list
model_quota_list
project_connection_list
project_connection_list_metadata

Access

agent_get
agent_container_status_get
agent_definition_schema_get
evaluation_dataset_get
evaluation_dataset_versions_get
evaluation_get
evaluation_comparison_get
evaluator_catalog_get
model_details_get
model_deployment_get
model_benchmark_get
model_benchmark_subset_get
model_similar_models_get
model_switch_recommendations_get
model_monitoring_metrics_get
model_deprecation_info_get
project_connection_get

Manage

agent_update
agent_invoke
agent_delete
evaluation_dataset_create
evaluation_agent_batch_eval_create
evaluation_dataset_batch_eval_create
evaluation_comparison_create
evaluator_catalog_create
evaluator_catalog_update
evaluator_catalog_delete
model_deploy
model_deployment_delete
project_connection_create
project_connection_update
project_connection_delete

Other

agent_container_control
prompt_optimize

Overview

Microsoft Foundry (formerly Azure AI Foundry) is Microsoft's platform for building, evaluating, and deploying AI agents and models.

Developer docs

Ferentin integration

Ferentin's Microsoft Foundry MCP server connects agents through Microsoft Entra ID (OAuth On-Behalf-Of), with 38 tools spanning agent lifecycle, evaluations and datasets, the model catalog and deployments, project connections, and prompt optimization. Operations run with the signed-in user's Azure RBAC permissions.

Connection details

Status: Beta
Integration type: Remote MCP server
Authentication: OAuth 2.0
Hosting: Vendor-hosted endpoint
Required scopes: 1
Data actions: Read and write
MCP tools: 38

Configure Setup guide

Permissions1 scope

https://ai.azure.com/.default

Security controls4

Entra ID OAuth
On behalf of
Azure rbac
No API keys

Technical details

Vendor: Microsoft Foundry
Endpoint: mcp.ai.azure.com

Public preview: no SLA; the tool set may change without notice. Not recommended for production.
Microsoft Entra does not support Dynamic Client Registration (DCR) for this server — each tenant registers its own Entra app.
Auth is OAuth On-Behalf-Of: tools execute with the signed-in user's permissions (Reader = read tools, Contributor = writes). No API keys.
The endpoint is public-only — Foundry resources behind Azure Private Link are not reachable through this server.
The OAuth scope (https://ai.azure.com/.default) and the 'organizations' authority are best-effort from current docs; verify against your Entra app registration.

Frequently asked about Microsoft Foundry

What can AI agents do with Microsoft Foundry through Ferentin?: Ferentin exposes 38 Microsoft Foundry MCP tools to your AI agents, grouped as Discover (4 tools), Access (17 tools) and Manage (15 tools). Every call is checked against your Ferentin policies before it reaches Microsoft Foundry.
How does Ferentin secure Microsoft Foundry access?: Requests through the Microsoft Foundry integration are covered by entra ID OAuth, on behalf of, azure rbac and no API keys. These controls are applied by Ferentin, not by Microsoft Foundry, so they hold across every connected agent.
What permissions does the Microsoft Foundry integration require?: The Microsoft Foundry integration requests 1 OAuth 2.0 scope: https://ai.azure.com/.default
How do I connect Microsoft Foundry to Ferentin?: Open the Ferentin admin console, add Microsoft Foundry as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
Is the Microsoft Foundry integration generally available?: The Microsoft Foundry integration is currently beta on Ferentin.

Related integrations

Microsoft Learn

Semantic search over official Microsoft/Azure docs and code samples — public and read-only.

MCP Servers

View

Google Vertex AI

Google Cloud's enterprise AI platform with managed Gemini models, fine-tuning, and MLOps capabilities.

LLM Providers

View

AWS Knowledge

Ground agents in AWS documentation, API references, best practices, and regional availability — public and read-only.

MCP Servers

View