AGENTIC MEMORY

Skills

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

← Back to Skills

azure-enterprise-infra-planner

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.

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.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-enterprise-infra-planner 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 · 41

references/phases/4-generate-plan.md

Phase 4: Generate Plan

Build <project-root>/.azure/infrastructure-plan.json using the schema in schema.md. Set meta.status to draft.

Use the user requirements and the research gathered from previous phases to assist:

  • Phase 1: insights from <project-root>/.azure/insights.json (existing environment, user-selected focus areas).
  • Phase 2: clarified requirements, derived sub-goals (inputs.subGoals), and WAF summaries covering missing resources, property hardening, and architecture patterns.
  • Phase 3: refined resource list, including ARM types, naming rules, and pairing constraints.

Important: Write the plan to file progressively using inline edits - never hold the full plan in a single tool-call output.

Gate

  • The plan is fully written to file.