Skip to main content
Use Azure API Management as the connection point between your Foundry workloads and Silmaril. Route model and remote MCP traffic through the gateway so checks happen before execution and before responses reach the agent.

​
Before you start

Get your Firewall endpoint, credentials and Azure connection configuration through deployment access. You will also need access to your Foundry project and the API Management instance that owns the model and tool routes.

​
Set up the connection

1

Choose the protected routes

Identify the model APIs and remote MCP servers used by your agents. Keep their authentication and routing policies together in API Management.
2

Apply your connection configuration

Use the Azure configuration supplied with your Silmaril deployment to connect the selected request and response boundaries to Firewall. Store credentials in your Azure secret store and start in observation mode.
3

Verify and enable enforcement

Send a model request and a tool call. Check their findings, then test a blocked request and response before enabling enforcement on the selected routes.

​
Model and tool boundaries

Keep the model and tool routes in your connection configuration aligned with the paths your agents use. Application-owned calls can also use a framework integration or SDK.

​
Operate the connection

Use observation mode to review findings and latency. Enable enforcement once request and response checks behave as expected. Keep the previous gateway policy revision for rollback, and verify both boundaries after a policy or model-route change. See Microsoft’s AI gateway documentation for API Management capabilities and service-tier settings.

​
Next steps

Verify your integration, then review findings and modes and enforcement.