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/recipes/common/dotnet-entry-point.md

C# (.NET) Entry Point (DO NOT MODIFY)

The base Azure Functions template includes a properly configured Program.cs that should NOT be modified or replaced by recipes.

⛔ CRITICAL: Do NOT replace or modify Program.cs from the base template.

Base Template Program.cs

The official functions-quickstart-dotnet-azd template uses:

using Microsoft.Azure.Functions.Worker;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;

var host = new HostBuilder()
    .ConfigureFunctionsWebApplication()  // ASP.NET Core integration
    .ConfigureServices(services =>
    {
        services.AddApplicationInsightsTelemetryWorkerService();
        services.ConfigureFunctionsApplicationInsights();
    })
    .Build();

host.Run();

Why This Matters

| Feature | ConfigureFunctionsWebApplication | ConfigureFunctionsWorkerDefaults | |---------|----------------------------------|----------------------------------| | ASP.NET Core integration | ✅ Yes | ❌ No | | IActionResult return types | ✅ Yes | ❌ No | | [FromBody] model binding | ✅ Yes | ❌ No | | App Insights integration | ✅ Built-in | ❌ Manual setup | | Modern HTTP handling | ✅ Yes | ⚠️ Limited |

What Recipes Should Provide

Recipes only need to add:

  1. Trigger function files (.cs files with [Function] attributes)
  2. Package references (.csproj additions for extensions)
  3. App settings (connection strings, configuration)

All triggers use attribute-based binding — no Program.cs modifications needed:

  • [HttpTrigger], [TimerTrigger], [CosmosDBTrigger]
  • [ServiceBusTrigger], [EventHubTrigger], [BlobTrigger]
  • [DurableClient], [SqlTrigger]

Common Mistake

❌ WRONG — Recipe overwrites Program.cs with outdated version:

var host = new HostBuilder()
    .ConfigureFunctionsWorkerDefaults()  // OLD PATTERN
    .Build();

✅ CORRECT — Recipe leaves Program.cs untouched, only adds function files.