All skills
microsoft avatar

/azure-prepare

@b8a1c66
by microsoftmicrosoft/skills3.1k stars
351

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.

Use this Skill: https://skilld.dev/gh/microsoft/skills/azure-prepare

This session only. Nothing lands on disk.

referencesservicesfunctionstemplatesrecipescommondotnet-entry-point.md

≈501 tokens on demand. Your agent reads this file only when SKILL.md points to it.

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.

Source: SKILL.md on GitHub

2 warnings3d4 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    This skill includes security considerations related to the processing of untrusted project files and the retrieval of external development templates. While these operations are essential for modernizing and preparing Azure applications, they represent a surface area for indirect prompt injection and depend on the integrity of external template repositories.

  • Socket3d

    5 alerts: gptAnomaly, gptSecurity

  • Snyk3d

    Risk: LOW · No issues

  • Runlayer7mo

    86/87 files flagged

Signed by skilld at b8a1c66. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated last week
metadata
{
  "author": "Microsoft",
  "version": "1.3.4"
}

README badge

README badge for microsoft/skills/azure-prepare