Like many people, I’ve been using Azure Copilot to help with Azure Administration tasks and operations, and have seen how it can really help to enhance […]
Naming every module in Azure Bicep used to be mandatory. With the release of the optional module names setting an explicit module deployment name is now optional. With […]
Azure provides multiple ways to interact with and provision resources, each designed to suit different workflows and preferences. Whether… Continue reading on Azure Terraformer »
The text explains the process of managing Azure subscriptions, particularly how to cancel a subscription and track its status using Azure Monitor and Log Analytics. It […]
This blog post discusses methods for passing resource information, primarily focusing on Azure Bicep modules. It outlines two approaches: passing full resource IDs and using user-defined […]
This is my involvement in Azure Spring Clean 2025, organized by Thomas Thornton, which I`m excited to be part of! For those unaware, the event promotes […]
For the Bicep language, an extensibility framework exists that adds capabilities to extend Infrastructure as Code deployments to other resources and providers. The extensibility framework is […]
Parameters are essential when authoring Bicep configuration files. They make your template reusable and polyvalent. In this blog post, I will explore ways to manage parameters […]
Sometimes, deploying a Bicep template using the preferred main.bicep method is not possible due to insufficient deployment permissions, especially when deploying across different subscriptions. This requires […]
As Infrastructure as Code (IaC) practices continue to evolve, maintaining clean and error-free code is crucial for seamless deployments. For this process, I have been working […]