Currently Virtual Machine Health Advisories sends an e-mail to the subscription administrator informing the affected VMs of the advisory.What if the affected resources (virtual machines) were listed in the health advisory itself? Instead of researching for e-mails, the management team can validate info in the portal, and plan migration accordingly instead of waiting for subs admin to find it and share.Similar approach is already in place for Planned Maintenance, hence this is just a similar improve.Example of current way it shows in Portal:An upcoming hardware update will affect virtual machines (VMs) in East US 2, from 5/7/2019 00:00 UTC until 5/12/2019 00:00 UTC. During this planned window, IaaS virtual machines will be migrated to newer network hardware. Please expect each VM to be unavailable for up to 15 minutes after initiating the migration. Operating system and data disks will be retained, but temporary disks will be reset.See a list of your affected VMs within an email sent to subscription administrators at approximately 7:30PM UTC on April 5, 2019.
