30-SECOND BRIEF
What it does—and when it fits
Azure AI Gateway configures Azure API Management as a governance layer for AI models, MCP tools, and agents. It covers model backends, semantic caching, token limits and metrics, load balancing, content safety, jailbreak detection, and tool rate limiting; APIM resource deployment itself remains Azure Prepare's responsibility.
INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
.claude/skills/azure-aigateway/~/.claude/skills/azure-aigateway/Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.
npx skills add microsoft/azure-skills --skill azure-aigateway --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Govern model traffic
Configure AI backends, load balancing, token limits, semantic caching, and usage metrics.
Protect tools and agents
Apply rate limits, content-safety checks, and jailbreak defenses to MCP or agent traffic.
Test gateway behavior
Inspect APIM gateway details and verify model or OpenAPI traffic through the configured policies.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to microsoft/azure-skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- It requires Azure CLI for configuration and testing, and does not provision the APIM instance itself.
- Gateway policies add a control layer but do not replace model evaluation, application authorization, or provider-side safety.
BEST FIT
Who it is for
Platform teams governing enterprise AI traffic
Developers exposing models, MCP tools, or agents through APIM
BEFORE YOU USE IT
Risks to review before use
Misconfigured gateway policy or exposed key
Incorrect caching, routing, limits, safety rules, or subscription-key handling can leak data, weaken controls, raise cost, or block production traffic. Review policy XML, secrets, backends, and staged test results before rollout.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at microsoft/azure-skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.