<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bicep on Erwin Staal</title>
    <link>https://staal-it.nl/tags/bicep/</link>
    <description>Recent content in Bicep on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/tags/bicep/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enforcing Microsoft Defender for Cloud Across 30&#43; Subscriptions With Bicep</title>
      <link>https://staal-it.nl/posts/azure-defender-for-cloud-settings/</link>
      <pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/azure-defender-for-cloud-settings/</guid>
      <description>&lt;p&gt;Security posture management is one of those things that starts manually and stays manual for too long. Someone enables Defender for Cloud on a subscription in the portal, picks a few plans, saves. Six months later a new subscription appears, nobody remembers exactly which plans were enabled on the others, and the configuration drifts. An audit comes along and suddenly you&amp;rsquo;re comparing screenshots.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Creating reusable modules with Bicep, Terraform or Pulumi</title>
      <link>https://staal-it.nl/posts/modularizing-iac-bicep-terraform-pulumi/</link>
      <pubDate>Sun, 12 Mar 2023 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/modularizing-iac-bicep-terraform-pulumi/</guid>
      <description>Over the years, I’ve been working with several infrastructure as code tools. One of the things that I always find essential, no matter the tool, is to write readable and maintainable code. One way to do that is to create a proper structure for what you are building. All of the IaC tools I have used allow you to modularize your code somehow. A module is a piece of code responsible for one specific thing.</description>
    </item>
    
    <item>
      <title>Run a script during deployment with DeploymentScripts in Bicep</title>
      <link>https://staal-it.nl/posts/run-a-script-during-deployment-with-deploymentscripts-in-bicep/</link>
      <pubDate>Wed, 04 Jan 2023 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/run-a-script-during-deployment-with-deploymentscripts-in-bicep/</guid>
      <description>On a recent project, I was using Terraform to build some infrastructure. It contained an Azure Web App with a custom domain configured. A custom domain name on a Web App allows you to access it using a friendly URL instead of the &amp;lt;your_name&amp;gt;.azurewebsites.net. In this project, the DNS records for the domain were hosted and managed on Cloudflare. Luckily, Terraform has a provider for both Azure and Terraform, and thus I could write a single module that would create the Web App, set the domain in Cloudflare, and configure the custom domain.</description>
    </item>
    
  </channel>
</rss>
