Forum Discussion
Upgrade monitor is Unsupported
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.
vitalyFMicrosoft
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;
- vitalyF
PatrikHansson , not sure what you mean exactly, but if I understood it correctly the answer to your question is "yes".
To elaborate more: VM Guest Health is a feature of Azure Monitor for VMs: https://docs.microsoft.com/en-us/azure/azure-monitor/insights/vminsights-overview and, in order to turn on Guest VM Health feature you need to have AzMon for VMs already enabled for a given VM.
While Guest Health is in preview, enablement step for that specific feature is separate, i.e. you first onboard to AzMon for VMs and, if pre-reqs are satisfied, will be offered to upgrade to include Guest Health feature (you do not have to do it - your can chose).
I can only enable it on 1 out of 4 VMs.
The other VMs says "Unsupported".
1. VMs is in Azure,
2. I have write permission (i am global admin everywhere)
3. VM, workspace, logs ect. is all in West Europe
4. VMs run Server 2019 (image from Azure)
I am not seeing any pre-requisite that my VMs does not comply with..
- vitalyF
Raaert , would it be possible for you to send me subscription id, resource group name and VM names for those four VMs (or simply ARM resource ids of those). vitalyf at microsoft.com is my email address - we can check our telemetry to understand why UX thinks only one VM of those four is upgradeable.
One thing we did find is that UX tends to be very strict about checking OS image. We will change that in coming days, but at this point if UX can't be absolutely sure VM image is "default" Azure image, it will consider VM unsupported and won't allow upgrade. We will relax that criteria as I mention. At this time it is still possible to upgrade using ARM templates as described here: https://docs.microsoft.com/en-us/azure/azure-monitor/insights/vminsights-health-enable?tabs=powershell
You already have DCR (it was created when you onboarded first VM), so, you just need to run one template to onboard VM. You can go to portal, type "deploy custom template" in search bar at the top and copy-paste template from documentation. Fill in parameters (VM name, VM region - looks like you at at "westeurope", VM OS type - windows/linux and DCR resource ID). Should be very easy and only the last parameter may be a bit hard to figure out.
Since you already have DCR you just need to find it and grab its resource id. DCR is created in the same resource group as your onboarded VM and has type "Data Collection Rule" - find that object and grab its resource id in the form "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/my-resource-group/providers/Microsoft.Insights/dataCollectionRules/Microsoft-VMInsights-Health-weu" and that's the parameter you'll need.
Hope this works for your remaining VMs at this point.
