Merge pull request #179054 from MikeRayMSFT/20211108-regions

Update regions in release notes, add pointers for product docs.

Author: PRMerger18

articles/azure-arc/data/overview.md

@@ -56,7 +56,10 @@ The following table describes the scenarios that are currently supported for Azu
 |---------|---------|---------|
 |East US|Available|Available
 |East US 2|Available|Available
+|West US|Available|Available
 |West US 2|Available|Available
+|West US 3|Available|Available
+|North Central US | Available | Available
 |Central US|Not available|Available
 |South Central US|Available|Available
 |UK South|Available|Available

articles/azure-arc/data/release-notes.md

@@ -63,27 +63,15 @@ The following `sql` commands now support directly connected mode:
 
 You can continue to use `AZDATA_USERNAME` and `AZDATA_PASSWORD` environment variables as before. If you only provide `AZDATA_USERNAME` and `AZDATA_PASSWORD` then the deployment uses them for both the logs and metrics dashboards.
 
-##### Region Availability
+##### Region availability
 
-- Directly connected mode is only available in the following Azure regions for this release:
+This release introduces directly connected mode availability in the following Azure regions:
 
-   - North Central US *
-   - Central US
-   - East US
-   - East US 2
-   - West US *
-   - West US 2
-   - West US 3 *
-   - UK South
-   - West Europe
-   - North Europe
-   - Australia East
-   - Southeast Asia
-   - Korea Central
-   - France Central
-
-    \* Newly added for November, 2011
+- North Central US
+- West US
+- West US 3
 
+For complete list, see [Supported regions](overview.md#supported-regions).
 
 #### Azure Arc-enabled SQL Managed Instance