Error: Cannot retrieve the dynamic parameters for the cmdlet. Error parsing undefined value

[sweprs]

I'm trying to deploy a bicep deployment with two policy assigments
New-AzSubscriptionDeployment -Name policydeployment -TemplateFile .\main.bicep -TemplateParameterFile .\azsub1.bicepparam

I get this error:
New-AzDeployment: Cannot retrieve the dynamic parameters for the cmdlet. Error parsing undefined value. Path '', line 1, position 1.

Here is the structure

[johnlokerse]

@sweprs What version of Bicep is installed?

[sweprs]

0.20.4

[anthony-c-martin]

@sweprs would you mind also sharing the version of the Az PowerShell modules you're using, and if possible, the .bicep file you are trying to deploy?

[sweprs]

Upgraded to latest Bicep version v0.21.1
Az module version is: 9.6

Attaching bicep files
az-landingzone-configuration.zip

[johnlokerse]

@sweprs I tried to run your main.bicep on my environment including the deployment command and I got the same 'dynamic parameters' error including that I was missing Bicep-cli. I normally do local deployments with Azure CLI and not via Azure PowerShell. After installing Bicep-cli the 'dynamic parameters' was fixed and it deployed the infrastructure.

Maybe something went corrupt during the upgrade? Did you try to reinstall it?

[sweprs]

Hmm.. strange. Yes, tried to reinstall it.
Tried with Azure CLI instead at it worked. I have older AZ modules so I will try to update those and see if that resolves the Powershell issue.

[mtessier84]

I have the same issue, did you find the root cause?

[sweprs]

Not yet but it works when using Azure CLI. Updated the AZ modules and dow I get some more info in the error:
New-AzDeployment: Cannot retrieve the dynamic parameters for the cmdlet. C:\Users\XXXXXXX\GIT\az-landingzone-configuration\azsub1.bicepparam(1,1) : Error BCP336: Using a Bicep Parameters file requires enabling EXPERIMENTAL feature "ParamsFiles". [https://aka.ms/bicep/config]

But since I'm using the lastest bicep extension i don't get why it is says EXPERIMENTAL.

I have a case with Microsoft and we will see what happens.

[anthony-c-martin]

@sweprs it sounds like you must have an older version of Bicep installed - the "ParamsFiles" experimental feature was removed a while back.

Azure CLI installs Bicep to ~/.azure/bin/bicep, whereas Azure PowerShell uses whichever bicep binary you have on your system's PATH. See the instructions here for Azure PowerShell.

[marsontret]

What does your bicep config file look like?

[MilesCameron-DMs]

I had a similar issue - the version of the Az module you were using didn't support using the Bicep parameters file or at least it wasnt listed on the docs for that version.

I see you updated - i updated to 10.4.1 of the Az module and that fixed the issue for me after restarting my shell.

[simon-windeler]

I've got the same issue but on az module 10.4.1, new install too of VS code. Putting the values in the main bicep file works ok but not when using the bicep param file! Works fine on my current set up but on a new set up for a customer to test it's failing! Have I missed something?

[MilesCameron-DMs]

I have another discussion open about the bicepparam file:

#11984

[MilesCameron-DMs]

As per #11983 (comment)

I moved to Az PowerShell version 10.3.0 and that also works.

10.4.1 has a bug so i would avoid that as per @anthony-c-martin note in issue #11983

[simon-windeler]

Thanks, will give it a try.

[itccbe]

Hi everyone, I'm having this issue on a Microsoft hosted DevOps agent.
AZ CLI BICEP: 0.23.1
PowerShell BICEP: 0.23.1
Get-Module -Name Az -ListAvailable: 9.3.0

It works with command az deployment group create, but not with New-AzResourceGroupDeployment.

Error: Cannot retrieve the dynamic parameters for the cmdlet. Error parsing
| undefined value. Path '', line 1, position 1.

Switching back to parameters.json file instead of *.bicepparam also works.

What is needed on the self-hosted agents, image: ubuntu-latest

[anthony-c-martin]

Get-Module -Name Az -ListAvailable: 9.3.0

I think this is the problem - .bicepparam support was first added in 9.7.1. Could you try upgrading the version of Az you have installed?

[itccbe]

The self-hosted agents (windows-latests and ubuntu-latest) comes with 9.3.0.
Which is not possible to upgrade: "WARNING: User declined to install module (Az)."

Locally on my laptop I have v8.3.0 and it is working:

Get-Module -Name Az -ListAvailable

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     8.3.0                 Az                                  Core,Desk
Script     8.0.0                 Az                                  Core,Desk
Script     7.0.0                 Az                                  Core,Desk