Event banner
Event details
How far are we from having parity across ARM Templates, Bicep and Terraform? Right now we struggle with some deployments of Bicep and Terraform because they lag behind ARM. Thanks
Can you please explain further the lag that you have been experiencing with Bicep behind ARM?
Mark GrayMicrosoft
As far as Terraform is concerned, we have released the AzAPI provider which, like Bicep, supports all Azure services including preview services on day 0.
- adotfrankToday, there is parity between ARM Templates and Bicep. Any resource that can be deployed in ARM can be deployed via Bicep. While there can be some lag in availability in the AzureRM provider in Terraform, we recently introduced the AzAPI provider for terraform which also has the same parity between ARM Templates/Bicep/TF: https://registry.terraform.io/providers/azure/azapi/latest/docs
- Like Synapse deployment - as of a few months back this was not possible from our efforts. Workspaces, VNETs, Linked Services, etc.
- adotfrankMurray, we would need more details about what is not working with these resource types in Bicep. There should not be any gap between these two tools. It might be easier to file an issue in the bicep github repo so you can provide specific code samples, error details, etc. https://github.com/Azure/bicep/issues
