It’s recommended that you do not statically assign the private IP assigned to the Azure virtual machine within the operating system of a VM, unless necessary, such as when assigning multiple IP addresses to a Windows VM. If you do manually set the private IP address within the operating system, ensure that it is the same address as the private IP address assigned to the Azure network interface, or you can lose connectivity to the virtual machine. Learn more about private IP address settings. You should never manually assign the public IP address assigned to an Azure virtual machine within the virtual machine's operating system.
When purchasing a VPS hosting package the web hosting provider will manage all the hardware and while you will have administrative access through a control panel to do whatever you want with your server, they will still make sure that it is available, has up-to-date system software, it is secured and has the available hardware resources to run according to the VPS package specification.
I have some sites hosted on a shared-hosting/cpanel environment and need to make a move up. I have some experience running my own server, but it is very basic (a local box to do live testing/file serv). My question is how difficult is it to run a VPS, should I buy a managed VPS (with stuff already installed), or unmanaged (blank box), and lastly if I go for unmanaged what steps should I take to keep my VPS secure? Edit: Also how difficult is it to backup files and databases? Can it be automated?
Typical Use Case: Early stage startup workloads, quick prototypes, prelaunch experimentations, dev/test environments, microservices node, code repositories, dedicated application servers for light workloads. Resource intensive workloads like data aggregation, gaming front-ends, video encoding, high performance computing, batch processing. Also see our managed services for Startupreneurs.