Terminal
Terminal/Skill
Collects the settings, plan, runtime, network and trigger inventory of an Azure Function App, without health or telemetry data.
By Microsoft
Works with
npx skills add azure/azure-functions-skills --skill azure-functions-inventoryUse this skill to collect the static specifications of an existing Azure Function App.
Write final answers in the user's language.
Ask only for missing inputs that are needed to identify the app:
If subscription or resource group is unknown, discover them with Resource Graph. If multiple matching apps are found, ask the user to choose one.
azurefunctions first when available.scripts/get-functionapp-inventory.ps1 -AppName <app-name>scripts/get-functionapp-inventory.sh -a <app-name> on macOS/Linux or Bash-SubscriptionId <sub> and/or -ResourceGroup <rg> when known.-s <sub> and/or -g <resource-group> when known.python3 or python executable for JSON shaping.references/inventory-commands.md.If a caller needs runtime or trigger interpretation after inventory collection, use ../azure-functions-common/references/routing.md on demand. Do not load shared language/extension references for plain inventory output.
azure-functions-health-status to check current health and telemetry next.azure-functions-diagnostics to triage missing or blocked inventory data.This skill should collect:
Do not include metrics, Application Insights, exceptions, traces, dependencies, Activity Log, or Resource Health analysis. Use the health skill for those.
Target: <app> (<resource-group>, <subscription>, <region>)
Plan/Runtime: <plan sku>, <kind>, <runtime>, Functions <version>, memory <MB>, max <n>, alwaysReady <value>
Network/Identity: VNet <subnet>, publicAccess <value>, identity <type>
Settings: <selected setting names and presence only>
Triggers: enabled <n>, disabled <n>; trigger breakdown <summary>
Related resources: <short resource type/name summary>
Gaps: <unavailable metadata, if any>