azure-indexlisted

**Canonical skill URI**: `skill://azure:azure-index` # Azure Intent Router Route the user's request to the correct skill or agent. ## Routing Rules ### F5 Customer Edge Keywords and paraphrases: "Customer Edge", "F5 CE", "XC CE", "CE site", "Secure Mesh Site", "secure mesh node", "F5 XC on Azure", "Distributed Cloud node", "Distributed Cloud appliance", "F5 cloud edge", "F5 appliance from the Azure Marketplace", "one-node CE", "three-node F5 cluster", "CE HA", "Route Server", "CE BGP", "CE bootstrap", "CE lifecycle", "CE image", and requests to deploy, resize, replace, repair, inspect, or tear down F5 Distributed Cloud in Azure. - Invoke `azure:azure-ce` for discovery, planning, mutation, lifecycle, status, diagnostics, cloud-init, or teardown. - Route ambiguous phrases combining F5 or Distributed Cloud with Azure deployment, VM, appliance, node, edge, routing, or HA to `azure:azure-ce`; do not treat them as generic VM requests. - Never route CE mutation through the generic CLI operator or legacy Azure VNet Site, Fleet, or shared-token procedures. - Existing-state, inventory, ownership, creator, and activity questions about Azure CE remain in `azure:azure-ce`. Use `az_account_show` followed by `azure_ce_inventory`; do not delegate, search the web, call `az_exec`, or invoke deployment discovery/planning/mutation. - Mutation and planning language takes precedence over inventory language. Unmatched Azure CE requests retain the deployment research gate. ### A