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/live-role-verification.md

Live Role Verification

Query Azure to confirm that provisioned RBAC role assignments are correct and sufficient for the application to function. This complements the static role check in azure-validate by validating live Azure state.

How It Differs from azure-validate's Role Check

| Check | Skill | What It Verifies | |-------|-------|-----------------| | Static | azure-validate | Generated Bicep/Terraform has correct role assignments in code | | Live | azure-deploy (this) | Provisioned Azure resources actually have the right roles assigned |

Both checks are needed because:

  • Bicep may be correct but provisioning could fail silently for roles
  • Manual changes or policy enforcement may alter role assignments
  • Previous deployments may have stale or conflicting roles

When to Run

After deployment verification (step 7). Resources are now provisioned, so live role assignments can be queried.

Verification Steps

1. Identify App Identities

Read .azure/deployment-plan.md to find all services with managed identities. Then query Azure for their principal IDs:

# App Service
az webapp identity show --name <app-name> -g <resource-group> --query principalId -o tsv

# Container App
az containerapp identity show --name <app-name> -g <resource-group> --query principalId -o tsv

# Function App
az functionapp identity show --name <app-name> -g <resource-group> --query principalId -o tsv

2. Query Live Role Assignments

Use MCP tools to list role assignments for each resource and identity (using the principalId from step 1):

azure__role(
  command: "role_assignment_list",
  scope: "<resourceId>",
  assignee_object_id: "<principalId>"
)

Or via CLI:

az role assignment list --scope <resourceId> --assignee-object-id <principalId> --output table

3. Cross-Check Against Requirements

For each identity, verify the assigned roles match what the app needs:

| App Operation | Expected Role | Scope | |---------------|---------------|-------| | Read/write blobs | Storage Blob Data Contributor | Storage account | | Generate user delegation SAS | Storage Blob Delegator | Storage account | | Read secrets | Key Vault Secrets User | Key Vault | | Send messages | Azure Service Bus Data Sender | Service Bus namespace | | Read/write documents | Cosmos DB Built-in Data Contributor | Cosmos DB account |

4. Check for Common Issues

| Issue | How to Detect | Fix | |-------|---------------|-----| | Role assigned at wrong scope | Role on resource group but needed on specific resource | Reassign at resource scope | | Generic role instead of data role | Contributor assigned but no data-plane access | Replace with data-plane role (e.g., Storage Blob Data Contributor) | | Missing role entirely | No assignment found for identity on target resource | Add role assignment to Bicep and redeploy | | Stale role from previous deployment | Old principal ID with roles, new identity without | Clean up old assignments, add new ones |

Decision Tree

Resources provisioned?
├── No → Skip live check (nothing to query yet)
└── Yes → For each app identity:
    ├── Query role assignments on target resources
    ├── Compare against expected roles from plan
    │   ├── All roles present and correct → ✅ Pass
    │   ├── Missing roles → ❌ Fail — add to Bicep, redeploy
    │   └── Wrong scope or generic roles → ⚠️ Warning — fix and redeploy
    └── Record results in deployment verification

Record in Deployment Verification

Add live role verification results to the deployment log in .azure/deployment-plan.md:

### Live Role Verification
- Command: `az role assignment list --scope <resourceId> --assignee-object-id <principalId>`
- Results:
  - <identity> → <role> on <resource> ✅
  - <identity> → missing <expected-role> on <resource> ❌
- Status: Pass / Fail