One Identity Safeguard for Privileged Sessions 5.7.0 - Deployment from Azure Marketplace


This document describes how to deploy One Identity Safeguard for Privileged Sessions (Safeguard for Privileged Sessions) as a Virtual Machine from the Azure Marketplace.

Deploying One Identity Safeguard for Privileged Sessions from the Azure Marketplace

This guide provides detailed descriptions for deploying One Identity Safeguard for Privileged Sessions (Safeguard for Privileged Sessions) from the Microsoft Azure Marketplace.

Before you start:

Before you start evaluating Safeguard for Privileged Sessions, make sure you understand what Safeguard for Privileged Sessions is and how it works. This information can greatly help you get Safeguard for Privileged Sessions operational. Read the following:


The following prerequisites must be met to deploy Safeguard for Privileged Sessions in Microsoft Azure:

  • You have a valid One Identity Safeguard for Privileged Sessions license. When deployed from the Microsoft Azure Marketplace, the One Identity Safeguard for Privileged Sessions uses the "Bring your own license" model. Note that to deploy two active Safeguard for Privileged Sessions nodes as an availability set, you must purchase two standalone Safeguard for Privileged Sessions licenses. To purchase a license, contact our Sales Team.

  • Microsoft recommends to use the Azure Resource Manager (ARM) deployment model. When you install Safeguard for Privileged Sessions from the Azure Marketplace, Safeguard for Privileged Sessions supports only this deployment method. If you need to deploy Safeguard for Privileged Sessions into and infrastructure that uses the Classic deployment model, contact your One Identity sales representative.

  • You have a Microsoft Azure account.


The following limitations apply to Safeguard for Privileged Sessions when you deploy it from the Microsoft Azure Marketplace.


Do not export or import configuration between a physical Safeguard for Privileged Sessions deployment and a virtual one. Because of the differences and limitations between physical and virtual appliances, configure the virtual appliance from scratch to ensure proper functionality. When you migrate a virtual Safeguard for Privileged Sessions to another one, you can export and import the configuration.

  • Root login is not available on the console.

  • SSH access is only available after you have completed the Welcome Wizard.

  • Currently, the data that is entered during the provisioning phase (for example username, IP address) of creating the virtual machine in Azure is not transferred to Safeguard for Privileged Sessions. Therefore, only the data entered in the Welcome Wizard will be used.

  • By default, you can only use Physical interface 1 (eth0) of Safeguard for Privileged Sessions, with a single IP address. Aside from changing the IP address of Safeguard for Privileged Sessions, do not modify other interface-related settings (additional logical interfaces, IP forwarding, and so on) on the Basic Settings > Network page of Safeguard for Privileged Sessions.

    The number of interfaces you can use depends on the size of your Azure VM. If your VM allows you to use multiple interfaces, you can configure multiple interfaces in Safeguard for Privileged Sessions. For details, see VM with multiple NICs.

  • The Seal the box functionality is not available.

  • The High Availability support of Safeguard for Privileged Sessions was designed to work between two physical Safeguard for Privileged Sessions appliances. This feature is not available in Azure environments. For further details, see the High Availability and redundancy in Microsoft Azure.

  • Due to Azure requirements, an additional 5-minute delay has been added to the boot process. This ensures that the root device appears in the system.

  • The size of the hard disk in Azure is 100 Gb. You cannot extend this virtual disk size later, nor can you write to Samba or other disks. In case you run out of disk space, either configure a Backup policy and an Archive policy if you have a server for this purpose, or configure a Cleanup policy that deletes the audit trails at certain time intervals. For details, see "Data and configuration backups" in the Administration Guide and "Archiving or cleaning up the collected data" in the Administration Guide.

  • Safeguard for Privileged Sessions currently cannot receive its IP address using DHCP. Make sure that:

    • The IP address you have configured in Azure and the IP address that you configure for Safeguard for Privileged Sessions for the Physical interface 1 on the Networking settings part of the Welcome Wizard are the same. Otherwise, you will not be able to access Safeguard for Privileged Sessions.

    • You set the internal IP static on the Network Interfaces tab of the Virtual Machine.

    • Do not assign a public IP address to Safeguard for Privileged Sessions, use Safeguard for Privileged Sessions as a component of your internal infrastructure. If you absolutely must configure Welcome Wizard from a publicly accessible IP address, note that Safeguard for Privileged Sessions will be publicly accessible. If you assign a public IP to the web management interface, consider the following:

  • Upgrading Safeguard for Privileged Sessions in Azure is the same as upgrading a physical appliance: you have to upload the firmware on the Safeguard for Privileged Sessions web interface. For detailed instructions, see Upgrade Guide.

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents