From e28fd0390b0c0e0652090217e8475dedc6a3eb91 Mon Sep 17 00:00:00 2001 From: Kunal Mohan Date: Tue, 20 Oct 2026 11:48:55 +0530 Subject: [PATCH] Fix azure docs --- .../deployment/public-clouds/deploying-on-azure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/server/how-to-guides/deployment/public-clouds/deploying-on-azure.md b/docs/server/how-to-guides/deployment/public-clouds/deploying-on-azure.md index 61a4b93..90d0b10 100644 --- a/docs/server/how-to-guides/deployment/public-clouds/deploying-on-azure.md +++ b/docs/server/how-to-guides/deployment/public-clouds/deploying-on-azure.md @@ -28,7 +28,7 @@ To set up the Livepatch Server on Azure using an Azure Blob Storage container fo ## Create the deployment -In Azure, Livepatch can be deployed on VMSS behind an Application Gateway with autoscaling configured on VMSS instances. The VMSS instances can be configured to auto-install the Livepatch Server snap at startup using a cloud-init configuration file in a Standard Ubuntu Server image. This guide uses a PostgreSQL server for patch storage. +In Azure, Livepatch can be deployed on VMSS behind an Application Gateway with autoscaling configured on VMSS instances. The VMSS instances can be configured to auto-install the Livepatch Server snap at startup using a cloud-init configuration file in a Standard Ubuntu Server image. This guide uses Azure Blob store for patch storage. ### Configure the VNet