Photo by Chris Liverani on Unsplash

Setup an Azure Runbook with a Webhook URI using Az.Automation CLI

Azure Resource Manager β€” ARM | Powershell Gallery | Azure Portal | Serverless | Functions

βš— Kevin Summersill πŸ”‹
Published in
3 min readAug 6, 2021

--

Microsoft inherently generates a Webhook when associating a Runbook to an Action Group. An Action Group is what is used to set up some sort of Action when an Alert is triggered from the metrics of a resource. However, the inherited webhook seems to only be an option within the Azure portal. A Webhook URI is a required parameter because the $Webhook payload is generated from the Alert to the Automation Accounts Runbook.

Digram explaining Runbook Webhook Association

If you are working with Azure Resource Management (ARM) templates you still are required to create a Webhook and associate that ServiceURI to a Runbook Reciever in an Action Group. However, after the ARM template is provisioned you may still have issues when it comes to updating a Webhook associated with an Action Group. You could technically rerun the ARM template for the Webhook and then rerun the template for the Action Group to update these in a declarative approach. Or…. You can just run a simple Powershell script. :)

--

--

βš— Kevin Summersill πŸ”‹
Geek Culture

Enterprise Solution Architect | Certified K8s Administrator/Developer βš“ | SAFe SPC | Cert Terraform | AWS Solutions Architect | Dev*Ops/GitOps Engineer πŸ”₯