 So Microsoft set out to simplify the challenges with ARM templates and they wanted to create something that had a concise syntax, reliable type safety and support for code reuse. That's what Bicep is. It's a domain specific language or a DSL that provides a much richer and more productive environment than what we get with ARM. In fact, you can compile a Bicep file down to an ARM template in vice versa. Now Bicep has a ton of benefits and Microsoft touts that Bicep has support for all resource types and API versions. It's also got a simple syntax, especially when you compare it to those ARM JSON templates. A better authoring experience thanks to a VS code extension that gives us type safety, intelligence, syntax validation and a bunch of other stuff. The result of a deployment to Azure with Bicep is repeatable, giving you confidence in your CINCD process. You don't have to worry about the ordering complexities of resource creation. You simply deploy with one command and Azure takes care of all that stuff for you. And it's also very modular so that you can break it up into different components that we call modules and Bicep. You can even preview what's going to happen to your deployment with the what if operation. You can see what's gonna be created, deleted or updated and any of the properties that are gonna be changed as well with that operation. And best of all, Bicep is included with Azure. You don't pay a thing and it's fully supported by Microsoft support.