Microsoft Foundry Operations and Security Guide

Problem

Microsoft Foundry workloads often get stuck on specific operational issues: hosted-agent log anomalies, Azure OpenAI quotas and rate limits, network isolation and subnet design, RBAC and guardrail setup, model routing and PTU cost, evaluation and CI/CD release. Official documentation is spread across many pages, so engineering teams repeatedly switch between troubleshooting, architecture decisions, and security compliance. This skill organizes those topics into a searchable operations reference covering troubleshooting, best practices, decision making, architecture and design patterns, limits and quotas, security, configuration, integration and coding patterns, and deployment.

How it works and boundaries

It starts by using the category index to locate the relevant section, then reads local content by line range or linked reference file. For scenarios that need current details, it calls mcp_microsoftdocs:microsoft_docs_fetch to retrieve Microsoft Learn documentation; if that MCP is unavailable, it falls back to fetch_webpage and reads the result as Markdown. The materials also note that when metadata.generated_at is older than three months, the repository should be updated; if the documentation tool is missing, it should be installed according to the guidance. The scope is best suited to teams that are planning or running Foundry agents, Foundry Models, Azure OpenAI, or Foundry IQ, and it is not intended for general cloud issues unrelated to Foundry. For Azure Government, PTU, model retirement, billing, or region availability, live quotas and official release status should still be verified.