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 votes
This feature is now in public preview. https://docs.microsoft.com/en-us/azure/automation/automation-update-management#using-dynamic-groups
I want to have option - button - to update now server (once), now (no scheduling)62 votes
We are working on this feature
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 votes
You 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.
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?