Bicep deployments now require resource group location, which can break existing deployment processes

[bec-callow-oct]

Severity

Known impact to one customer with a workaround

Version

Earliest tried was 2026.3.15816

Latest Version

I could reproduce the problem in the latest build

What happened?

Resource group location was previously optional for bicep steps, so users with existing resource groups did not need to provide it. Recent changes caused this field to become mandatory, resulting in existing deployment processes becoming broken until a value was added to the field.

Reproduction

Create a simple bicep deployment without a resource group location.

Error and Stacktrace

Error    |       Octopus.Action.Azure.ResourceGroupLocation is required
Error    |       System.Exception
...
Verbose  |       Process /bin/bash ... exited with code 100
Fatal    |       The remote script failed with exit code 100

More Information

No response

Workaround

No response