App Service on Azure Stack Hub 2020 Q3 release notes
These release notes describe the improvements and fixes in Azure App Service on Azure Stack Hub 2020 Q3 and any known issues. Known issues are divided into issues directly related to the deployment, update process, and issues with the build (post-installation).
Update Azure Stack Hub to a supported version (or deploy the latest Azure Stack Development Kit) if necessary, before deploying or updating the App Service resource provider (RP). Be sure to read the RP release notes to learn about new functionality, fixes, and any known issues that could affect your deployment.
Supported Azure Stack Hub version App Service RP version 2102 2021.Q1 Installer (release notes) 2008 2020.Q3 Installer (release notes) 2005 2020.Q2 Installer (release notes)
The App Service on Azure Stack Hub 2020 Q3 build number is 188.8.131.52
Refer to the Before You Get Started documentation before beginning deployment.
Before you begin the upgrade of Azure App Service on Azure Stack to 2020 Q3:
Ensure all roles are Ready in the Azure App Service Administration in the Azure Stack Hub Admin Portal
Backup App Service Secrets using the App Service Administration in the Azure Stack Hub Admin Portal
Back up the App Service and Master Databases:
Back up the Tenant App content file share
Cloud operators are responsible for the maintenance and operation of the File Server and SQL Server. The resource provider does not manage these resources. The cloud operator is responsible for backing up the App Service databases and tenant content file share.
Syndicate the Custom Script Extension version 1.9.3 from the Marketplace
Azure App Service on Azure Stack Update Q3 includes the following improvements and fixes:
Updates to App Service Tenant, Admin, Functions portals and Kudu tools. Consistent with Azure Stack Portal SDK version.
Addition of Full Screen Create experience for Web and Function Apps
New Azure Functions Portal Experience to be consistent with Web Apps
Updates Azure Functions runtime to v1.0.13154.
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.1.22
- ASP.NET Core 2.2.14
- ASP.NET Core 3.1.8
- ASP.NET Core Module v2 13.1.19331.0
- Azul OpenJDK
- Curl 7.55.1
- Git for Windows 184.108.40.206
- MSDeploy 3.5.90702.36
- PHP 7.4.5
- Updated Kudu to 90.21005.4823
Updates to underlying operating system of all roles:
Cumulative Updates for Windows Server are now applied to Controller roles as part of deployment and upgrade
Issues fixed in this release
Tenants can now create App Service Plan using new on App Service Plan view in tenant portal
Tenants can manage certificates for their applications in the tenant portal
Functions monitoring can now retrieve data from storage endpoints enforcing TLS 1.2
Moved wait for Management Servers step outside of Deploy Cloud step during installation to improve reliability of deployment and upgrade
Issue whereby workers fail to complete the health check exercise due to worker runtime log file folder size violating quota limit after error in clean-up logic. Clean-up logic has been fixed in this update.
Review the known issues for update and take any action prescribed.
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 (update)
- In situations where a customer has converted the appservice_hosting and appservice_metering databases to contained database, upgrade may fail if logins have not been successfully migrated to contained users
Customers that have converted the appservice_hosting and appservice_metering databases to contained database post deployment, and have not successfully migrated the database logins to contained users, may experience upgrade failures.
Customers must execute the following script against the SQL Server hosting appservice_hosting and appservice_metering before upgrading your Azure App Service on Azure Stack Hub installation to 2020 Q3. This script is non-destructive and will not cause downtime.
This script must be run under the following conditions
By a user that has the system administrator privilege, for example the SQL SA Account;
If using SQL Always on, ensure the script is run from the SQL instance that contains all App Service logins in the form:
- All WebWorker logins - which are in the form WebWorker_
USE appservice_hosting IF EXISTS(SELECT * FROM sys.databases WHERE Name=DB_NAME() AND containment = 1) BEGIN DECLARE @username sysname ; DECLARE user_cursor CURSOR FOR SELECT dp.name FROM sys.database_principals AS dp JOIN sys.server_principals AS sp ON dp.sid = sp.sid WHERE dp.authentication_type = 1 AND dp.name NOT IN ('dbo','sys','guest','INFORMATION_SCHEMA'); OPEN user_cursor FETCH NEXT FROM user_cursor INTO @username WHILE @@FETCH_STATUS = 0 BEGIN EXECUTE sp_migrate_user_to_contained @username = @username, @rename = N'copy_login_name', @disablelogin = N'do_not_disable_login'; FETCH NEXT FROM user_cursor INTO @username END CLOSE user_cursor ; DEALLOCATE user_cursor ; END GO USE appservice_metering IF EXISTS(SELECT * FROM sys.databases WHERE Name=DB_NAME() AND containment = 1) BEGIN DECLARE @username sysname ; DECLARE user_cursor CURSOR FOR SELECT dp.name FROM sys.database_principals AS dp JOIN sys.server_principals AS sp ON dp.sid = sp.sid WHERE dp.authentication_type = 1 AND dp.name NOT IN ('dbo','sys','guest','INFORMATION_SCHEMA'); OPEN user_cursor FETCH NEXT FROM user_cursor INTO @username WHILE @@FETCH_STATUS = 0 BEGIN EXECUTE sp_migrate_user_to_contained @username = @username, @rename = N'copy_login_name', @disablelogin = N'do_not_disable_login'; FETCH NEXT FROM user_cursor INTO @username END CLOSE user_cursor ; DEALLOCATE user_cursor ; END GO
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
- Custom domains are not supported in disconnected environments
App Service performs domain ownership verification against public DNS endpoints, as a result custom domains are not supported in disconnected scenarios.
- For an overview of Azure App Service, see Azure App Service on Azure Stack overview.
- For more information about how to prepare to deploy App Service on Azure Stack, see Before you get started with App Service on Azure Stack.