Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Setting Up Clustering Liferay Portal on Azure

Written By

Edward Han

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

This article details what is needed to setup Liferay on the Microsoft Azure cloud

Virtual Machine Setup

Azure manages all instances as Virtual Machines. Create a new instance in the Azure Dashboard and follow the prompts to setup all the components. Some key parts:

  1. Setup a virtual network. This will help to partition your Liferay cluster from the world. As part of this step you should create a public IP to connect to
  2. Setup the required storage accounts. Storage accounts are used to store you VM's image. They are also used for cross-vm filestores like the ones needed for document library. You should keep these separate as VM images are the core of your servers.
  3. Setup a resource group to manage your cluster (optional, helps with organization)
  4. Setup your database. This can be either Microsoft's SQL service or a VM with a DB installed such as Oracle or MySQL. Microsoft SQL will provide you with connection strings while other DBs require more hands on management of VMs.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?