Setting the file. One moment.
Skill 47 · Azure Deployment Preflight
Subchapter 47.2
references/REPORT-TEMPLATE.mdMarkdown7 KBView on GitHub
Use this template structure when generating preflight-report.md in the project root.
# Azure Deployment Preflight Report
**Generated:** {timestamp}
**Status:** {overall-status}
---
## Summary
| Property | Value |
|----------|-------|
| **Template File(s)** | {bicep-files} |
| **Parameter File(s)** | {param-files-or-none} |
| **Project Type** | {azd-project | standalone-bicep} |
| **Deployment Scope** | {resourceGroup | subscription | managementGroup | tenant} |
| **Target** | {resource-group-name | subscription-name | mg-id} |
| Status | Meaning | Visual |
|---|---|---|
| Pass | All checks succeeded, safe to deploy | ✅ |
| Pass with Warnings | Checks succeeded but review warnings | ⚠️ |
| Fail | One or more checks failed | ❌ |
| Status | Meaning |
|---|---|
| ✅ Pass | Check completed successfully |
| ❌ Fail | Check found errors |
| ⚠️ Warnings | Check passed with warnings |
| ⏭️ Skipped | Check was skipped (tool unavailable, etc.) |
# Azure Deployment Preflight Report
**Generated:** 2026-01-16T14:32:00Z
**Status:** ⚠️ Pass with Warnings
---
## Summary
| Property | Value |
|----------|-------|
| **Template File(s)** | `infra/main.bicep` |
| **Parameter File(s)** | `infra/main.bicepparam` |
| **Project Type** | azd project |
| **Deployment Scope** | subscription |
| **Target** | my-subscription |
| **Validation Level** | Provider |
### Validation Results
| Check | Status | Details |
|-------|--------|---------|
| Bicep Syntax | ✅ Pass | No errors found |
| What-If Analysis | ⚠️ Warnings | 1 resource ignored due to nested template limits |
| Permission Check | ✅ Pass | Full deployment permissions verified |
---
## Tools Executed
### Commands Run
| Step | Command | Exit Code | Duration |
|------|---------|-----------|----------|
| 1 | `bicep build infra/main.bicep --stdout` | 0 | 1.2s |
| 2 | `azd provision --preview --environment dev` | 0 | 8.4s |
### Tool Versions
| Tool | Version |
|------|---------|
| Azure CLI | 2.76.0 |
| Bicep CLI | 0.25.3 |
| Azure Developer CLI | 1.9.0 |
---
## Issues
### Warnings
#### ⚠️ Nested Template Limit Reached
- **Severity:** Warning
- **Source:** what-if
- **Message:** 1 resource was ignored because nested template expansion limits were reached
- **Recommendation:** Review the ignored resource manually after deployment
---
## What-If Results
### Change Summary
| Change Type | Count |
|-------------|-------|
| 🆕 Create | 3 |
| 📝 Modify | 1 |
| 🗑️ Delete | 0 |
| ✓ No Change | 2 |
| ⚠️ Ignore | 1 |
### Resources to Create
| Resource Type | Resource Name |
|---------------|---------------|
| Microsoft.Resources/resourceGroups | rg-myapp-dev |
| Microsoft.Storage/storageAccounts | stmyappdev |
| Microsoft.Web/sites | app-myapp-dev |
### Resources to Modify
#### Microsoft.KeyVault/vaults/kv-myapp-dev
| Property | Current Value | New Value |
|----------|---------------|-----------|
| properties.sku.name | standard | premium |
| tags.environment | staging | dev |
### Resources to Delete
*No resources will be deleted.*
---
## Recommendations
1. Review the storage account name `stmyappdev` to ensure it meets naming requirements
2. Confirm the Key Vault SKU upgrade from standard to premium is intentional
3. The ignored nested template resource should be verified after deployment
---
## Next Steps
The preflight validation passed with warnings. Review the warnings above, then proceed:
```bash
azd provision --environment dev
```
---
*Report generated by Azure Deployment Preflight Skill*