Azure Ecosystem

Azure is the Microsoft cloud route when tasks involve Azure resources, App Service, AKS, Storage, Entra, Application Insights, Azure AI, Foundry, AI Gateway, Kusto, or enterprise infrastructure. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27

When To Use This

Use Azure when the target runtime, identity, observability, AI service, or infrastructure is Azure-specific. Use the specialized Azure skill family rather than generic cloud advice once the product is named. Source: Skill Resolver, 2026-06-27

Decision Matrix

Core Model

Azure routing is a skill family, not a single page. Start with account/subscription/tenant confirmation, then route to the product-specific skill. Keep mutations gated by read/list and what-if/preview where available. Source: Skill Resolver, 2026-06-27

Routing Summary

Preferred order: az CLI for exact account state, Azure personal skills for procedure, product-specific skills for App Insights, AI Gateway, Kusto, Messaging, RBAC, quotas, reliability, compliance, migration, Foundry, Entra, and deployment validation. Source: Skill Resolver, 2026-06-27; config/capability-harvest-seeds.json

Failure Modes

• Running against the wrong tenant or subscription.
• Mutating resources without region/resource-group confirmation.
• Treating Entra identity, RBAC, and app auth as one thing.
• Skipping what-if/preview for deploys.

Verification Path

Run az account show before any Azure operation. For deploys, use az deployment group what-if or equivalent preview where possible, then read back the changed resource. Source: config/capability-harvest-seeds.json; Skill Resolver, 2026-06-27

---

Timeline

• 2026-06-27 | Canonical ecosystem page created to consolidate Azure CLI, skill family, Foundry, Entra, and App Insights routing. Source: User request, 2026-06-27; Ecosystem Capability Coverage