• 12 Dec 2022
  • 2 Minutes to read
  • Contributors
  • Dark
  • PDF


  • Dark
  • PDF


Serverless360 allows users to upgrade their Private Hosting environment to the latest version with the help of Upgrade option present in the latest Deployment application.


The Upgrade option in the Deployment application helps users to begin with the migration process.

Initial step is to validate the connection strings of SQL database and Storage account created during the deployment.

Upon successful validation, Check for Updates button can be used to view the current version of the instance along with the available latest version.

Clicking the latest version number hyperlink displays the list of features and enhancements that are included in it.

PH Upgrade.gif

Users can check for updates directly from the Serverless360 application in the General Settings section or by using the Release update icon.

Release update.png

Breaking changes in 1.7.0

Serverless360 installation includes deployment of Azure Function apps in customers' Azure subscription.

Few months back, version 4.0 of function apps have been made generally available. As a result of the new version launch, it has been announced that the apps in version 2.x and 3.x will be deprecated after December 2022.

Considering the above change in Azure Functions, Serverless360 deploys 4.x functions during the deployment starting from version 1.7.0.

For the existing customers, they need to upgrade the existing Function apps to 4.0 manually.

Below are the Function apps that need to be upgraded,

  1. sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-functionapp
  2. sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-ad-functionapp
    (below will be available if BAM module is configured)
  3. sl360bam-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-fnapp
  4. sl360bamprocessor-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-fnapp

An upgrade is initiated when you set the value of FUNCTIONS_EXTENSION_VERSION app setting to ~4 in the above list of Function apps.


In addition to updating the FUNCTIONS_EXTENSION_VERSION, a new app setting AzureFunctionsWebHost__hostid need to be added with the following values.

  1. sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-functionapp - processor
  2. sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-ad-functionapp - documenter
    (below will be available if BAM module is configured)
  3. sl360bam-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-fnapp - bam
  4. sl360bamprocessor-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-fnapp - bamprocessor


Finally, the following setting need to be added in the Function apps

Key Value


The Function app sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-ad-cg-functionapp requires no action as it is in version 1, and it is supported for long run.

Breaking changes in 2.0.0

Serverless360 installation includes deployment of Azure Web apps in customers' Azure subscriptions. Serverless360s' architecture consisted of two Web apps up to version 1.9.0. To decrease the overhead and increase the maintainability starting from version 2.0.0 only one Web app will be used.

Below is the Web app for which the configuration needs to be updated,

  • sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-frontend-webapp

  • In the Azure portal open the Web app sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-backend-webapp and navigate to the Configuration under Settings from the left menu.

  • Under the Application settings section click on the Advanced edit button and copy its content. Replace the copied content into the Application settings of sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-frontend-webapp.

  • Similarly, under the Connection strings section click on the Advanced edit button and copy its content. Paste the copied content into the Connection strings of sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-frontend-webapp.


Proceed with the upgrade from the Serverless360 installer and after the successful completion follow the below steps.

  • The application setting WEBSITE_RUN_FROM_PACKAGE in the (sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-frontend-webapp) Web app needs to be updated.

  • Open the Storage Account named sl360xxxxxxxxxxxx and navigate to the container named packages. Then generate the SAS URL for the blob Kovai.SL360.Web.zip. (Set the expiration time to a longer period for the SAS URL. Eg. more than 2 years).


  • Update the application setting of the Web app WEBSITE_RUN_FROM_PACKAGE with the SAS URL.


  • The Web app sl360-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-backend-webapp will not be used going forward and can be deleted.

Was this article helpful?