# Azure Functions Health Status

> Use when investigating current Azure Functions app status and health: Running/Stopped state, Resource Health, plan status, Azure Monitor metrics, Application Insights/Log Analytics requests, failures, exceptions, traces, dependencies, and recent Activity Log. Do not use for static inventory-only requests.

- **Type:** Skill
- **Install:** `agentstack add skill-azure-azure-functions-skills-azure-functions-health-status`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Azure](https://agentstack.voostack.com/s/azure)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Azure](https://github.com/Azure)
- **Source:** https://github.com/Azure/azure-functions-skills/tree/main/templates/skills/azure-functions-health-status

## Install

```sh
agentstack add skill-azure-azure-functions-skills-azure-functions-health-status
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Azure Functions Health Status

Use this skill to investigate the current status and health of an existing Azure Function App.

Write final answers in the user's language.

## Required interaction

Ask only for missing inputs that are needed to identify the app and time window:

- Function App name (required unless already provided)
- Subscription ID or name (optional)
- Resource group (optional)
- Investigation time window, default `24h` (optional)

If subscription or resource group is unknown, discover them with Resource Graph. If multiple matching apps are found, ask the user to choose one.

## Fast path

1. Call Azure best practices for `azurefunctions` first when available.
2. Run the bundled health script for the current shell/OS:
   - `scripts/get-functionapp-health-status.ps1 -AppName `
   - `scripts/get-functionapp-health-status.sh -a ` on macOS/Linux or Bash
   - Add `-SubscriptionId ` and/or `-ResourceGroup ` when known.
   - Add `-Hours ` when the user requests a specific time window.
   - For Bash, use `-s `, `-g `, and/or `-H ` when known.
   - Bash script requires Azure CLI plus a working `python3` or `python` executable for JSON shaping.
3. If bundled script execution is unavailable, use `references/health-status-commands-and-kql.md`.
4. Report health findings and action items; avoid dumping raw logs unless requested.

If health findings require runtime or trigger-specific interpretation, use `../azure-functions-common/references/routing.md` on demand. Do not load shared language/extension references for plain status output.

## Scope boundary

This skill should collect:

- Current app state: enabled/running/stopped, metadata availability, runtime availability
- Plan status and Resource Health result
- Azure Monitor metrics: instance count, CPU, memory, execution counts/units, always-ready units
- Trigger status summary and notable disabled or indexing-failed functions
- Application Insights/Log Analytics: request counts/failures/p95, dependency failures, exceptions, warning/error traces
- Recent Activity Log events
- Gaps: missing telemetry, unsupported Resource Health, unavailable diagnostic data

Do not perform full static inventory beyond fields needed to interpret health. Use the inventory skill for detailed specifications.

## Next steps

- On success, suggest `azure-functions-diagnostics` to interpret findings and recommend fixes when health signals are degraded or unclear.
- On failure, suggest `azure-functions-inventory` to confirm app identity and configuration before retrying health checks.

## Interpretation rules

- For Flex Consumption, Resource Health may return `Unknown` or `Unsupported`; rely on app metadata, plan status, metrics, telemetry, and Activity Log.
- Workspace-based Application Insights uses `AppRequests`, `AppExceptions`, `AppTraces`, and `AppDependencies`; classic tables may be empty.
- Treat unresolved `%SETTING_NAME%` placeholders in traces/exceptions as configuration/indexing issues.
- Redact connection strings, keys, tokens, and storage secrets. It is safe to report setting names and whether values exist.

## Output template

```text
Target:  (, , )
Current status: app , metadata , plan , Resource Health 
Metrics: instances , CPU , memory , executions 
Execution: requests , failed , p95 highlights ; dependency failures 
Triggers: enabled , disabled ; indexing/config issues 
Recent changes: 
Findings: 
Recommended next actions: 
Gaps: 
```

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Azure](https://github.com/Azure)
- **Source:** [Azure/azure-functions-skills](https://github.com/Azure/azure-functions-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-azure-azure-functions-skills-azure-functions-health-status
- Seller: https://agentstack.voostack.com/s/azure
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.