App Service on Azure Stack update 6 release notes

Applies to: Azure Stack integrated systems and Azure Stack Development Kit

These release notes describe the improvements and fixes in Azure App Service on Azure Stack Update 6 and any known issues. Known issues are divided into issues directly related to the deployment, update process, and issues with the build (post-installation).


Apply the 1904 update to your Azure Stack integrated system or deploy the latest Azure Stack development kit before deploying Azure App Service 1.6.

Build reference

The App Service on Azure Stack Update 6 build number is


Refer to the Before You Get Started documentation before beginning deployment.

Before you begin the upgrade of Azure App Service on Azure Stack to 1.6:

  • Ensure all roles are Ready in the Azure App Service Administration in the Azure Stack Admin Portal

  • Back up the App Service and Master Databases:

    • AppService_Hosting;
    • AppService_Metering;
    • Master
  • Back up the Tenant App content file share

  • Syndicate the Custom Script Extension version 1.9.1 from the Marketplace

New features and fixes

Azure App Service on Azure Stack Update 6 includes the following improvements and fixes:

  • Updates to App Service Tenant, Admin, Functions portals and Kudu tools. Consistent with Azure Stack Portal SDK version.

  • Updates Azure Functions runtime to v1.0.12299.

  • Updates to core service to improve reliability and error messaging enabling easier diagnosis of common issues.

  • Updates to the following application frameworks and tools:

    • ASP.NET Core 2.2.4
    • NodeJS 10.15.2
    • Zulu OpenJDK
    • Tomcat 7.0.81
    • Tomcat 8.5.37
    • Tomcat 9.0.14
    • PHP 5.6.39
    • PHP 7.0.33
    • PHP 7.1.25
    • PHP 7.2.13
    • Updated Kudu to 81.10329.3844
  • Updates to underlying operating system of all roles:

Post-deployment Steps


If you have provided the App Service resource provider with a SQL Always On Instance you MUST add the appservice_hosting and appservice_metering databases to an availability group and synchronize the databases to prevent any loss of service in the event of a database failover.

Known issues (post-installation)

  • Workers are unable to reach file server when App Service is deployed in an existing virtual network and the file server is only available on the private network, as called out in the Azure App Service on Azure Stack deployment documentation.

If you chose to deploy into an existing virtual network and an internal IP address to connect to your file server, you must add an outbound security rule, enabling SMB traffic between the worker subnet and the file server. Go to the WorkersNsg in the Admin Portal and add an outbound security rule with the following properties:

  • Source: Any
  • Source port range: *
  • Destination: IP Addresses
  • Destination IP address range: Range of IPs for your file server
  • Destination port range: 445
  • Protocol: TCP
  • Action: Allow
  • Priority: 700
  • Name: Outbound_Allow_SMB445

Known issues for Cloud Admins operating Azure App Service on Azure Stack

Refer to the documentation in the Azure Stack 1904 Release Notes

Known issues for Tenants deploying applications on Azure App Service on Azure Stack

  • Deployment Center is greyed out

Tenants cannot yet make use of Deployment Center, which is a feature that was released in the public cloud in late 2018. Tenants can still use the standard deployment methods (FTP, Web Deploy, Git, etc.) via the portal, CLI, and PowerShell.

  • Deployment options (Classic) UX and Deployment credentials portal options not available

In order to reach the deployment options and deployment credentials user experiences in the Azure Stack deployment, tenants should access the portal using this URL format - https://portal.<region>.<FQDN>/?websitesExtension_oldvsts=true - which, for the ASDK would be https://portal.local.azurestack.external/?websitesExtension_oldvsts=true , and then navigate to their applications normally.

  • Azure Function Monitoring continually shows "Loading" in the portal

When you attempt to monitor individual Functions, in the tenant portal, you will see no invocation log, success count, or error count. To re-enable this functionality, go to your Function App, go to Platform Features, and go to Application settings. Add a new app setting - name AzureWebJobsDashboard and set the value to the same value as set in AzureWebJobsStorage. Then go to the Monitor view on your function and you will see the monitoring information.

Next steps