![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 64%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOI%3C/text%3E%3C/svg%3E)
Azure Update Manager
An Azure service to centrally manages updates and compliance at scale.
321 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
In Azure Update Manager, the process has evolved, and runbook-based patching is no longer directly integrated as it was in Update Management. Instead, Azure Update Manager focuses on automating patch orchestration without relying on runbooks. However, if you still need to use runbooks for custom logic or specific workflows, you can create automation workflows separately and trigger them using other mechanisms, such as Azure Automation or Logic Apps, alongside Azure Update Manager's features.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin
