1# Bicep Recipe
2 
3Standalone Bicep workflow (without AZD).
4 
5## When to Use
6 
7- IaC-first approach
8- No CLI wrapper needed
9- Direct ARM deployment control
10- Existing Bicep modules to reuse
11- Custom deployment orchestration
12 
13## Before Generation
14 
15**REQUIRED: Research best practices before generating any files.**
16 
17| Artifact | Research Action |
18|----------|-----------------|
19| Bicep files | Call `mcp_bicep_get_bicep_best_practices` |
20| Bicep modules | Call `mcp_bicep_list_avm_metadata` and follow [AVM module order](../azd/iac-rules.md#avm-module-selection-order-mandatory) |
21| Resource schemas | Use `activate_azure_resource_schema_tools` if needed |
22 
23## Generation Steps
24 
25### 1. Generate Infrastructure
26 
27Create Bicep templates in `./infra/`.
28 
29→ [patterns.md](patterns.md)
30 
31**Structure:**
32```
33infra/
34├── main.bicep
35├── main.parameters.json
36└── modules/
37    ├── container-app.bicep
38    ├── storage.bicep
39    └── ...
40```
41 
42### 2. Generate Dockerfiles (if containerized)
43 
44Manual Dockerfile creation required.
45 
46## Output Checklist
47 
48| Artifact | Path |
49|----------|------|
50| Main Bicep | `./infra/main.bicep` |
51| Parameters | `./infra/main.parameters.json` |
52| Modules | `./infra/modules/*.bicep` |
53| Dockerfiles | `src/<service>/Dockerfile` |
54 
55## References
56 
57- [Bicep Patterns](patterns.md)
58 
59## Next
60 
61→ Update `.azure/deployment-plan.md` → **azure-validate**
62