Bicep, a declarative language which provides an alternative to JSON for deploying ARM templates.

For anyone like me who has never been particularly comfortable working with JSON when deploying resources to Azure. There is a new language called Bicep which provides a more declarative approach to working with ARM templates.

According to Microsoft Bicep offers the following benefits:

• Support for all resource types and API versions: Bicep immediately supports all preview and GA versions for Azure services. As soon as a resource provider introduces new resources types and API versions, you can use them in your Bicep file. You don’t have to wait for tools to be updated before using the new services.
• Simple syntax: When compared to the equivalent JSON template, Bicep files are more concise and easier to read. Bicep requires no previous knowledge of programming languages. Bicep syntax is declarative and specifies which resources and resource properties you want to deploy.
• Authoring experience: When you use VS Code to create your Bicep files, you get a first-class authoring experience. The editor provides rich type-safety, intellisense, and syntax validation.
• Modularity: You can break your Bicep code into manageable parts by using modules. The module deploys a set of related resources. Modules enable you to reuse code and simplify development. Add the module to a Bicep file anytime you need to deploy those resources.
• Integration with Azure services: Bicep is integrated with Azure services such as Azure Policy, template specs, and Blueprints.
• No state or state files to manage: All state is stored in Azure. Users can collaborate and have confidence their updates are handled as expected. Use the what-if operation to preview changes before deploying your template.
• No cost and open source: Bicep is completely free. You don’t have to pay for premium capabilities. It’s also supported by Microsoft support.

I only came across this on Friday, so not had a huge amount of time to work with it, but it looks very promising and seems to fit more into my way of working than when using JSON directly.

For more information check out the MS documentation https://bityl.co/7YWC.