Bicep modules provide this awesome feature to be able to create schema for your Bicep modules via User-defined data types. When you reference Bicep module in bicep template or bicep parameters file you get nice intellisense in VSC to understand the structure of the parameters, whether they are required or not and additional information. This is the same experience when you start to define a resource. I was one of the first requestors and adopters of the feature and I heavily use it every day. Although the feature provides great experience within VSC there is still a need to document that schema in some other place just like it is done for Azure resource. This trivial task is not so easy to do but today I will show you how easy it is by using GitHub Copilot.
Category: Azure
Azure Monitor Alert Types Dev.bg Presentation and Examples
On the 2nd of July I have presented Azure Monitor Alert Types session at dev.bg. As this was event in Bulgarian and I have publish the examples online you can check them at GitHub repository even if you haven’t attended.
Master IaC with Azure Bicep at Global Azure Bootcamp Bulgaria 2025
On the 10th of May I have presented Master IaC with Azure Bicep session at Global Azure Bootcamp Bulgaria 2025. As this was local event and I have publish the examples online you can check them at GitHub repository even if you haven’t attended.
Monitoring canceled Azure Subscriptions
Azure Subscription cannot be just deleted. They go trough different states. Although you might have taken all necessary to secure your Azure tenant sometimes mistakes happen or your environment might be compromised by bad actors. The first step of removing Azure Subscription is to cancel it. That is critical action that you may want to monitor although you should have in place other ways to monitor resources that will signal that they are not available. In any case additional alert that this action was done could be useful information to be alerted upon. In this blog posts we will take a look how we can do that by using Azure Monitor. The deployment of the Azure Monitor resource will be done via Azure Bicep.
Passing Resources between Azure Bicep modules
Bicep modules is core feature for structuring your code and achieving certain functionality when deploying Azure resources. When using modules quite often you will have to pass pass resource information like resource ID in order to be used within the module. Another use case is when an end user have to provide information for existing resource so that resource can be used for the deployment of another resource. This blog post will focus on the different methods for passing resources between modules or from bicep parameters file to module.




