| To change the vnet of a VM, you still need to deallocate it and restore it into the new vnet. Anything they don't offer directly, they offer a pile of canned VMs authored by Bitnami, who adds their own layer of management scripts to them, which (in our case) corrupted the filesystem on restarting from the great Shellshock cloud reboot. Azure is, in part, an ad-hoc cloud offering made up of services offered by mutually incompatible business units. Adding analytics in the dashboard has a 50% chance of routing you off of Azure to a separate MS monitoring/analytics solution (OMS) requiring its own licence. Their linux management agents have repeatedly locked up our VMs. Because of the way Cosmo pricing works, we were billed ~$5,000 over 3 months for 50MBs of data that was basically unused at the time--because you pay for "reserved network units" on a per collection basis (as in a mongo collection), and the floor pricing drove it that high without any utilization. As parent said, it's a bunch of MVP garbage, to which I'd add: to tick a bunch of checkboxes for Fortune 100s to sign 8-9 figure deals with promises of volume pricing. Operationally it's flea market. |
* When selecting a VM size in the new-VM wizard, it silently resets it to "DS1 v2" a bit later. You have to go back to the first tab and re-select the size you really wanted.
* This then promptly resets my "Already have a Windows Server license?" setting so then I have reapply that too.
* The default VM template suggested is Windows 2016, not Windows 2019.
* The selection box for the region keeps resetting to US East, even though that's the worst location for me. There is no default location setting in the portal that I can set for myself. This is an Enterpise-wide setting only.