AzureFunBytes is a weekly opportunity to learn more about the fundamentals and foundations that make up Azure. It’s a chance for me to understand more about what people across the Azure organization do and how they do it. Every week we get together at 11 AM Pacific on Microsoft LearnTV and learn more about Azure.

This week is Microsoft Build! There are so many sessions to take part in! I wanted to spend some time using one of the amazing things that have come out of this huge event. I have been playing with Azure Bicep lately for creating my resources. Today I’d like to show you how to create a basic template and deploy it to Azure. Then I will look at how quickstart templates are converted in the Bicep Playground. We’ll look at the Bicep CLI install, the VS Code plug-in, and of course Azure CLI.

Bicep is a Domain Specific Language (DSL) for creating your Azure resources. While many different methods may select programming languages such as Ruby, Bicep really aims to reduce complexity by introducing a cleaner syntax for you to reuse your code more often. Bicep is a transparent abstraction of ARM templates, which differs from using another general-purpose programming language. Bicep uses Azure Resource Templates (ARM template) files in JSON to compile and deploy your desired infrastructure.

What is Bicep (Preview)? - https://cda.ms/28H
Install Bicep (Preview) Bicep on GitHub - https://github.com/Azure/bicep
Quickstart: Create Bicep files with Visual Studio Code - https://cda.ms/28J
Bicep Playground - https://bicepdemo.z22.web.core.windows.net/
ARM template documentation - https://cda.ms/28G
Tutorial: Create and deploy first Azure Resource Manager Bicep file - https://cda.ms/28F
Bicep on Twitter - https://twitter.com/BicepLang

#bicep