Added the extension min version requirement

Author: anosov1960

docs/sql-server/azure-arc/connect-at-scale.md

@@ -25,9 +25,7 @@ You can automatically connect the SQL Server instances on multiple machines usin
 
 You can connect multiple SQL Server instances installed on multiple Windows or Linux machines to Azure Arc using the same [script your generated for a single machine](connect.md). The script will connect and connect each machine and the installed SQL Server instances on it to Azure Arc. For the best experience, we recommend using an Azure Active Directory [service principal](/azure/active-directory/develop/app-objects-and-service-principals). A service principal is a special limited management identity that is granted only the minimum permission necessary to connect machines to Azure and to create the Azure resources for Azure Arc-enabled servers. This is safer than using a higher privileged account like a Tenant Administrator, and follows our access control security best practices.  
 
-You can connect multiple SQL Server instances installed on multiple Windows or Linux machines to Azure Arc using the same [script your generated for a single machine](connect.md). The script connects each machine and the installed SQL Server instances to Azure.
-
-### Use Azure Active Directory service principal
+ ### Use Azure Active Directory service principal
 
 For the best experience, use an Azure Active Directory [service principal](/azure/active-directory/develop/app-objects-and-service-principals). A service principal is a special limited management identity that is granted only the minimum permission necessary to connect machines and SQL Server instances to Azure. The service principal is safer than using a higher privileged account like a Tenant Administrator, and follows access control security best practices.  
 

docs/sql-server/azure-arc/release-notes.md

@@ -19,7 +19,8 @@ Azure Arc-enabled SQL Server releases for general availability support
 
 This release introduces a SQL Server extension that continuously monitors for changes of the SQL Server configuration and automatically updates the corresponding __SQL Server - Azure Arc__ resources. The extension is installed as part of the SQL Server instance registration process. To upgrade your existing __SQL Server - Azure Arc__ resources to an agent-based configuration, use any of the methods described in [Connect your SQL Server to Azure Arc](connect.md).
 
-This release also introduces a built-in role *Azure Connected SQL Server Onboarding* that defines the minimal permissions that would allow the hosting machine's MSI to onboard the SQL Server instances to to Azure Arc.
+> [!IMPORTANT]
+> If you installed a version of SQL Server extension during the preview, make sure it is updated to version 1.1.1668.43 or later. An extension can be updated using the *Extention* blade of the specific connected server resource.
 
 The introduction of SQL Server extension requires that the user accounts have more privileges in order to connect a  SQL Server instance to Azure Arc. For details, see [Required permissions](overview.md#required-permissions).  
 
@@ -28,7 +29,7 @@ The introduction of SQL Server extension requires that the user accounts have mo
 
 ### Other changes
 
-This release includes a new Azure policy _Configure SQL Server extension on Azure Arc enabled servers_. It enables automatic registration of all SQL Server instances after their hosting server is connected to Azure Arc. For details of using this policy, see [At scale registration from Azure](connect-at-scale.md#connecting-at-scale-using-azure-policy).
+This release includes a new Azure policy _Configure Arc-enabled machines running SQL Server to have SQL Server extension installed_. It enables automatic registration of all SQL Server instances after their hosting server is connected to Azure Arc. For details of using this policy, see [At scale registration from Azure](connect-at-scale.md#connecting-at-scale-using-azure-policy).
 
 ## April 2021