Skip to main content
Version: 2.24.0

Azure VM setup guide

Deploy the Glasswall Halo Virtual Appliance from Azure Marketplace, then configure Halo and verify file protection.

Prerequisites​

  • An Azure subscription with permission to deploy Marketplace offers, virtual machines, disks and networking resources.
  • Sufficient virtual machine (VM) quota in your chosen Azure region.
  • A Glasswall Halo license. The Marketplace offer uses Bring Your Own License (BYOL).
  • A Secure Shell (SSH) key pair, or permission to generate one during deployment.
  • A network path from your workstation to the VM.
  • For Transport Layer Security (TLS), a domain name with a matching certificate and private key. For single sign-on (SSO), the Microsoft Entra ID details described in the authentication guide.

Step 1 - Create the virtual machine​

  1. Sign in to the Azure portal and open the Marketplace listing linked above. Confirm the offer is Glasswall Halo Virtual Appliance by Glasswall Solutions.

  2. Select the Halo v2 plan and start creating a VM. This plan supplies the latest certified Halo 2.x image; check the selected image version before deployment.

  3. Choose your subscription, resource group, VM name and region.

  4. Select a VM size appropriate for the workload:

    • Core Content Disarm and Reconstruction (CDR) for development or testing: 16 virtual central processing units (vCPUs) and at least 32 GB of memory, for example Standard_D16as_v5.
    • Internet Content Adaptation Protocol (ICAP), storage monitoring, Foresight or any production workload: 32 vCPUs, for example Standard_D32as_v5.
    • Production with several features enabled: 48 vCPUs, for example Standard_D48as_v5.

    These examples follow the Marketplace listing. Check availability in your region and the minimum requirements for your enabled features.

  5. Under Administrator account, select SSH public key, enter glasswall as the administrator username and select or generate a key pair.

  6. On Disks, configure an operating system (OS) disk of at least 500 GB.

  7. On Networking, choose the virtual network and subnet. Use a public Internet Protocol (IP) address only if required by your access design; otherwise connect through your private network.

  8. Configure network security group inbound rules for the required Transmission Control Protocol (TCP) ports:

    • Port 22: SSH administration. Allow access from administrator IP addresses or the management network.
    • Port 443: Halo Portal and application programming interface (API). Allow access from intended users and API clients.
    • Ports 1344 and 11344: ICAP and ICAP with mutual TLS (mTLS), respectively, when enabled. Allow access from ICAP clients only.
  9. Click Review + create, review the configuration and offer terms and click Create. If generating an SSH key, download and securely retain the private key when prompted.

  10. After deployment completes, open the VM resource and record its reachable IP address.

For general portal guidance, see Microsoft's Linux VM creation guide.

Step 2 - Connect and configure Halo​

Connect using the glasswall administrator username and the SSH key selected during deployment:

ssh -i /path/to/private-key glasswall@<vm-ip-address>

Allow the appliance services to initialize, then run the setup wizard:

sudo halotui

Follow Using the wizard to configure TLS and Portal/API authentication. Keep networking managed by Azure; configure reserved addresses on the Azure network interface.

For manual configuration, see TLS/SSL configuration and Authentication.

Step 3 - Activate and verify​

  1. Open https://<halo-domain> using the domain configured for TLS, and confirm that the Portal loads with a valid certificate.
  2. Sign in using the authentication configured in the previous step.
  3. Activate your license using the Portal license setup guide or the API license setup guide.
  4. Protect a non-sensitive sample file in the Portal and confirm that a protected file can be downloaded.
  5. If using the API, open https://<halo-domain>/swagger/index.html and verify access with your configured credentials.

Troubleshooting​

  • VM size unavailable: check regional availability and your subscription's regional and VM-family vCPU quotas.
  • SSH times out: check the VM address, network route and effective network security group rules for port 22.
  • SSH authentication fails: use the glasswall administrator username and the private key matching the public key configured in Azure.
  • Portal or API times out: check port 443, Domain Name System (DNS) resolution and the network route to the VM. If SSH works, inspect service readiness with sudo kubectl get pods -A.
  • Certificate error: check that DNS points to the VM and that the configured certificate covers the hostname you are using.
  • File protection fails: check license activation and the license troubleshooting guide.

If the problem persists, contact Glasswall support.

Remove a test deployment​

When finished, delete the VM and review its associated disks, public IP and network resources for anything no longer required. Delete the resource group only if all resources in it belong to this deployment and are no longer needed.