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/verify.md

AZD Verification

Verify deployment success and application health.

Step 1: Verify Resources

azd show

Expected output:

Showing deployed resources:
  Resource Group: rg-myapp-dev
  Services:
    api - Endpoint: https://api-xxxx.azurecontainerapps.io

Step 2: Health Check

# Get endpoint
ENDPOINT=$(azd env get-values | grep -E "SERVICE_.*_URI|.*_ENDPOINT" | head -1 | cut -d'=' -f2)

# Test endpoint
curl -f "$ENDPOINT/health" || curl -f "$ENDPOINT"

PowerShell:

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

# Test endpoint
try { Invoke-WebRequest "$Endpoint/health" } catch { Invoke-WebRequest $Endpoint }

Expected: HTTP 200 response.

Step 3: Report Results to User

⛔ MANDATORY — You MUST present the deployed endpoint URLs to the user in your response. A deployment is not considered complete until the user has received the URLs.

⛔ ALWAYS run azd show after deployment to extract endpoint URLs. Do NOT rely on the azd deploy output alone — it is frequently truncated before endpoint URLs appear.

azd show

Parse the Endpoint: lines from the azd show output to collect all deployed service URLs.

Present a summary to the user that includes:

| Item | Source | |------|--------| | Deployed service endpoint(s) | Endpoint: lines from azd show | | Aspire Dashboard URL (if applicable) | Aspire Dashboard: line from azd show | | Azure Portal deployment link (if available) | Portal URL from provisioning output |

Example response format:

✅ Deployment succeeded!

| Service | Endpoint |
|---------|----------|
| apiservice | https://apiservice.xxx.azurecontainerapps.io |

Aspire Dashboard: https://aspire-dashboard.xxx.azurecontainerapps.io

⚠️ Always use fully-qualified URLs with the https:// scheme. If a command returns a bare hostname (e.g. myapp.azurestaticapps.net), prepend https:// before presenting it to the user.

Step 4: Post-Deployment Verification (if applicable)

For deployments with Azure SQL Database and managed identity:

Verify SQL Access

⚠️ Warning: az sql db query requires the rdbms-connect extension: az extension add --name rdbms-connect --yes

# Load environment variables
eval $(azd env get-values)

# Check managed identity user exists in database
az sql db query \
  --server "$SQL_SERVER" \
  --database "$SQL_DATABASE" \
  --resource-group "$AZURE_RESOURCE_GROUP" \
  --auth-mode ActiveDirectoryDefault \
  --queries "SELECT name, type_desc FROM sys.database_principals WHERE type = 'E'"

PowerShell:

# Load environment variables
azd env get-values | ForEach-Object {
    $name, $value = $_.Split('=', 2)
    Set-Item "env:$name" $value
}

# Check managed identity user exists in database
az sql db query `
  --server $env:SQL_SERVER `
  --database $env:SQL_DATABASE `
  --resource-group $env:AZURE_RESOURCE_GROUP `
  --auth-mode ActiveDirectoryDefault `
  --queries "SELECT name, type_desc FROM sys.database_principals WHERE type = 'E'"

Expected: Should list the App Service or Container App managed identity.

Verify Database Schema

For EF Core applications:

# Check tables exist
az sql db query \
  --server "$SQL_SERVER" \
  --database "$SQL_DATABASE" \
  --resource-group "$AZURE_RESOURCE_GROUP" \
  --auth-mode ActiveDirectoryDefault \
  --queries "SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE='BASE TABLE'"

PowerShell:

az sql db query `
  --server $env:SQL_SERVER `
  --database $env:SQL_DATABASE `
  --resource-group $env:AZURE_RESOURCE_GROUP `
  --auth-mode ActiveDirectoryDefault `
  --queries "SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE='BASE TABLE'"

Expected: Should list application tables (not just __EFMigrationsHistory).

Check Application Logs

# For App Service
az webapp log tail --name <app-name> --resource-group <resource-group>

# For Container Apps
az containerapp logs show --name <app-name> --resource-group <resource-group> --follow

Look for:

  • ✅ No SQL authentication errors
  • ✅ Successful database connection
  • ✅ Application started successfully

Common Issues

| Symptom | Cause | Fix | |---------|-------|-----| | HTTP 500 on startup | SQL authentication failure | See sql-managed-identity.md | | "Invalid object name" errors | Migrations not applied | See ef-migrations.md | | Endpoint not accessible | Service still starting | Wait 1-2 minutes, retry | | Health check fails | Application error | Check logs with az webapp log tail |

References