Template error creating Secondary node in Active-Active

[Infiniteez]

Hi,

The deployment of the Active-Active scenario fails with the following error. The error occurs with both existing VNET and new VNET.

Unable to process template language expressions for resource '/subscriptions/REDACTED/resourceGroups/REDACTED/providers/Microsoft.Resources/deployments/OPNsense-Secondary' at line '812' and column '5'. 'The language expression property '0' can't be evaluated, property name must be a string.' (Code: InvalidTemplate)

[dmauser]

Hi @Infiniteez, thanks for reporting this!

Root cause: In bicep/main.bicep the load-balancer and OPNsense-Secondary module output references were wrapped in any(...). That cast strips Bicep's static type info, so the compiler emitted runtime expressions like reference(...).outputs.backendAddressPools[0].id instead of the correct ...outputs.backendAddressPools.value[0].id. ARM then complained that property 0 can't be evaluated on the outputs object — exactly the error you hit at line 812 (the OPNsense-Secondary deployment block).

Fix: Removed any() from the affected output accesses in bicep/main.bicep and added the missing .value accessor in the compiled ARM/main.json (7 sites: backendAddressPools[0], inboundNatRules[0/1], frontendIP.privateIPAddress, and trustedNicIP).

Verified with:

• az bicep build — clean compile, matches the hand-edited ARM.
• az deployment group validate with scenarioOption=Active-Active → Succeeded.
• az deployment group what-if → Succeeded; Primary + Secondary VMs, both LBs, NSG, NICs, and CustomScript extensions all resolve and are planned for creation.

Could you please pull the latest main and re-run your Active-Active deployment (both new and existing-VNET paths) to confirm it works in your environment? Closing once you confirm.