Hi there, I’m Robin!

Failed to save Kubernetes service - addonProfiles.ingressApplicationGateway.config.applicationGatewayId is invalid I ran into an issue when deploying Azure Kubernetes services using ARM Templates. We previously set the ingress-agw addon to configure the ingress using an application gateway. We recently moved to the Azure Application Gateway Ingress Controller using Helm and simply set the addon configuration to ’null’ but that creates a conflict when making other changes such as changing the SKU (Pricing Tier) of the cluster. ...

Disable Health Probe on Azure Front Door Origin Groups using Bicep If you want to know how… read on! Introduction For origins with a single backend it is recommended by the Microsoft Learn documentation to disable the health probe to prevent the Front Door from consuming resources on your backend. Because I had troubles disabling the Health Probe using Bicep, because of lacking documentation on how to disable it, specifically for the Front Door Standard / Premium, which seems to belong to the Microsoft.Cdn resource provider. I wanted to share with you how you can disable the Health Probe, as it is quite easy, but if there is no documentation about this then it may take some time to figure it out. Click here to find out how to disable it or just continue reading. ...

Azure Automation Runbook: Could not convert string to DateTimeOffset I recently started getting issues with different customers in which we use Azure Automation for Update Management. We use the pre- and post runbook functionality for quite some time already, but recently we started getting these errors.. on multiple lines in the runbook output: "Could not convert string to DateTimeOffset: 1619773997. Path 'expires_on', line 1, position 2937." While researching this issue I figured out it had something to do with Az Powershell and depending on a older or newer module within one of the submodules. (which can be found here{:target="_blank"}) ...

Azure Update Management: You have requested to create an update configuration on a machine that is not registered for Update Management We have several customers running with our Update Management solution via Azure Automation. We schedule the deployments via Powershell and Azure DevOps. I have ran into several issues after migrating VM’s to Azure or moving VM’s within Azure. Somehow the System Hybrid Worker gets corrupted and does not work anymore, so update deployments will fail with the following warning: ...