Preparation
1.Login to the Azure Portal with an account that is able to create resources.
2.Create a new resource group for your SEPPmail VM or select an existing one.
3.Create a new storage account or select an existing one. The storage account needs to have a container, this is needed to store the SEPPmail VM image.
4.Download the newest SEPPmail disk image from downloads.seppmail.com, select the "Hyper-V" image.
5.Upload this image to the container created or selected previously.
Create Disk
Create a new disk image, based on the uploaded SEPPmail disk image.
1.Select "Images" in the Azure portal.
2.Select "Create".
3.Enter name, region and resource group.
4.Select "Linux" .
5.Select "Gen1" VM Generation.
6.Browse and select the storage blob previously created.
7.Select the Account Type (Disk class) based on your performance requirements.
8.Host Caching: To avoid any caching related data loss we recommend "none" .
9.Key Management: Platform managed key or other required encryption based on your requirements.
10.Other settings like "Zone resiliency" may be set, based on your availability requirements.
11.Add Tags as required and create the disk.
Create VM
1.Go to "Virtual Machines".
2.Click on "Create a Virtual Machine".
3.Select the resource group, VM name, region and availability options.
4.In "Images", select "see all images ==> my images".
5.Select the recently created image.
6.Select availability options based on your requirements.
7.Select sizing based on your requirements (see docs.seppmail.com for sizing recommendations).
8.In "Authentication" select SSH, as username password doesnt work with the SEPPmail Appliance in Azure.
9.Select Inbound ports (usually HTTPS for GINA, SSH maybe only for the internal network).
10.Set License type ==> Other.
11.In "Disks", create an additional disk if you want to use "GINA cache mode" or LFT. The disk should be 30GB+. Disk parameters can be set as required for performance and redundancy.
12.Review and create the VM.
13.You will be prompted to download the private key pair. Store them in a secure place and use them in your ssh sessions.
14.VM is provisioned - Test the running machine in the VM menu ==> Help ==> Serial console. If you get a login prompt, the machine is up and running.
15.After provisioning, you need to configure the network security group to access the appliance on the admin-interface via Port 8443.
16.There may be errors like "OSProvisioningTimedOut" which you can ignore, as the approach Azure provisions VM´s differs from our image concept.
