Azure Infra Cost Estimator

4. Feature flags from deployment settings where relevant:

• DEPLOY_AZURE_CONTAINER_REGISTRY
• DEPLOY_AZURE_OPENAI
• DEPLOY_AZURE_SERVICE_BUS
• DEPLOY_AZURE_COSMOSDB
• DEPLOY_OBSERVABILITY_TOOLS

5. AKS sizing assumptions if set (for example AKS_NODE_POOL_VM_SIZE, node count).

Procedure

1. Identify provisioned resources from azure.yaml, infra/bicep/, and infra/terraform/ plus enabled feature flags.
2. Build a bill-of-materials list grouped as:

• Core: AKS, networking, Key Vault, baseline logs/monitoring.
• Optional: ACR, OpenAI, Service Bus, Cosmos DB, full observability stack.

3. For each resource group item, map to Azure Pricing Calculator service entries.
4. Use region-specific calculator pricing where possible. If exact SKU is unknown, choose a conservative default and label it as an assumption.
5. Compute monthly estimate per line item using:

• Unit price x quantity x usage hours/units.

6. Produce a markdown table with columns:

• Resource
• SKU/Assumption
• Quantity
• Estimated Monthly Cost
• Notes

7. Provide totals:

• Core subtotal
• Optional features subtotal
• Grand total per environment
• Grand total across environment count

8. Add confidence and risk notes:

• Unknown SKU fields
• Throughput-sensitive services (Cosmos DB RU/s, OpenAI token usage)
• Region variance warning

Decision Points

• If region is missing: default to eastus2 and mark estimate as provisional.
• If feature flags are unknown: provide three scenarios:
• Minimal baseline
• Standard demo
• Full feature set
• If usage is unknown: assume 730 hours/month for always-on and also show a workshop-only variant.
• If calculator value is unavailable for a specific SKU: use nearest supported SKU and flag as approximation.

Output Requirements

Always return:

1. A short assumptions section.
2. A markdown cost table.
3. A totals section.
4. A brief "what can change this estimate" section.

Quality Checks Before Finalizing

• Every estimated line item includes an explicit assumption or exact SKU.
• Table includes all enabled optional services.
• Total math is internally consistent.
• Region and environment count are explicitly stated.
• Unknowns and approximation risk are clearly called out.

Output Template

Use this template when responding:

## Azure Cost Estimate

### Assumptions

- Region: <region>
- Environments: <n>
- Monthly usage: <hours/units>
- Enabled options: <list>

| Resource            | SKU/Assumption | Quantity | Estimated Monthly Cost | Notes  |
| ------------------- | -------------- | -------: | ---------------------: | ------ |
| AKS control + nodes | <sku>          |    <qty> |               $<value> | <note> |
| ...                 | ...            |      ... |                    ... | ...    |

### Totals

- Core subtotal: $<value>/month
- Optional subtotal: $<value>/month
- Total per environment: $<value>/month
- Total for <n> environments: $<value>/month

### What Can Change This Estimate

- <item>
- <item>