microsoft/azure-functions

Placeholder. Assess an Azure Functions project or Function App for unsupported or end-of-life runtimes, deprecated programming models, extension bundles, hosting plans, and code or configuration that should move to a supported target. Read-only. Use when the Azure Functions canvas asks for an AI assessment, or when the user asks to assess migration needs.

Use when reviewing an existing Azure Function App against Azure Functions best practices and proposing safe, approval-gated remediations for runtime, configuration, identity, security, observability, performance, scale, cost, triggers, and bindings.

Open Azure Functions: one canvas for creating, opening, editing, modernizing, reviewing, running, deploying, and monitoring function apps. Use for: open Azure Functions; open function app; create a function app project with or without AI; edit a function app; check runtimes or configuration; Deep Review; diagnose or monitor a Function App; migrate to isolated worker or Flex Consumption.

Shared Azure Functions reference material for the Azure Functions skill suite: runtime/language routing, trigger/binding extension references, official docs and repository pointers. Use only when another Azure Functions skill needs reusable language or binding context. Not intended as a standalone user-facing workflow.

Scaffold a new Azure Functions project, or add a new function/trigger to an existing project without re-initializing it

Proxy Azure Functions deployment requests to the Azure Skills prepare, validate, and deploy workflow while preserving Azure Functions-specific guidance

Use when diagnosing or resolving Azure Functions issues: deployment failures, runtime errors, trigger/binding failures, language worker issues, telemetry/log analysis, known issue research, source investigation, and remediation. Acts as a facade that routes to focused Azure Functions skills and small language/extension references.

Analyze local Azure Functions workspace code and configuration for common issues, then report prioritized findings with evidence and fixes. Use when the user asks to check, review, audit, or diagnose a local Azure Functions project before running or deploying it. This skill targets local workspaces only — use azure-functions-diagnostics for deployed Azure resources.

Turn session findings into previewed GitHub issues for the azure-functions plugin

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.

Discover the Azure Functions skill that best matches the user's goal

Build, scaffold, extend, deploy, and troubleshoot Azure Functions Hosted Skills: cloud-hosted, event-driven intelligent capabilities built with Markdown, natural-language instructions, declarative configuration, code, and tools. Use whenever the user asks for an Azure Functions Hosted Skill, medium-code intelligent capability, AI app on Azure Functions, intelligent app on Azure Functions, serverless agent, serverless agents, Azure Functions agent, scheduled agent, morning briefing, daily digest, timer agent, inbox summary, email or Teams briefing, background AI workflow, connector-triggered agent, HTTP/chat capability, MCP tool, webhook-style agent, or Azure Functions hosted agent.

Use when collecting Azure Functions app specifications/inventory only: resource identity, SKU/plan, runtime, Function App config, network, identity, selected app settings, and function/trigger inventory. Do not use for runtime health, failures, metrics, or telemetry investigation.

Verify prerequisites and set up your environment for Azure Functions development

Use only when the user explicitly asks to use or resume azure-functions-update by name. Migrate Azure Functions programming models and configuration through an approved scenario. Current scenarios: C# in-process to .NET isolated worker, Python programming model v1 to v2, Python Blob SDK type bindings, Python HTTP streaming, extension bundles v1-v3 to v4, and the Durable Functions extension v1 or v2 to a current version. Language-version and hosting-plan updates are separate handoffs. Do not select this workflow from a generic update request or a name in a question, quotation, file, or review.