Merge branch 'main' into release-dallas

Author: v-alje

.github/workflows/stale.yml

@@ -20,21 +20,17 @@ jobs:
         exempt-pr-labels: keep-open
         stale-pr-message: >
           This pull request has been inactive for 14 days.
-          If you are finished with your changes, don't forget to sign off. See the [contributor guide](https://review.docs.microsoft.com/en-us/help/contribute/contribute-how-to-write-pull-request-automation) for instructions.
+          If you are finished with your changes, don't forget to sign off. See the [contributor guide](https://review.docs.microsoft.com/help/contribute/contribute-how-to-write-pull-request-automation?branch=main) for instructions.
           If this PR is inactive for 14 more days, it will be closed automatically. Thank you!
           
-          SQL Docs Team
+          SQL Docs Team: [Contact Us](mailto:rogue1@microsoft.com)
           
-          [Contact Us](mailto:rogue1@microsoft.com)
-          
-          [Contributor Guide](https://review.docs.microsoft.com/en-us/help/contribute/sql-server-docs-contribute?branch=master)
+          [Contributor Guide](https://review.docs.microsoft.com/en-us/help/contribute/sql-server-docs-contribute?branch=main)
         close-pr-message: >
           This pull request has been inactive for 28 days. At this time, we are closing the PR. 
           If you decide to continue working on your change, you can reopen the PR and continue working. Thank you!
            
-          SQL Docs Team
-          
-          [Contact Us](mailto:rogue1@microsoft.com)
+          SQL Docs Team: [Contact Us](mailto:rogue1@microsoft.com)
           
-          [Contributor Guide](https://review.docs.microsoft.com/en-us/help/contribute/sql-server-docs-contribute?branch=master)
+          [Contributor Guide](https://review.docs.microsoft.com/en-us/help/contribute/sql-server-docs-contribute?branch=main)
         

azure-sql/database/media/sql-vulnerability-assessment/view-additional-findings-link.png

@@ -73,7 +73,7 @@ Take the following steps to configure the vulnerability assessment:
 
     1. From the resource's **Defender for Cloud** page, select **View additional findings in Vulnerability Assessment** to access the scan results from previous scans.
 
-        :::image type="content" source="media/sql-vulnerability-assessment/view-additional-findings-link.png" alt-text="Opening the scan results and manual scan options":::   
+        :::image type="content" source="media/sql-vulnerability-assessment/view-additional-findings-link.png" alt-text="Opening the scan results and manual scan options.":::
 
     1. To run an on-demand scan to scan your database for vulnerabilities, select **Scan** from the toolbar:
 
@@ -88,7 +88,7 @@ Take the following steps to configure the vulnerability assessment:
 When a vulnerability scan completes, the report is displayed in the Azure portal. The report presents:
 
 - An overview of your security state
-- The number of issues that were found, and
+- The number of issues that were found
 - A summary by severity of the risks
 - A list of the findings for further investigations
 
@@ -125,7 +125,8 @@ Select **Scan History** in the vulnerability assessment pane to view a history o
 
 If you have an organizational need to ignore a finding, rather than remediate it, you can optionally disable it. Disabled findings don't impact your secure score or generate unwanted noise.
 
-When a finding matches the criteria you've defined in your disable rules, it won't appear in the list of findings. Typical scenarios include:
+When a finding matches the criteria you've defined in your disable rules, it won't appear in the list of findings. 
+Typical scenarios may include:
 
 - Disable findings with severity below medium
 - Disable findings that are non-patchable

azure-sql/database/sql-vulnerability-assessment.md

@@ -31,7 +31,7 @@ The initial versions of Python and R are different in SQL Managed Instance and S
   | SQL Server 2017            | 3.5.2 and 3.7.2 (CU22 and later) | 3.3.3 and 3.5.2 (CU22 and later)     |
   | SQL Server 2016            | Not available                    | 3.2.2 and 3.5.2 (SP2 CU14 and later) |
 
-\* Beginning with SQL Server 2022, runtimes for R, Python, and Java, are no longer shipped or installed within SQL Setup. Instead, install your desired R and/or Python custom runtime(s) and packages. For more information, see [Install SQL Server 2022 Machine Learning Services (Python and R) on Windows](/sql/machine-learning/install/sql-machine-learning-services-windows-install-sql-2022.md).
+\* Beginning with SQL Server 2022, runtimes for R, Python, and Java, are no longer shipped or installed within SQL Setup. Instead, install your desired R and/or Python custom runtime(s) and packages. For more information, see [Install SQL Server 2022 Machine Learning Services (Python and R) on Windows](/sql/machine-learning/install/sql-machine-learning-services-windows-install-sql-2022).
 
 ## Python and R Packages
 
@@ -44,7 +44,7 @@ For more information about managing Python and R packages, see:
 
 ### Manage packages via sqlmlutils
 
-You can install binary packages with `sqlmlutils`, if you can build locally to produce a binary package as output. For examples, see [Install R packages with sqlmlutils](/sql/machine-learning/package-management/install-additional-r-packages-on-sql-server.md) or [Install Python packages with sqlmlutils](/sql/machine-learning/package-management/install-additional-python-packages-on-sql-server.md).
+You can install binary packages with `sqlmlutils`, if you can build locally to produce a binary package as output. For examples, see [Install R packages with sqlmlutils](/sql/machine-learning/package-management/install-additional-r-packages-on-sql-server) or [Install Python packages with sqlmlutils](/sql/machine-learning/package-management/install-additional-python-packages-on-sql-server).
 
 
 ## Resource governance

azure-sql/managed-instance/machine-learning-services-differences.md

@@ -33,7 +33,7 @@ Azure SQL Managed Instance must be deployed within an Azure [virtual network](/a
 > After a managed instance is created, moving the managed instance or virtual network to another resource group or subscription is not supported. 
  
 > [!IMPORTANT]
-> You can [move the instance to another subnet inside the Vnet](vnet-subnet-move-instance.md).
+> You can [move the instance to another subnet inside the Vnet](vnet-subnet-move-instance.md). Moving a managed instance from one subnet to another within the same VNET is allowed and supported. Moving a managed instance across VNET is not supported.
 
 ## Create a virtual network
 

azure-sql/managed-instance/virtual-network-subnet-create-arm-template.md

@@ -29,6 +29,7 @@ monikerRange: ">=sql-server-2016"
 ##  <a name="Prerequisites"></a> Prerequisites  
 
 -   Before adding a database that uses FILESTREAM, with or without FileTable, to an availability group, ensure that FILESTREAM is enabled on every server instance that hosts an availability replica for the availability group. For more information, see [Enable and Configure FILESTREAM](../../../relational-databases/blob/enable-and-configure-filestream.md).  
+-   On a Windows Server 2012-based failover cluster, you should apply hotfix discussed in [Can't access VNN FILESTREAM share when you use the FILESTREAM and FileTable features on a Windows Server 2012-based failover cluster](https://support.microsoft.com/topic/can-t-access-vnn-filestream-share-when-you-use-the-filestream-and-filetable-features-on-a-windows-server-2012-based-failover-cluster-55e0d990-33ec-5097-5e95-4afa145a1bfa) to access file share using Virtual Network Name (VNN). This hotfix is also available at [Microsoft Update Catalog](https://catalog.update.microsoft.com/search.aspx?q=2835620)
 
 ##  <a name="vnn"></a> Using Virtual Network Names (VNNs) for FILESTREAM and FileTable Access  
  When you enable FILESTREAM on an instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], an instance-level share is created to provide access to the FILESTREAM data. You access this share by using the computer name in the following format:  

docs/database-engine/availability-groups/windows/filestream-and-filetable-with-always-on-availability-groups-sql-server.md

@@ -2,9 +2,8 @@
 author: rwestMSFT
 ms.service: sql
 ms.topic: include
-ms.date: 04/08/2022
+ms.date: 08/12/2022
 ms.author: randolphwest
 # SQL on Azure VM version support (currently 2008, 2008 R2, 2012)
 ---
-
-[!INCLUDE [Applies to](../../includes/applies-md.md)] ![yes](../media/yes-icon.png) [!INCLUDE [SQL Server 2008](../../includes/sskatmai-md.md)] ![yes](../media/yes-icon.png) [!INCLUDE [SQL Server 2008 R2](../../includes/sskilimanjaro-md.md)] ![yes](../media/yes-icon.png) [!INCLUDE [SQL Server 2012](../../includes/sssql11-md.md)]
+[!INCLUDE [Applies to](../../includes/applies-md.md)]  :::image type="icon" source="../media/yes-icon.svg" border="false"::: [!INCLUDE [sql2008](../sql2008-md.md)]  :::image type="icon" source="../media/yes-icon.svg" border="false"::: [!INCLUDE [sql2008r2](../sql2008r2-md.md)]  :::image type="icon" source="../media/yes-icon.svg" border="false"::: [!INCLUDE [sssql11-md](../sssql11-md.md)]