Forum Discussion
Upgrade monitor is Unsupported
Noticing that a lot of VMs have upgrades for Azure Monitor, but they are then listed as Unsupported.
Can't see why though, anyone know where I can find information
19 Replies
PatrikHansson The following Azure resource providers need to registered for your subscription to enable Azure Monitor for VMs guest health.
- Microsoft.WorkloadMonitor
- Microsoft.Insights
I am having the same issue on several VMs, i would guess they have forgotten to write the pre-requisite that it needs to be "gen 1" VMs.. as i can enable on gen1 but not on gen2 VMs.
vitalyFMicrosoft
Raaert , I did some digging and I think you're referring to "gen1" or "gen2" images of Windows Datacenter OS. At this point upgrade UX erroneously blocks upgrade for VMs with images not on "known good" list. That list includes gen1 but not gen2 OS image. We're working to do two things on the upgrade UX:
a/ Update "known good" list to the latest (that one will include gen2 OS images
b/ Fix upgrade UX to allow to proceed in case VM image isn't on known good image list.
In the meantime, upgrade can be accomplished using ARM templates as described here: https://docs.microsoft.com/en-us/azure/azure-monitor/insights/vminsights-health-enable?tabs=powershell
PatrikHansson This is probably related to the new "https://azure.microsoft.com/en-us/updates/azure-monitor-for-virtual-machines-guest-health-preview/" feature that's in public preview. That new feature has some https://docs.microsoft.com/en-gb/azure/azure-monitor/insights/vminsights-health-enable?tabs=powershell#current-limitations regarding operating systems and the Azure regions in which the feature is available.
If my suspicion is correct, the VMs are either running an unsupported OS, or are in a region that's not yet supported for Virtual Machines Guest Health. Or the Log Analytics workspace is not in a supported region.
- vitalyF
There are limitations around using Guest VM Health preview feature and you're likely running into one of them. UX is fairly strict in how it handles the checks at onboarding time, but the full picture is the following:
1. VM must be in Azure (Arc or on-prem virtual machines are not supported at this time);
2. You should have "write permission" to VM - be able to install extensions, configure system managed identity;
2. VM must be in supported region (https://docs.microsoft.com/en-us/azure/azure-monitor/insights/vminsights-health-enable?tabs=powershell). The list of regions is expanding and we just made a few new ones available in addition to the starter set - UX may not support all regions until it catches up. The regions stated in the docs are supported via scripting (when you onboard using ARM templates) and majority of those supported via UX as well;
3. VM must be sending guest health data to a Log Analytics workspace in a supported region. This is a somewhat tricky requirement. When onboarded from UX, LA workspace is already assigned (when you onboarded to VM Insights) and that's the one UX sets as destination for guest health data, but when onboarding though ARM templates you can set a different/new workspace and place that one in a supported region. That makes data flow somewhat more complex, but allows you to work around LA regions requirement if you wish. We're also working to expand set of regions supported for workspaces;
4. VM must run supported OS. In simple terms we state that we support Windows Server 2012 and up, Ubuntu 16 & 18. In reality, custom distros (built on Ubuntu) and other Linux flavors will likely work, we're just being careful on UX to explicitly state we tested and confirm these distros are fine. What OS are you running?
We will also be working on UX to provide more information on top of "Not supported" to indicate the actual reason (such as "Write permission required", etc).
Does this mean you have to enable guest-level monitoring for the VM beforehand? Because that seams to be the thing that stands on out for the VMs that i was able to upgrade.
3. VM must be sending guest health data to a Log Analytics workspace in a supported region. This is a somewhat tricky requirement. When onboarded from UX, LA workspace is already assigned (when you onboarded to VM Insights) and that's the one UX sets as destination for guest health data, but when onboarding though ARM templates you can set a different/new workspace and place that one in a supported region. That makes data flow somewhat more complex, but allows you to work around LA regions requirement if you wish. We're also working to expand set of regions supported for workspaces;
