SQL resource provider 2.0.6.x release notes

These release notes describe the improvements and known issues in SQL resource provider version 2.0.6.x.

Build reference

Starting from this release, SQL resource provider becomes a standard Azure Stack Hub value-add RP. If you want to get access to the SQL resource provider in Azure Stack Hub marketplace, open a support case to add your subscription to the allowlist.

The resource provider has a minimum corresponding Azure Stack Hub build. The minimum Azure Stack Hub release version required to install this version of the SQL resource provider is listed below.

It is required that you apply the minimum supported Azure Stack Hub update to your Azure Stack Hub integrated system before deploying the latest version of the SQL resource provider.

Supported Azure Stack Hub version SQL resource provider version
Version 2108,2206 SQL RP version


If there is an existing version of SQL resource provider running in your system, make sure to update it to version 1.1.93.x, before upgrading to this lattest version.

New features and fixes

This version of the Azure Stack Hub SQL resource provider includes the following improvements and fixes:

  • Installation and future version upgrade will be from the Azure Stack Hub marketplace.
  • A specific version of Add-on RP Windows Server will be required. The correct version of Microsoft AzureStack Add-On RP Windows Server will be automatically downloaded if you install the resource provider in connected environment. In disconnected environment, make sure the right version of Microsoft AzureStack Add-On RP Windows Server image is downloaded before deploying or upgrading to this version of the SQL resource provider.
  • Receive alerts when certifications are about to expire. Check this document for details.
  • Other bug fixes.

Known issues

After deployment or upgrade, Azure Stack Hub Operators need to manually register their default provider subscription to the tenant namespace (Microsoft.SQLAdapter) before they can create Login or Databases.

Next steps