Skip to content

Montage for Microsoft Foundry Agents

Microsoft Foundry Agent Service consumes remote MCP endpoints through a managed agent runtime.

Integrations

How do I verify Montage workspace access with Microsoft Foundry Agents?

Microsoft Foundry Agent Service consumes remote MCP endpoints through a managed agent runtime. This differs from a local Agent Framework Python client: the hosted runtime must reach Montage and use its own configured remote authorization. The current documentation separates tool definitions, project connections, approval responses, and endpoint reachability. Begin with one narrowly permitted status tool rather than treating a model deployment as permission to use a private workspace.

01 / CONFIGUREOne remote endpointUse this client's documented HTTP setup
02 / AUTHORIZEYour workspace accessUse a supported sign-in or credential flow
03 / VERIFYRun signals_statusCheck a real workspace response
Microsoft Foundry Agents · read-only verification prompt
Using Microsoft Foundry Agents, call only Montage signals_status as the first live operation. Report the actual workspace identity and coverage from the tool response. If authentication, transport, or the tool is unavailable, stop and explain the blocker. Do not start collection, recurring tracking, writes, publishing, messaging, or social actions.
01 / Integrations

Identify the managed agent context

Use the Foundry project and agent type covered by the current MCP guide. Confirm that the selected model supports the intended tools and that the application's project identity is understood. Do not copy local stdio setup into the managed runtime; the service accepts remote MCP endpoints rather than launching arbitrary local commands on your computer.

02 / Integrations

Define a unique remote server label

Configure the documented MCP tool with a stable server_label and server_url pointing to https://app.montages.co/mcp. Keep labels unique per agent. Review endpoint reachability before changing credentials: a blocked network path and a rejected Montage grant require different fixes. Do not deploy a proxy merely to hide an unresolved compatibility problem.

03 / Integrations

Separate project and Montage authentication

Follow Foundry's MCP authentication documentation for the selected server connection. Use only an existing approved credential or compatible OAuth configuration; an Azure project token does not automatically authorize Montage. If consent cannot be represented securely by the managed connection, stop and use an interactive client. This guide creates no project credential or permission expansion.

04 / Integrations

Allow only status during testing

Use allowed_tools with the exact published signals_status name and preserve approval requirements. An approval response must correspond to the real tool request in the same conversation, not a generic blanket approval. A discovered schema demonstrates availability, while execution authorization remains a separate server decision tied to the Montage workspace.

05 / Integrations

Validate the managed tool receipt

Make the initial live Montage call signals_status and inspect the tool output rather than only the agent's final text. Confirm workspace identity and preserve any Unauthorized or Forbidden response. Do not turn on background mode or relax approval to repair an authentication failure. Successful verification grants no automatic collection, recurring tracking, or social actions.

Keep the boundaries clear.

  • Managed Foundry MCP runtime and local Agent Framework are distinct; remote endpoint reachability and remote authorization are separate prerequisites.
  • Documented setup, not live interoperability certification. A visible tool catalog is not workspace authorization.
  • First live operation: read-only signals_status. No automatic collection, recurring tracking, or social actions; broader actions need separate explicit authorization.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage