Azure Functions - Use Bicep unleash your creativity with VS code extensions resource visualization

You've probably seen how to create #Azure resources using the Azure portal. But that's a manual process and easily screw-up-able when you need to repeat the resource creation for multiple projects, or when moving from dev to production, or deploying your customer's solution to their Azure subscription.

Wouldn't it be better to script the resource creation and configuration process to ensure it's the same every time? What about versioning your resource configuration so it's part of your code?

You can with #Infrastructure-as-Code, or IaC. #IaC is popular in the #DevOps world and fits nicely alongside a complete CI/CD process. It involves creating your resources from machine-readable files that can be versioned with your project in source control.

In this video, I start with a blank slate and show you how to use Azure Bicep, a domain-specific language from Microsoft to create Azure resources for an #AzureFunctions App.