azure-prepare

Azure preparation requires gathering requirements, analyzing the workspace, selecting a deployment recipe, and planning architecture before generating any code. This structured readiness workflow mandates updating a preparation manifest after each phase to capture decisions and prevent risky deployments.

The azure.yaml manifest is referenced during Azure preparation to ensure readiness before generating infrastructure. You must complete workspace analysis, requirements gathering, and architecture planning phases first, updating a preparation manifest after each phase to govern the deployment workflow.

Yes, a mandatory preparation step is required before creating Bicep or Terraform files for Azure. You must gather requirements, scan the codebase, and plan the architecture first. This enforces manifest-driven governance to capture decisions before any provisioning occurs.

Yes, Azure preparation workflows apply to modernizing deployments, adding components, updating configurations, and creating new applications. The workflow guides you through codebase scanning and recipe selection, ensuring the preparation manifest is updated after each phase to maintain compliance.

The best way to enforce compliance checkpoints is to mandate manifest updates after every preparation phase, from requirements gathering to architecture planning. Integrating a validation step before deployment ensures all readiness criteria and configuration decisions are captured and verified.

Azure deployments fail without a preparation manifest because mandatory readiness steps were skipped, leading to misconfigurations. You must coordinate requirements gathering, workspace analysis, and recipe selection first, capturing all artifacts and decisions in the manifest before provisioning.