Upgrade monitor is Unsupported

Richard Waal , PatrikHansson 

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).