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/error-handling.md

Error Handling Patterns

MANDATORY: All function implementations MUST include proper error handling with logging.

Python

import logging

try:
    # Your function logic here
    result = process_data(data)
    logging.info(f"Success: processed {item_id}")
except Exception as error:
    logging.error(f"Error processing {item_id}: {error}")
    raise  # Re-raise to trigger retry/dead-letter

TypeScript

try {
    // Your function logic here
    const result = await processData(data);
    context.log(`Success: processed ${itemId}`);
} catch (error) {
    context.error(`Error processing ${itemId}:`, error);
    throw error;  // Re-raise to trigger retry/dead-letter
}

JavaScript

try {
    // Your function logic here
    const result = await processData(data);
    context.log(`Success: processed ${itemId}`);
} catch (error) {
    context.error(`Error processing ${itemId}:`, error);
    throw error;  // Re-raise to trigger retry/dead-letter
}

C# (.NET)

try
{
    // Your function logic here
    var result = await ProcessDataAsync(data);
    _logger.LogInformation($"Success: processed {itemId}");
}
catch (Exception ex)
{
    _logger.LogError(ex, $"Error processing {itemId}");
    throw;  // Re-raise to trigger retry/dead-letter
}

Java

try {
    // Your function logic here
    Result result = processData(data);
    context.getLogger().info("Success: processed " + itemId);
} catch (Exception e) {
    context.getLogger().severe("Error processing " + itemId + ": " + e.getMessage());
    throw e;  // Re-raise to trigger retry/dead-letter
}

PowerShell

try {
    # Your function logic here
    $result = Process-Data -Data $data
    Write-Host "Success: processed $itemId"
}
catch {
    Write-Error "Error processing $itemId : $_"
    throw  # Re-raise to trigger retry/dead-letter
}

Key Principles

  1. Always log before throwing - Enables debugging from logs
  2. Re-throw exceptions - Allows Functions runtime to handle retry/dead-letter
  3. Include context in logs - Item ID, operation name, relevant metadata
  4. Use appropriate log levels - Info for success, Error for failures