DynamicsSubs

¡Hola! I am sure you must have gone through my earlier post that housed an introduction to Azure Bicep and how we can easily manage mass deployment of resources, dynamically using the same: https://subsd365.blogspot.com/2024/05/manage-your-azure-resource-deployments.html This blog itself gave you an insight of deploying Azure resources and resource groups using Azure biceps. However in my next blog, I will take a deeper look at Azure bicep, giving you a feel of creating and managing and deploying a bit more complex resources which have dependencies and a lot of overheads to consider. One of the shortfalls of the ARM template was: your ARM template is always needed to be tagged to a subscription or a resource group. Consequently it's very difficult to create a resource group and then add resources to that resource group. What you used to do as a workaround was: to create two independent templates: one for resource group and then another for resources, and then execute them sequent...

  In a world where we live by action, automation and speed, Azure Biceps are an awesome way to expeidate your deployments. Biceps are new normal and monograms of infrastructure-As-Code, where you can manipulate your resource creation by feeding in parameters, inputs and varying conditions through Azure CLIs. Confused? Let me bring up the definition of Azure Biceps, from Microsoft's definition:  Bicep is a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources. In a Bicep file, you define the infrastructure you want to deploy to Azure, and then use that file throughout the development lifecycle to repeatedly deploy your infrastructure. Your resources are deployed in a consistent manner .  You cane create any resource, resources -- any number of them, simply mainitaining their defintions on simple module based files and invoking their deployments through Azure CLI based commmands. As compared ARM templates: Bicep syntax reduces that complexity...