In our environment all large amount of vm's is not started all the time. But need to be up to date. I could create runbooks to start the vm just before the scheduled update and deallocate at the end. But controlling this from the schedule itself could be helpfull.45 votes
This is now possible with pre/post steps (https://docs.microsoft.com/en-us/azure/automation/pre-post-scripts) and the examples here:
Upon scheduling an update deployment, message "....virtual machine being configured....", persists forever, no updates actually scheduled
Message "The components for the 'Update management' solution have been enabled, and now this virtual machine is being configured. Please be patient, as this can sometimes take up to 15 minutes." persists47 votes
Thank you for your feedback. We have released a deployment to address this issue. Please let us know if you have additional comments or questions.
Scheduled update deployments overview times do not correspond with planned times, or it only displays scheduled times in GMT.3 votes
We did have a bug in this area. It should be fixed. Please leave a comment if you still see the issue.
- Don't see your idea?