azure-workload-generator

Generate Azure workload infrastructure code in Bicep and Terraform.

1|Updated Jan 10, 2026

Search Tags:#azure #terraform #infrastructure-as-code #workload #bicep #naming-convention #ip-addressing

Ready to run

npx skills add https://github.com/Hafizurrahman-Fatehmahomed/ai-300 --skill azure-workload-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azure-workload-generator
Source: https://github.com/Hafizurrahman-Fatehmahomed/ai-300/tree/main/azure-Infrastructure-agent/.claude/skills/azure-workload-generator
Command: npx skills add https://github.com/Hafizurrahman-Fatehmahomed/ai-300 --skill azure-workload-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill streamlines the creation of Azure spoke workload infrastructure by generating consistent, policy-compliant code in Bicep and Terraform, reducing manual configuration and misconfigurations.

Core Features & Use Cases

Generate production-ready VNet, Subnet, VM, NIC, NSG, and optional data disk in both Bicep and Terraform.
Produce ready-to-deploy IaC artifacts that follow enterprise naming conventions and IP addressing standards.
Use for new workloads, spoke networks, or rapid IaC generation when workload deployment or environment setup is required.

Quick Start

To generate a workload, run the azure-workload-generator skill and provide required inputs (customer code, workload name, environment, VNet address space, subnet, VM OS, VM size, data disk needs, tags). Then review generated files under azure-workloads/Customer/<customerCode>/.

Frequently Asked Questions about azure-workload-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate Azure spoke workload infrastructure code in both Bicep and Terraform?▼

You can generate Azure spoke workload infrastructure code by providing inputs like customer code, workload name, VNet address space, and VM size to produce ready-to-deploy Bicep and Terraform files.

Can I apply custom naming conventions and IP addressing standards when provisioning VNets and Subnets?▼

Yes, you can apply custom naming conventions and IP addressing standards when provisioning VNets and Subnets, ensuring parameterized templates calculate subnets and enforce enterprise policies automatically.

Does this infrastructure as code generator support environment tagging and optional data disks?▼

Yes, the infrastructure as code generator supports environment tagging and optional data disks by incorporating these requirements into parameterized templates for resource configurations.

What Azure resources are included in the generated Terraform and Bicep templates?▼

The generated Terraform and Bicep templates include production-ready VNets, Subnets, VMs, NICs, NSGs, and optional data disks, configured according to your specified environment parameters.

What inputs do I need to provide for rapid Azure IaC generation?▼

For rapid Azure IaC generation, you need to provide the customer code, workload name, environment, VNet address space, subnet details, VM OS, VM size, data disk needs, and tags.

Where are the generated Bicep and Terraform files saved after workload deployment setup?▼

The generated Bicep and Terraform files are saved under the azure-workloads/Customer/<customerCode>/ directory structure, organized by the customer code provided during generation.