Automate Azure Image Builder in Bicep with custom builder resource group
Of course we want to secure and keep our Azure tenant tidy with the help of Azure Policies. And without any hesitation I preach to automate everything! But what if these two mindsets conflict with one another? What if there is an Azure Policy in place that demands a naming standard or tags for resource groups that causes an automated Azure Image Builder deployment to fail? With Azure Image Builder (AIB) we can automate the process of building images for use in an Azure Virtual Desktop environment for instance....