UM-ScheduleUpdatesWithVmsTags.ps1 is creating a new schedule each run instead of updating the existing schedule or deleting old copies of the existing schedule.
UM-CleanUp-Schedules.ps1 only cleans up old schedules when the tag is missing. As such, my assumption is UM-ScheduleUpdatesWithVmsTags.ps1 should be updating the existing schedules and not creating a new one.
With this code, I'm unable to schedule Azure ARC enabled servers for patching. Though the scripts execute without any issues, the schedules created for Azure ARC servers do not have default 'patchomscomputers' linked runbook and hence no patching is taking place.
My understanding is that Azure Automation can only execute 200 jobs at a time. If most of our VMs are scheduled for the same date/time, what would happen if we exceed that limit (i.e. would they be queued or fail). I am concerned that having X number of VMs all with schedules at the same date/time would hit this limit but not certain.
Out of the list of hundres of VMs, only one patched, which was the one that I manually updated the schedule for. I notice this one is linked to Patch-MicrosoftOMSComputers. However, the ones created by UM-ScheduleUpdatesWithVmsTags.ps1 are not linked to the Patch-MicrosoftOMSComputers Runbook.