Intermediate Bicep - This learning path covers child and extension resources, managing changes to your code using Git, structuring your Bicep code for collaboration, previewing Azure deployment changes by using what-if, and migrating Azure resource and JSON ARM templates to Bicep.
Solution To address these challenges, we can leverage Bicep, a domain-specific language (DSL) for Azure resource deployment. Bicep simplifies the authoring experience and provides a more readable and maintainable syntax compared to traditional ARM templates.
A bicep module is a bicep file that describes a part of your infrastructure in a reusable way. You can start by having a library of bicep modules in a git repository that you can just use, or you can publish the bicep modules to a private repository for sharing among multiple projects. There is also a public repository that Microsoft maintains.
Did you know that you can now add user login to app deployed on Azure, with just Bicep code? No Portal, CLI, SDK, or app code needed! For those new to Bicep,...
Easily add login to your Azure app with Bicep | Microsoft Community Hub
After months of collaboration and invaluable community feedback, we're thrilled to announce that Azure Verified Modules for Platform Landing Zone using Bicep is now generally available! This release represents a significant milestone in the evolution of Azure Landing Zones. Bicep customers can now leverage the same modular, flexible, and battle-tested approach that our Terraform community has ...
Deploying AI solutions at scale requires more than just innovation; it necessitates automation. In this updated blog, we explore how to optimize and standardize Microsoft Foundry deployments using Infrastructure-as-Code (IaC). By leveraging the declarative capabilities of Bicep alongside the automation features of GitHub Workflows, you can establish reproducible, secure, and fully automated ...