What-if previews predicted control-plane changes before deployment. In this case, a module is copied into five projects and no longer receives a security fix. “Use deployment what-if at the correct scope” would not satisfy that requirement; the supported action is “Reference a centrally managed versioned Bicep module”. Versioned reusable modules reduce maintenance divergence between deployments.

Declarative deployment ordering must include resources referenced by dependent objects. In this case, a module is copied into five projects and no longer receives a security fix. “Declare or infer dependency on the subnet resource” would not satisfy that requirement; the supported action is “Reference a centrally managed versioned Bicep module”. Versioned reusable modules reduce maintenance divergence between deployments.

ARM dependency analysis ensures dependent resources are deployed in a safe order. In this case, a module is copied into five projects and no longer receives a security fix. “Use correct resource references and dependencies in the deployment” would not satisfy that requirement; the supported action is “Reference a centrally managed versioned Bicep module”. Versioned reusable modules reduce maintenance divergence between deployments.

Modules encapsulate resource definitions with explicit parameters and outputs. In this case, an ARM template must create a subnet after the VNet exists. “Extract a reusable Bicep module for the VNet” would not satisfy that requirement; the supported action is “Use correct resource references and dependencies in the deployment”. ARM dependency analysis ensures dependent resources are deployed in a safe order.

Resources must be declared under a valid deployment scope. In this case, an ARM template must create a subnet after the VNet exists. “Use supported subscription-scoped deployment or a module with appropriate scope” would not satisfy that requirement; the supported action is “Use correct resource references and dependencies in the deployment”. ARM dependency analysis ensures dependent resources are deployed in a safe order.

What-if previews predicted control-plane changes before deployment. In this case, an ARM template must create a subnet after the VNet exists. “Use deployment what-if at the correct scope” would not satisfy that requirement; the supported action is “Use correct resource references and dependencies in the deployment”. ARM dependency analysis ensures dependent resources are deployed in a safe order.

Bicep targetScope declares the deployment boundary for its resources. In this case, a template creates a private endpoint before its required subnet exists. “Specify the appropriate targetScope and deploy at subscription scope” would not satisfy that requirement; the supported action is “Declare or infer dependency on the subnet resource”. Declarative deployment ordering must include resources referenced by dependent objects.

Resources must be declared under a valid deployment scope. In this case, a template creates a private endpoint before its required subnet exists. “Use supported subscription-scoped deployment or a module with appropriate scope” would not satisfy that requirement; the supported action is “Declare or infer dependency on the subnet resource”. Declarative deployment ordering must include resources referenced by dependent objects.

Versioned reusable modules reduce maintenance divergence between deployments. In this case, a template creates a private endpoint before its required subnet exists. “Reference a centrally managed versioned Bicep module” would not satisfy that requirement; the supported action is “Declare or infer dependency on the subnet resource”. Declarative deployment ordering must include resources referenced by dependent objects.

Bicep module scopes allow resource-group-targeted deployments under authorized scopes. In this case, an admin needs to deploy a resource at subscription scope rather than resource-group scope. “Use scoped module deployments referencing each target resource group” would not satisfy that requirement; the supported action is “Specify the appropriate targetScope and deploy at subscription scope”. Bicep targetScope declares the deployment boundary for its resources.

Without an explicit different target, deployment often inherits the caller scope. In this case, an admin needs to deploy a resource at subscription scope rather than resource-group scope. “The module scope expression and its parameters” would not satisfy that requirement; the supported action is “Specify the appropriate targetScope and deploy at subscription scope”. Bicep targetScope declares the deployment boundary for its resources.

ARM dependency analysis ensures dependent resources are deployed in a safe order. In this case, an admin needs to deploy a resource at subscription scope rather than resource-group scope. “Use correct resource references and dependencies in the deployment” would not satisfy that requirement; the supported action is “Specify the appropriate targetScope and deploy at subscription scope”. Bicep targetScope declares the deployment boundary for its resources.

Bicep module scopes allow resource-group-targeted deployments under authorized scopes. In this case, a Bicep file targeting resource group contains a subscription-level policy assignment. “Use scoped module deployments referencing each target resource group” would not satisfy that requirement; the supported action is “Use supported subscription-scoped deployment or a module with appropriate scope”. Resources must be declared under a valid deployment scope.

Without an explicit different target, deployment often inherits the caller scope. In this case, a Bicep file targeting resource group contains a subscription-level policy assignment. “The module scope expression and its parameters” would not satisfy that requirement; the supported action is “Use supported subscription-scoped deployment or a module with appropriate scope”. Resources must be declared under a valid deployment scope.

ARM dependency analysis ensures dependent resources are deployed in a safe order. In this case, a Bicep file targeting resource group contains a subscription-level policy assignment. “Use correct resource references and dependencies in the deployment” would not satisfy that requirement; the supported action is “Use supported subscription-scoped deployment or a module with appropriate scope”. Resources must be declared under a valid deployment scope.

Resources must be declared under a valid deployment scope. In this case, an infrastructure project must deploy the same module into two resource groups. “Use supported subscription-scoped deployment or a module with appropriate scope” would not satisfy that requirement; the supported action is “Use scoped module deployments referencing each target resource group”. Bicep module scopes allow resource-group-targeted deployments under authorized scopes.

Bicep targetScope declares the deployment boundary for its resources. In this case, an infrastructure project must deploy the same module into two resource groups. “Specify the appropriate targetScope and deploy at subscription scope” would not satisfy that requirement; the supported action is “Use scoped module deployments referencing each target resource group”. Bicep module scopes allow resource-group-targeted deployments under authorized scopes.

Explicit outputs avoid brittle UI scraping and reduce ambiguity. In this case, an infrastructure project must deploy the same module into two resource groups. “Consume a declared deployment output containing the resource ID” would not satisfy that requirement; the supported action is “Use scoped module deployments referencing each target resource group”. Bicep module scopes allow resource-group-targeted deployments under authorized scopes.

Bicep targetScope declares the deployment boundary for its resources. In this case, a module unexpectedly creates all resources in the invoking group. “Specify the appropriate targetScope and deploy at subscription scope” would not satisfy that requirement; the supported action is “The module scope expression and its parameters”. Without an explicit different target, deployment often inherits the caller scope.

Resources must be declared under a valid deployment scope. In this case, a module unexpectedly creates all resources in the invoking group. “Use supported subscription-scoped deployment or a module with appropriate scope” would not satisfy that requirement; the supported action is “The module scope expression and its parameters”. Without an explicit different target, deployment often inherits the caller scope.

Explicit outputs avoid brittle UI scraping and reduce ambiguity. In this case, a module unexpectedly creates all resources in the invoking group. “Consume a declared deployment output containing the resource ID” would not satisfy that requirement; the supported action is “The module scope expression and its parameters”. Without an explicit different target, deployment often inherits the caller scope.

Decompilation translates ARM JSON into candidate Bicep requiring review. In this case, a team wants to return a storage endpoint after deployment so a pipeline can configure an app. “Run the Bicep decompile operation and review the result” would not satisfy that requirement; the supported action is “Define a Bicep output for the endpoint”. Outputs provide calculated deployment values to downstream steps.

Generated infrastructure code may require manual cleanup and compatibility checks. In this case, a team wants to return a storage endpoint after deployment so a pipeline can configure an app. “Inspect resource syntax, references and generated names before deployment” would not satisfy that requirement; the supported action is “Define a Bicep output for the endpoint”. Outputs provide calculated deployment values to downstream steps.

Without an explicit different target, deployment often inherits the caller scope. In this case, a team wants to return a storage endpoint after deployment so a pipeline can configure an app. “The module scope expression and its parameters” would not satisfy that requirement; the supported action is “Define a Bicep output for the endpoint”. Outputs provide calculated deployment values to downstream steps.

Bicep module scopes allow resource-group-targeted deployments under authorized scopes. In this case, a CI job scrapes the Azure portal to discover a newly deployed resource ID. “Use scoped module deployments referencing each target resource group” would not satisfy that requirement; the supported action is “Consume a declared deployment output containing the resource ID”. Explicit outputs avoid brittle UI scraping and reduce ambiguity.

Generated infrastructure code may require manual cleanup and compatibility checks. In this case, a CI job scrapes the Azure portal to discover a newly deployed resource ID. “Inspect resource syntax, references and generated names before deployment” would not satisfy that requirement; the supported action is “Consume a declared deployment output containing the resource ID”. Explicit outputs avoid brittle UI scraping and reduce ambiguity.

Decompilation translates ARM JSON into candidate Bicep requiring review. In this case, a CI job scrapes the Azure portal to discover a newly deployed resource ID. “Run the Bicep decompile operation and review the result” would not satisfy that requirement; the supported action is “Consume a declared deployment output containing the resource ID”. Explicit outputs avoid brittle UI scraping and reduce ambiguity.

Outputs provide calculated deployment values to downstream steps. In this case, an administrator exports an ARM JSON deployment and wants a readable starting point in Bicep. “Define a Bicep output for the endpoint” would not satisfy that requirement; the supported action is “Run the Bicep decompile operation and review the result”. Decompilation translates ARM JSON into candidate Bicep requiring review.

Allowed-value constraints reject unsupported choices early. In this case, an administrator exports an ARM JSON deployment and wants a readable starting point in Bicep. “Specify a parameter allowed-value set or Bicep @allowed constraint” would not satisfy that requirement; the supported action is “Run the Bicep decompile operation and review the result”. Decompilation translates ARM JSON into candidate Bicep requiring review.

Parameter validation can prevent invalid input from reaching resource creation. In this case, an administrator exports an ARM JSON deployment and wants a readable starting point in Bicep. “Constrain parameter values to supported SKU choices” would not satisfy that requirement; the supported action is “Run the Bicep decompile operation and review the result”. Decompilation translates ARM JSON into candidate Bicep requiring review.

Explicit outputs avoid brittle UI scraping and reduce ambiguity. In this case, an engineer assumes converted Bicep is perfect and deploys it unreviewed. “Consume a declared deployment output containing the resource ID” would not satisfy that requirement; the supported action is “Inspect resource syntax, references and generated names before deployment”. Generated infrastructure code may require manual cleanup and compatibility checks.

Outputs provide calculated deployment values to downstream steps. In this case, an engineer assumes converted Bicep is perfect and deploys it unreviewed. “Define a Bicep output for the endpoint” would not satisfy that requirement; the supported action is “Inspect resource syntax, references and generated names before deployment”. Generated infrastructure code may require manual cleanup and compatibility checks.

Parameter validation can prevent invalid input from reaching resource creation. In this case, an engineer assumes converted Bicep is perfect and deploys it unreviewed. “Constrain parameter values to supported SKU choices” would not satisfy that requirement; the supported action is “Inspect resource syntax, references and generated names before deployment”. Generated infrastructure code may require manual cleanup and compatibility checks.