Validation and operations | Session 07: Azure API Center and the AI/MCP inventory

Chapter 6 of 6

Confirm the result#

Run the read-only inventory check:

PowerShell

.\scripts\check-inventory.ps1 `
  -ApprovedSubscriptionId $approvedSubscriptionId `
  -RemoteMcpServerTitle $remoteMcpServerTitle

Bash

./scripts/check-inventory.sh --approved-subscription-id "$approved_subscription_id" --remote-mcp-server-title "$remote_mcp_server_title"

The direct agent API, synchronized APIM gateway API, and MCP server must each appear once with the required metadata. The APIM integration must resolve to the approved source. The script checks provisioning and source health when the service response exposes them and writes no inventory export. The owner checks omitted source health, the native MCP deployment location, and MCP runtime health in the portal. This is an inventory check, not end-to-end runtime validation.

After implementation#

What remains	Owner
API Center service, inventory scope, and metadata schema	API program owner
Ownership, consumers, lifecycle, review, and expiry metadata	Business and technical owners
Classification, residency, risk, and evaluation destination	Data and risk owners
APIM integration and reader assignment	APIM owner
OpenAPI definitions and managed analysis findings	API developers

Run this control in the approved nonproduction inventory. Keep the direct agent definition and deployment files in source control. Maintain synchronized and native MCP metadata in API Center.

To remove the inventory, the API program owner first confirms that no later session or approved consumer relies on it. Through the approved Azure change path, check the live implementationSession=07-api-center-ai-mcp-inventory tag, remove the exact APIM reader assignment, and delete only the marked API Center. Its child inventory resources are deleted with it. The APIM instance, Foundry agent, remote MCP runtime, runtime policies, and repository definitions remain.