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

Requirements Gathering

Collect project requirements through conversation before making architecture decisions.

Categories

1. Classification

| Type | Description | Implications | |------|-------------|--------------| | POC | Proof of concept | Minimal infra, cost-optimized | | Development | Internal tooling | Balanced, team-focused | | Production | Customer-facing | Full reliability, monitoring |

2. Scale

| Scale | Users | Considerations | |-------|-------|----------------| | Small | <1K | Single region, basic SKUs | | Medium | 1K-100K | Auto-scaling, multi-zone | | Large | 100K+ | Multi-region, premium SKUs |

3. Budget

| Profile | Focus | |---------|-------| | Cost-Optimized | Minimize spend, lower SKUs | | Balanced | Value for money, standard SKUs | | Performance | Maximum capability, premium SKUs |

4. Compliance

| Requirement | Impact | |-------------|--------| | Data residency | Region constraints | | Industry regulations | Security controls | | Internal policies | Approval workflows |

5. Subscription Policies

After the user confirms a subscription, query Azure Policy assignments to discover enforcement constraints before making architecture decisions.

mcp_azure_mcp_policy(command: "policy_assignment_list", subscription: "<subscriptionId>")

| Policy Constraint | Impact | |-------------------|--------| | Blocked resource types or SKUs | Exclude from architecture | | Required tags | Add to all Bicep/Terraform resources | | Allowed regions | Restrict location choices | | Network restrictions (e.g., no public endpoints) | Adjust networking and access patterns | | Storage policies (e.g., deny shared key access) | Use policy-compliant auth | | Naming conventions | Apply to resource naming |

⚠️ Warning: Skipping this step can cause deployment failures when Azure Policy denies resource creation. Checking policies here prevents wasted work in architecture and generation phases.

Record discovered policy constraints in .azure/deployment-plan.md under a Policy Constraints section so they feed into architecture decisions.

Gather via Conversation

Use ask_user tool to confirm each of these with the user:

  1. Project classification (POC/Dev/Prod)
  2. Expected scale
  3. Budget constraints
  4. Compliance requirements (including data residency preferences)
  5. Subscription and policy constraints (confirm subscription, then check policies automatically)
  6. Architecture preferences (if any)

Document in Plan

Record all requirements in .azure/deployment-plan.md immediately after gathering.