Update Management
Please take a few minutes to submit your idea or vote up an existing idea. All of the feedback you share in these forums will be monitored and reviewed by the Update Management engineering team.
-
Dynamic Update Deployments
Update deployments needs to be dynamic. As of now if we target a group of 5 servers the deployment is static and will always target only these 5 servers, even if the group changes and have 100 servers in it. The update deployment should be able to evaluate the group membership at each runtime.
69 votesThis feature is now in public preview. https://docs.microsoft.com/en-us/azure/automation/automation-update-management#using-dynamic-groups
-
Update now
I want to have option - button - to update now server (once), now (no scheduling)
62 votesWe are working on this feature
-
Ability to apply updates on VMs in multiple subscriptions
Our large enterprise customers has large number of VMs in large number of subscriptions. We manage automation via a central Azure Automation accounts. Currently Update Management appears to work only on VMs in the subscription containing Azure Automation account. Ability is needed so that we can target Azure Automation Update Management to work on VMs in multiple subscription.
50 votesYou can now enroll machines from multiple subscriptions into a single Automation Account. https://docs.microsoft.com/en-us/azure/automation/automation-onboard-solutions-from-browse
However, we still have the requirement that machines enrolled in Update Management only enroll into a single Log Analytics workspace.
-
Fix "week days" scheduling so that it sticks
When I choose "week days" as my scheduling option, it only works for the first run of the schedule. The next scheduled date takes on the same day of the month as the first run, and when I go to edit the schedule, it has reverted to "Month days". This means I must continually check on my schedules and adjust them after each run. Please fix. Thanks.
3 votes
- Don't see your idea?