“Redeploy with Cleanup” Button or Feature

[jaserkarim356]

Describe the feature end to end, including deployment scenario details under which the feature would occur.

Add a "Redeploy with cleanup” action to the AVD Landing Zone Accelerator (LZA) after a failed deployment.
When an operator clicks Redeploy, the accelerator should:

• discover resources created by the prior run (via deployment records/tags),
• validate the target region/availability zone context,
• safely prune conflicting resources created by the earlier run, and
• recreate them with the new parameters.

It must handle regions with no zones and transitions where the selected zone set changed between runs, avoiding today’s “stuck state” where re‑deploying is blocked by prior zone choices.

Today, re‑deployments can fail due to availability zone selection behavior—even in regions without zones.

Error Observed
<code id='' style='white-space:pre-wrap'><div><div>Deployment template language expression evaluation failed: 'Evaluation result of language expression '1' is type 'Integer', expected type is 'Array'.'. Please see <a target="_blank" class="msportalfx-ext-link" href="https://aka.ms/arm-functions">https://aka.ms/arm-functions</a> for usage details.</div></div></code></br> (Code: InvalidTemplate)

Thus forcing teams to manually clean up and start from scratch.

Why is this feature important. Describe why this would be important for your organization and others. Would this impact similar orgs in the same way?

Reliability & speed: Our factory team frequently iterates deployments with customers; failed re deploys add hours of manual cleanup and scheduling friction. This feature removes hours of manual teardown between customer working sessions. Large partner and customer teams will see the same reliability and velocity gains because re deploys are common during iterative builds.

Please provide the correlation id associated with your error or bug.

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Can you describe any alternatives that you have taken since this feature does not exist?

Manual delete and redeploy of all deployment resources. This works but is slow and error prone.

Feature Implementation

Not implemented in product. Team suspects parameter parsing/validation constraints in a .bicep module contribute to the behavior. No branch to share.