jurjenoskam

@majastrz Unfortunately I haven't found a way to work around it, because anything you enter in the input field is not interpreted and simply becomes part of the literal contents...

Will this fix make it possible to use the Portal to deploy templates that use the complete feature set of languageVersion 2.0?

I was able to deploy a languageVersion 2.0 template in West Europe last Friday (April 5th), so this now seems to be implemented. Thanks!

We've just ran into this problem as well. This example template builds and deploys just fine: ```bicep resource uami1 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' existing = { scope: resourceGroup('rg-subscription-default-resources') name: 'deployment-uami-${subscription().subscriptionId}' } resource uami2...

It seems this should have been part of microsoftgraph/microsoft-graph-docs#7578, which says it "Graph: support add/remove/list owners on app, sp, and group". The PR did this for app and group, but...