Azure API Center and the AI/MCP inventory

Chapter 3 of 6

Confirm these requirements:

• The approved nonproduction Foundry agent endpoint and APIM API are available. The platform and gateway owners confirm the endpoint, marked policy-assistant-responses API, and both resource scopes. (The private-networking, governed-agent, and APIM controls establish these prerequisites.)
• The deployment operator has time-bound Contributor on the exact API Center resource group and User Access Administrator on the exact APIM instance. The deployment assigns the API Center identity API Management Service Reader Role (71522526-b88f-4d52-b57f-d31fc3546d0d) at that service scope.
• The API program owner has approved Free or Standard, the current API Center region, and the full APIM source boundary. Free has no Microsoft support. Confirm current eligibility or separate cost before relying on a linked Standard-plan benefit.
• The APIM API ID policy-assistant-responses exists and carries its implementation marker.
• The remote MCP server is read-only and has an approved HTTPS Streamable HTTP endpoint.
• Named owners have completed the metadata decisions for the three selected assets and any other API that the APIM link will import.

Keep subscription IDs, endpoints, credentials, tokens, prompts, responses, telemetry, and customer data out of source control.

Implementation files#