AzureFunBytes – Getting started with Bicep

Jay Gordon

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.

We’ve just finished Microsoft Build! There were 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 with Azure Bicep, a new Microsoft approach to deploying Azure resources using Infrastructure as Code. 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 there are various methods for writing infrastructure as code (IaC), such as Ruby, etc. Bicep 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. Just like ARM templates, Bicep relies on the JSON syntax to compile and deploy your desired infrastructure.

What is Bicep (Preview)?
Install Bicep (Preview) Bicep on GitHub
Quickstart: Create Bicep files with Visual Studio Code
Bicep Playground
ARM template documentation
Tutorial: Create and deploy first Azure Resource Manager Bicep file
Bicep on Twitter

Learn about Azure fundamentals with me!

Live stream is available on Twitch, YouTube, and LearnTV at 11 AM PT / 2 PM ET Thursday. You can also find the recordings here as well:

AzureFunBytes on Twitch
AzureFunBytes on YouTube
Azure DevOps YouTube Channel
Follow AzureFunBytes on Twitter


Discussion is closed.

Feedback usabilla icon