Launching the image
To launch it, you can either download the VHD image and upload it yourself, or use the URL of the public image that we've published on Microsoft Open Technologies's VM Depot.
For example, to create a VM in northern Europe using the Azure cross-platform CLI, simply run
azure vm create DNS_PREFIX -o vmdepot-50279-1-16 -l "North Europe" USER_NAME [PASSWORD] azure vm endpoint create-multiple DNS_PREFIX 25:25,443:443,80:80
- Create a new VM using whichever method you prefer
- Uncheck "VM agent"; otherwise the deployment will take longer as there's no agent installed
- The provided username/password won't be used, it defaults to "admin"
- Browse to its web admin on port 443
- Login with username and password "admin" (the credentials you choose in Azure arn't used)
- Choose a new password and specify a DNS server (such as Google's "18.104.22.168") in the getting started guide
- Once the getting started guide is completed, you will be redirected to the web admin's overview page
- Configure a storage disk on the System > Hardware page (for example Azure's included temp disk)
- Formatting the desired storage disk (the system will reboot)
- Login and go to the same page again, and choosing the desired storage disk at as storage device (the system will reboot again)
The system partiton is read-only during normal operation, and all data (email, database, definitions, temp) are written to a separate storage partition. There are many different storage partitions options; the most simple in the Azure case is to use the included "temp" disk that comes with all VMs. It's however not guaranteed to be persistent, and its use is discouraged unless you use for example in-line delivery.
Another option is to "extend" the system partitions's disk by adding the storage partition to the end of it. An option to use the system disk as storage will automatically appear on the System > Hardware page if it's large enough (more than 10 GB). This is very common in "bare metal" installations, because the system partitons's disk is almost always larger than the 500 MB that the system partition occupies. In a virtual machine scenario, this is as simple as resizing the system disk.