Azure-docs: Scope of in case of VMs using availability zones

[tksh164]

In the case of the VMs with availability zones, what is the delivery scope of scheduled events? It is the same as standalone VMs?

Scope
Scheduled events are delivered to:

• Standalone Virtual Machines.
• All the VMs in a cloud service.
• All the VMs in an availability set.
• All the VMs in a scale set placement group.

As a result, check the Resources field in the event to identify which VMs are affected.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 479d877a-81a0-5436-76d9-898303c5bbec
• Version Independent ID: f352ae78-1d3f-a780-554c-fc304ada5a69
• Content: Scheduled Events for Linux VMs in Azure - Azure Linux Virtual Machines
• Content Source: articles/virtual-machines/linux/scheduled-events.md
• Service: virtual-machines-windows
• GitHub Login: @mimckitt
• Microsoft Alias: mimckitt

[VikasPullagura-MSFT]

@tksh164
Thanks for your Question! We are currently investigating and will get back on this.

[VikasPullagura-MSFT]

@mimckitt Can you please add your comments on this.

[mimckitt]

@tksh164 the scope is the same for availability sets. The idea of an AV set is the same in a AZ with the exception of it just spans across data centers instead of staying within the same one. I will update the doc to include that information now :)

[tksh164]

Thank you @mimckitt

[tksh164]

@mimckitt - Is the delivery scope of scheduled events really the same for availability set and availability zone? I tried it, but I could not confirm that behavior.

In case of the availability set, the event was notified to VM1 and VM2 if VM2 reboot. The event has VM2 as "Resources".

• Availability Set
  
  
  
  • VM1
  
  
  • VM2
  
  

{
    "DocumentIncarnation": 4,
    "Events": [
        {
            "EventId": "E49CEBE2-525D-4D56-A8F5-4035484A238B",
            "EventStatus": "Scheduled",
            "EventType": "Reboot",
            "ResourceType": "VirtualMachine",
            "Resources": [
                "as-vm2"
            ],
            "NotBefore": "Thu, 21 May 2020 18:03:01 GMT"
        }
    ]
}

But, in case of the availability zone, the event was notified to only VM3 if VM3 reboot. Also, not notified VM4. The event has VM3 as "Resources".

• Availability Zone
  
  
  
  • Zone 1: vm3, vm4
  
  
  • Zone 2: vm5
  
  

{
    "DocumentIncarnation": 1,
    "Events": [
        {
            "EventId": "5FDDB6DC-595B-4131-845D-B4CD5F97F31E",
            "EventStatus": "Scheduled",
            "EventType": "Reboot",
            "ResourceType": "VirtualMachine",
            "Resources": [
                "az-vm3"
            ],
            "NotBefore": "Thu, 21 May 2020 18:34:33 GMT"
        }
    ]
}

[mimckitt]

Will confirm and get back to you

[tksh164]

Do you have any updates?

[mimckitt]

Sorry for the delay. I have been following up on this. I expect to hear back this week and will provide an update.

[mimckitt]

Got this figured out.

The scheduled events go to single VMs in a zone and group of VMs in AVset. E.g. if you have 100 VMs in a AvSet and there is an update to one of them, the schedule event will go to all 100, whereas if there are 100 single VMs in a zone, then event will only go to the Vm which is getting impacted.

So it does still work with Availability Zones it seems it displays a bit differently. I will be updating the doc to make this more clear.

[tksh164]

@mimckitt - Thank you for your update. I will be waiting for the document update.

[mimckitt]

Adjusted the doc. Once the PR merges the changes take a few hours to go live.

Thanks again for pointing this out! Glad we caught this and were able to improve the doc and make the experience more clear.

please-close