Scope the tool connection
Configure the remote MCP server, selected tools and authentication appropriate to the application.
- Receives
- Agent task and approved tool catalogue
- Produces
- Narrow tool capability set
Microsoft Foundry integration.
Explore governed AI assistance that connects approved knowledge, models and tools to marketing and revenue tasks.
Let’s connectAgent tools with explicit access and approval
Connect a bounded task to approved knowledge and tools, then inspect both the final answer and the actions taken to produce it.
Review proposed action
When approval is configured, inspect the tool name and arguments in the approval request before resuming the response.
- Receives
- Proposed tool call and authorization context
- Produces
- Approved or rejected action
Evaluate and observe
Record relevant traces and test task correctness, source support and access behavior before promoting a changed configuration.
- Receives
- Agent response and tool outcomes
- Produces
- Release evidence and operational review
Step 1 of 3
Inspect the data contract.
Select a field to examine its owner, permitted changes and conflict handling. Clear ownership keeps updates consistent across systems.
| Field or object | Accountable owner | Mapping and control |
|---|---|---|
| Application owner | Explicitly restricts the tools exposed to the agent. | |
| Foundry response | Links the human decision to the proposed action. | |
| Source owner | Supports verification of retrieved evidence. |
Resolve the important decisions.
Tool allowlist and authorization
An allowlist limits model capability. The tool implementation still validates the caller and every requested operation.
Approval lifecycle
Foundry MCP can emit mcp_approval_request items. The application must preserve the response context and route the decision correctly.
Validate before handover.
Select the scenarios to discuss with your implementation team.
0 of 3 selected
Test an example workflowPlatform documentation
A connection with a clear purpose.
A scoped agent with approved function, OpenAPI or MCP tools, identity controls and an evaluation process.
We begin by identifying the business process this connection supports. Source ownership, permissions and the expected update behavior are documented before data starts moving.
The data behind the workflow.
AgentsModelsToolsToolboxesEvaluationsTraces
Object and field availability depend on the platform edition, API permissions and the agreed use case. Mapping defines which system owns each value and how changes are reconciled.
Decisions worth making early.
Scope & access
Restrict tool authority, protect source access and use human review for consequential actions.
Data & behavior
Validate regional availability, chosen agent capabilities and deployment requirements before implementation.
From mapping to a maintainable connection.
Discover the workflow
Agree the trigger, source of truth, receiving system and the person accountable for exceptions.
Validate the contract
Confirm permissions, object mappings, identifiers, consent and API behavior using a representative test environment.
Test real scenarios
Exercise expected updates, duplicates, missing data, access failures and vendor rate limits.
Document and enable
Hand over field mappings, credentials ownership, monitoring guidance and recovery procedures.
The engineering detail.
Read the contracts, controls and failure behavior behind a maintainable implementation.
What could work better, together?
Tell us where your operations are today. We’ll help you see what comes next.