AllegroGraph is available as an Azure Linux Virtual Machine image on the Azure Marketplace.

More information about Azure VMs can be found in Microsoft documentation:

Creating an AllegroGraph VM

The simplest way to create an instance based on the AllegroGraph VM image in your Azure account, is to go to this page on the website which links to the appropriate Azure page.

It is also possible to create a VM instance programmatically using Azure CLI, PowerShell, ARM templates or other tools. For more information visit

Choosing an instance type

Choosing an instance type depends on your use case and amount of data you want to operate with. As a default for experiments with AllegroGraph, we recommend D4ds type. For more information on instance types visit

AllegroGraph instance details

An AllegroGraph user with administrative privileges under the name admin is created upon first boot of the VM, with randomly generated password appended to /home/azureuser/README. Logged in as this user, you can create additional users, specify user permissions, and modify admin's password. (You can create a new user with administrative privileges and delete admin if desired.)

By default AllegroGraph VM image has open ports 10035 for HTTP access, and 10036 for SSL. They will be accessible from the internet if you assign a public IP for your VM instance.

To use the AllegroGraph command line tools such as agtool, you must enable SSH access to the VM instance. AllegroGraph is installed under the UNIX user azureuser in the /home/azureuser/agraph-home/ (that is the AllegroGraph installation directory referred to elsewhere in the documentation). The path to agtool is /home/azureuser/agraph-home/bin/agtool. The path to data directory is /home/azureuser/agraph-data/.

SSH access

We recommend that you generate new ssh keys for azureuser when creating a VM instance to have an easy and secure access to the instance.

If you are going to use a Linux environment (including WSL) to connect to the instance with SSH, then you must change the permissions on the private key file generated by Azure to be more restricted:

chmod 600 private_key.pem

Otherwise by default Azure VM will block corresponding public key on connection attempt, you won't be able to access the VM instance and will have to create a different one.