AGENTIC MEMORY

Skills

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

← Back to Skills

azure-deploy

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

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-deploy 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 · 33

references/recipes/azd/post-deployment.md

Post-Deployment Steps

Execute critical post-deployment configuration after infrastructure provisioning completes.

⚠️ Run AFTER azd up or azd provision completes successfully

When to Apply

Post-deployment steps are required when your deployment includes:

| Scenario | Required Actions | |----------|-----------------| | ASP.NET Core + Azure SQL + Managed Identity | Grant managed identity SQL access, apply EF migrations | | App Service + Azure SQL + Entra auth | Grant App Service identity database permissions | | Container Apps + SQL Database | Configure managed identity access, run migrations |

ASP.NET Core + EF Core + Azure SQL

Complete workflow for apps using Entity Framework with Azure SQL Database.

Prerequisites

  • azd up or azd provision completed successfully
  • App Service or Container App has system-assigned managed identity enabled
  • Azure SQL Server configured with Entra ID admin
  • EF Core project with migrations

Step 1: Grant Managed Identity SQL Access

Grant the App Service or Container App's managed identity permissions on the SQL database.

See SQL Managed Identity Access for detailed SQL scripts and examples.

Quick Template:

# Get the app identity name from azd
eval $(azd env get-values)
APP_NAME=$SERVICE_API_NAME  # or SERVICE_WEB_NAME

# Connect as Entra admin and grant permissions
# See sql-managed-identity.md for connection patterns

PowerShell:

# Get the app identity name from azd
azd env get-values | ForEach-Object {
    $name, $value = $_.Split('=', 2)
    Set-Item "env:$name" $value
}
$AppName = $env:SERVICE_API_NAME  # or SERVICE_WEB_NAME

# Connect as Entra admin and grant permissions
# See sql-managed-identity.md for connection patterns

Step 2: Apply EF Core Migrations

Apply Entity Framework migrations to create database schema.

See EF Core Migrations for deployment patterns and troubleshooting.

Quick Options:

| Method | Command | Use When | |--------|---------|----------| | azd hook | Add postprovision hook in azure.yaml | Automated deployments | | Manual | dotnet ef database update | One-time or troubleshooting | | SQL Script | dotnet ef migrations script --idempotent | Pre-generated scripts |

Step 3: Verify Deployment

# Get app endpoint
ENDPOINT=$(azd env get-values | grep SERVICE_.*_URI | cut -d'=' -f2)

# Health check
curl -f "$ENDPOINT/health" || echo "Health check failed"

# Test database connectivity
curl -f "$ENDPOINT/api/test-db" || echo "Database connection failed"

PowerShell:

# Get app endpoint
$Endpoint = azd env get-values | Select-String -Pattern 'SERVICE_.*_URI' |
    Select-Object -First 1 | ForEach-Object { ($_ -split '=', 2)[1] }

# Health check
try { Invoke-WebRequest "$Endpoint/health" } catch { Write-Output "Health check failed" }

# Test database connectivity
try { Invoke-WebRequest "$Endpoint/api/test-db" } catch { Write-Output "Database connection failed" }

Expected Result:

  • HTTP 200 from health endpoint
  • No SQL authentication errors in logs
  • Application starts successfully

Common Issues

| Error | Cause | Solution | |-------|-------|----------| | Login failed for user '<token-identified principal>' | Managed identity not granted SQL access | Follow sql-managed-identity.md | | Cannot open database | Firewall rules block access | Check SQL firewall, ensure "Allow Azure services" enabled | | Invalid object name | Migrations not applied | Run EF migrations per ef-migrations.md | | No such table | Schema missing | Apply migrations or check connection string database name |

Best Practices

  1. Automate with azd hooks — Add postprovision hook to azure.yaml for repeatable deployments
  2. Use idempotent scripts — Generate SQL with dotnet ef migrations script --idempotent
  3. Verify incrementally — Test SQL access, then migrations, then endpoint
  4. Log everything — Enable verbose logging during initial setup for troubleshooting

References