---
title: "Updating Signer on Azure App Services"
description: "How to update Signer on Azure App Services: check the installed version, back up the database, publish the new package through Kudu, confirm the new version and know how to roll back."
canonical: "https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/azure/update"
locale: "en"
product: "Signer"
last_updated: "2026-10-22"
---

# Updating Signer on Azure App Services

This page shows how to update an on-premises Signer instance installed on an App Service following the
[Azure App Services setup](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/azure).

## Before you update

1. Check the installed version. Open `https://<your-domain>/api/system/info`. The `productVersion` field shows the version.
1. Read the [changelog](https://docs.lacunasoftware.com/en-us/articles/signer/changelog) of every version between yours and the new one. Look for the versions
   marked as changing the database model.
1. If you are moving from 2.x to 3.x, also follow [Updating to 3.x](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/update-30#azure-app-services).
   On a Windows App Service, the *.NET version* setting must be **.NET 10 (LTS)**.
1. Update the staging App Service first. Test sending and signing documents before you update production.
1. Pick a low-usage time. On the first startup, the application updates the database when the new version changes
   the model.

> **Warning**
>
> If the App Service Plan runs more than one instance, only one must update the database. Scale the plan down to one
> instance (*Scale out*) before you update, and scale it back after the site starts.

## Backup

1. In the Azure portal, open the Signer *SQL database* and check that you can do a point-in-time restore to the time
   before the update. If you prefer, create a copy of the database with **Copy**.
1. Keep the `.zip` package of the installed version. You will need it if you have to restore the binaries.

The App Service settings (**Configuration**) and the storage account files do not change with the update.

## Update

1. Download the new version package: `https://cdn.lacunasoftware.com/signer/signer-<version>.zip`. The links for each
   version are in the [changelog](https://docs.lacunasoftware.com/en-us/articles/signer/changelog).
1. In the App Service **Overview**, click **Stop**.
1. Go to **Advanced Tools** and click **Go** to open Kudu.
1. In the top menu, click **Tools** and then **Zip Push Deploy**.
1. Drag the `.zip` package onto the file list and wait for the deploy to finish.
1. Make in **Configuration** the changes the changelog asks for and click **Save**.
1. In **Overview**, click **Start**.

## Check the update

1. Open `https://<your-domain>/api/system/info` and check that `productVersion` shows the new version. The first
   request can take a while as the database is updated.
1. If there is an error, check the logs in the storage account table set in
   `Serilog__WriteTo__0__Args__storageTableName` (default: *SignerLog*).

If the site does not start and the log shows `PKI SDK License was not loaded successfully`, the application did not
load the PKI SDK license (missing, invalid or expired). Ask Lacuna for an updated license and set it in
`PkiSuite__SdkLicense`.

## If something goes wrong

If the new version has a problem, contact Lacuna support first. If you must go back to the previous version, follow
the [version rollback](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/rollback). To restore the binaries, publish the previous version's `.zip`
package through Kudu.

## See also

* [Azure App Services setup](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/azure)
* [Version rollback](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/rollback)
* [Changelog](https://docs.lacunasoftware.com/en-us/articles/signer/changelog)