Azure Bicep's known limitations
Like any other tool, Bicep has some limitations, and considering how new it is, it does make sense for some of these issues to have not been addressed yet. So, let's see what these limitations are and where to find more information about them.
Single-line objects and arrays
The first known limitation is that there is no support for single-line objects and arrays. You might have used an array to create multiple resources using copy in your ARM templates, in which case you would have passed an array parameter (that is, [‘a', ‘b', ‘c']). You cannot have the same in Bicep, but this can be done using a new line:
allowed: [ ‘Basic' ‘Standard' ‘Premium' ]
Work is in progress to add support for this, and you can find updates in their GitHub repository at https://github.com/Azure/bicep/issues/498.
