跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

azure-apim-architecture

Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.

Thomas Thornton · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add thomast1906/github-copilot-agent-skills --skill azure-apim-architecture

技能说明


name: azure-apim-architecture description: Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway. license: MIT metadata: author: Thomas Thornton version: "1.0.0" last-updated: "2026-05-19" azure-services: "api-management, front-door, vnet, private-link, api-center"

Azure APIM Architecture Skill

Provides comprehensive guidance on Azure API Management architecture patterns for enterprise API marketplaces, including component selection, network topology, cost optimization, and design decision rationale.

When to Use This Skill

Activate this skill when users ask questions related to:

  • Component selection: "Should I use Azure Front Door or Application Gateway?"
  • Network architecture: "VNet Internal mode vs External mode?"
  • Multi-environment strategy: "Separate APIM instances or workspaces for dev/test/prod?"
  • Cost optimization: "How much will this cost in UK South?"
  • Authentication patterns: "OAuth vs subscription keys for public APIs?"
  • Design rationale: "Why did you choose X instead of Y?"

Core Knowledge

1. Azure Front Door Premium (Not Application Gateway)

Decision: Use Azure Front Door Premium as ingress layer

Rationale:

  • Built-in DDoS protection: Platform-level, included at no extra cost (saves £2,644/month vs separate Azure DDoS Standard)
  • Private Link support: Secure backend connectivity to APIM VNet Internal mode without public internet exposure
  • Global capabilities: Multi-POP network, future-proof for geographic expansion
  • WAF included: Managed OWASP rulesets for application security
  • Better for APIs: Optimized for HTTP/HTTPS routing, lower latency than App Gateway

Cost: £378/month (UK South) vs Application Gateway WAF v2 ~£350/month (similar cost, AFD offers more features)

Microsoft Docs: Azure Front Door Overview

Alternatives Rejected:

  • Application Gateway: No global capabilities, requires separate DDoS (£2,644/mo), less optimized for API workloads
  • Direct APIM exposure: Not secure, no DDoS protection layer

2. VNet Internal Mode (Not External)

Decision: Deploy all APIM instances in VNet Internal mode

Rationale:

  • Maximum security: No public IP exposure, gateway endpoints accessible only within VNet via internal load balancer
  • Zero-trust architecture: All external access via Front Door → Private Link → APIM internal endpoint (Azure backbone, no internet)
  • Simplified attack surface: Only Front Door is internet-facing (single point of defense)
  • Compliance: Meets data residency and security requirements (no data leaving Azure network)
  • Internal API security: Private APIs accessible only within VNet without separate APIM instance

Microsoft Guidance:

"Use the internal VNet mode when you want to expose your API Management instance only to clients within the VNet. This mode provides maximum security by ensuring the gateway and management endpoints are accessible only via private IPs." - APIM VNet Modes

Network Flow:

Internet User → Azure Front Door (WAF, DDoS)
    ↓ Private Link (Azure backbone, no internet)
APIM Internal Endpoint (10.1.1.4, no public IP)
    ↓ VNet connectivity
Backend APIs (within VNet or peered VNets)

Key Implications:

  • Gateway endpoint: 10.1.1.4 (internal IP only, not registered in public DNS)
  • Developer portal: Accessed via VNet or Front Door with Private Link
  • Management endpoint: Requires VPN/Bastion or Azure portal (no public access)
  • Private DNS zones: azure-api.net resolves to internal IP within VNet
  • Warning: Complexity: Requires proper VNet configuration, Private DNS setup, Private Link approval

External Mode Rejected:

  • Gateway has public IP (even if restricted by NSGs)
  • Larger attack surface
  • Cannot enforce 100% private traffic flow

Microsoft Docs: APIM VNet Integration


3. Separate APIM Instances per Environment (Not Workspaces)

Decision: Use 3 separate APIM instances for dev/test/prod, not workspaces within a single instance

Rationale:

  • Cost optimization: Developer tier for dev/test (£45/month) vs Premium shared cost (£648/workspace if conceptually split)
  • Blast radius isolation: Dev changes cannot impact production (separate compute, configuration, secrets, networking)
  • Independent scaling: Scale prod (3 units zone-redundant) separately from dev (1 unit)
  • Environment-specific configuration: Different backends, rate limits, policies, secrets per environment without risk of cross-contamination
  • Deployment safety: Test promotes confidence before prod (true replica environments, not logical separation)
  • Compliance: Some frameworks require physical separation of production from non-production

Microsoft Guidance:

"Workspaces provide logical isolation within a single API Management instance for organizing APIs, products, and subscriptions by team or project. They're ideal for multi-tenant scenarios within the same environment, but don't provide compute or infrastructure isolation." - APIM Workspaces

Cost Comparison:

ApproachDevTestProdTotal
Separate Instances (recommended)£45£45£1,944£2,034/mo
Workspaces in Single Premium£648*£648*
阅读完整来源 ↗