AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-prepare

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-prepare at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 164

references/services/functions/templates/selection.md

Template Selection Guide

Map user intent to MCP template resource filter.

NEVER hardcode template names — names can change. Always use functions_template_get(language) to discover available templates, then filter by resource field.

Intent → Resource Mapping

| User Says | Code Indicators (existing projects) | Resource Filter | Recipe Reference | |-----------|-------------------------------------|-----------------|------------------| | "HTTP", "REST", "API", "webhook" | HttpTrigger, @app.route, req: HttpRequest | http | — | | "timer", "schedule", "cron", "periodic" | TimerTrigger, @app.schedule, TimerInfo | timer | recipes/timer/README.md | | "Cosmos", "CosmosDB", "document DB" | CosmosDBTrigger, @app.cosmos_db, cosmos_db_input | cosmos | recipes/cosmosdb/README.md | | "Event Hub", "streaming", "events" | EventHubTrigger, @app.event_hub, event_hub_output | eventhub | recipes/eventhubs/README.md | | "Service Bus", "queue", "message" | ServiceBusTrigger, @app.service_bus_queue | servicebus | recipes/servicebus/README.md | | "blob", "file", "storage trigger" | BlobTrigger, @app.blob, blob_input, blob_output | blob | recipes/blob-eventgrid/README.md | | "SQL", "database trigger" | SqlTrigger, @app.sql, sql_input, SqlOutput | sql | recipes/sql/README.md | | "MCP", "MCP server", "tools" | McpToolTrigger, @app.mcp_tool, mcp in project | mcp | recipes/mcp/README.md | | "durable", "workflow", "orchestration" | DurableOrchestrationTrigger, orchestrator, durable_functions | durable | recipes/durable/README.md | | "AI", "agent", "chatbot", "OpenAI" | openai, AzureOpenAI, langchain, semantic_kernel | http | Scan description for "AI", "agent", "Copilot SDK" | | No specific trigger / intent unclear | — | http (default) | — |

Selection Algorithm

1. DISCOVER: functions_template_get(language) → template list
2. DETECT (existing code): Scan for code indicators above → map to resource
3. MATCH (new projects): Scan template descriptions for user intent
4. FILTER: resource == mapped_resource AND infrastructure == user_iac_choice
5. PREFER: AZD-enabled (infrastructure: "bicep" or "terraform")
6. SELECT: Template whose description best matches user intent
7. DEFAULT: If intent unclear or no trigger specified → use `http`

Output: Working Function App

MCP templates return complete, deployable projects — each array entry has { path, content }:

| Array | Contents | Action | |-------|----------|--------| | functionFiles[] | Function source code (triggers, bindings, business logic), infra and other files | Create directories from path, write content to each file | | projectFiles[] | settings.json, host.json, dependencies files | Create directories from path, write content to each file |

Write files from the array output above. NEVER hand-write Bicep/Terraform and use azd init -t <template>/func init/func new as fallback when composing multiple recipes and required templates are not found.

For deployment steps, see README.md.

Default Behavior

When user intent is ambiguous or no specific trigger is mentioned, default to HTTP:

  • User says "create a function" with no trigger → HTTP
  • User describes business logic without specifying trigger → HTTP
  • Intent cannot be determined from context → HTTP

HTTP is the safest default because it's the most common trigger type and provides a simple request/response pattern that works for most use cases.

IaC Selection

| User Says | Filter By | |-----------|-----------| | Nothing specified | infrastructure: "bicep" (default) | | "terraform", "use terraform" | infrastructure: "terraform" | | "bicep", "use bicep" | infrastructure: "bicep" |

Non-AZD Fallback

If specific trigger/binding has no AZD template:

  1. Use non-AZD template for function code only
  2. Find related AZD template as IaC reference:

| Non-AZD Resource | Related AZD Reference | |-----------------|----------------------| | RabbitMQ, Kafka | EventHub AZD | | SendGrid, Twilio, Webhook | HTTP AZD | | IoT Hub | EventHub AZD |