AZD Validation

Validation steps for Azure Developer CLI projects.

Prerequisites

• azure.yaml exists in project root
• Infrastructure files exist:
  • For Bicep: ./infra/ contains Bicep files
  • For Terraform: ./infra/ contains .tf files and azure.yaml has infra.provider: terraform

Validation Steps

• [ ] 1. AZD Installation
• [ ] 2. Schema Validation
• [ ] 3. Environment Setup
• [ ] 4. Authentication Check
• [ ] 5. Subscription/Location Check
• [ ] 6. Aspire Pre-Provisioning Checks
• [ ] 7. Provision Preview
• [ ] 8. Build Verification
• [ ] 9. Docker Build Context Validation
• [ ] 10. Package Validation
• [ ] 11. Azure Policy Validation
• [ ] 12. Aspire Post-Provisioning Checks

Validation Details

1. AZD Installation

Verify AZD is installed:

azd version

If not installed:

mcp_azure_mcp_extension_cli_install(cli-type: "azd")

2. Schema Validation

Validate azure.yaml against official schema:

mcp_azure_mcp_azd(command: "validate_azure_yaml", parameters: \{ path: "./azure.yaml" \})

3. Environment Setup

Verify AZD environment exists and is configured. See Environment Setup for detailed steps.

4. Authentication Check

azd auth login --check-status

If not logged in:

azd auth login

5. Subscription/Location Check

Check environment values:

azd env get-values

If AZURE_SUBSCRIPTION_ID or AZURE_LOCATION not set:

Use Azure MCP tools to list subscriptions:

mcp_azure_mcp_subscription_list

Use Azure MCP tools to list resource groups (check for conflicts):

mcp_azure_mcp_group_list