Alex Frankel

We cannot do this with a `param` since we won't know the value at compile time. In other words, if you were to run `bicep build` with a param argument,...

#3607 seems related to this @mblant, but it is not the same ask

Repro for triage: works: ```bicep var stringArray = [ './policies/policy_1.json' ] var policies = [for i in range(0, length(stringArray)): json(loadTextContent(stringArray[i]))] ``` doesn't work: ```bicep var stringArray = [ './policies/policy_1.json' './policies/policy_2.json'...

The reason this works is because the type of a single-item string array gets simplified down to a string literal, which the function can handle. It's not something we intentionally...

@miqm will break out this last comment and track the fix with a separate issue

What is preventing you from authoring something like this?: ```bicep resource foo 'Microsoft.Solutions/applications@2021-07-01' = { name: 'foo' kind: 'ServiceCatalog' properties: { parameters: { storageAccountName: { value: storageAccountName } } }...

Can you share the code you have written (as text, not as an image, if possible)?

Can you also share how you are deploying this code and providing parameters? When I try this code in VS code, I don't see any errors.

Any errors triggered by `bicep build` will also show up in VS code. When I run `bicep build` I do not get any errors. I also attempted to deploy this...

We do want to align the Az PowerShell and Az CLI installations so they install to the same location. That is tracked with #3447. VS Code is actually a different...