Merge pull request #188941 from maud-lv/maud-sc-regions

Update concept-region-support.md

Author: Court72

articles/service-connector/concept-region-support.md

@@ -1,36 +1,50 @@
 ---
 title: Service Connector Region Support
 description: Service Connector region availability and region support list
-author: shizn
-ms.author: xshi
+author: maud-lv
+ms.author: malev
 ms.service: service-connector
 ms.topic: conceptual
-ms.date: 10/29/2021
+ms.date: 02/17/2021
 ms.custom: ignite-fall-2021, references_regions
 ---
 
-# Service Connector region support
+# Service Connector Preview region support
 
-When you create a service connection with Service Connector, the conceptual connection resource is provisioned into the same region with your compute service instance by default. This page shows the region support information and corresponding behavior of Service Connector Public Preview.
+When you create a service connection with Service Connector, the conceptual connection resource is provisioned into the same region as your compute service instance by default. This page shows the region support information and corresponding behavior of Service Connector Public Preview.
 
 ## Supported regions with regional endpoint
 
 If your compute service instance is located in one of the regions that Service Connector supports below, you can use Service Connector to create and manage service connections.
 
+- Australia East
+- East US
+- East US 2 EUAP
+- Japan East
+- North Europe
+- UK South
 - West Central US
 - West Europe
-- North Europe
-- East US
 - West US 2
 
 ## Supported regions with geographical endpoint
 
-Your compute service instance might be created in the region that Service Connector has geographical region support. It means that your service connection will be created in a different region from your compute instance. You will see an information banner about the region details when you create a service connection in this case. The region difference may impact your compliance, data residency, and data latency.
+Your compute service instance might be created in a region where Service Connector has geographical region support. It means that your service connection will be created in a different region from your compute instance. In such cases you will see a banner providing some details about the region when you create a service connection. The region difference may impact your compliance, data residency, and data latency.
+
+|Region             | Support Region|
+|-------------------|---------------|
+|Australia Central  |Australia East |
+|Australia Southeast|Australia East |
+|Central US         |West US 2      |
+|East US 2          |East US        |
+|Japan West         |Japan East     |
+|UK West            |UK South       |
+|North Central US   |East US        |
+|West US            |East US        |
+|West US 3          |West US 2      |
+|South Central US   |West US 2      |
 
-- East US 2
-- West US 3
-- South Central US
+## Regions not supported in the public preview
 
-## Not supported regions in public preview
+In regions where Service Connector isn't supported, you will still find Service Connector CLI commands and the portal node, but you won't be able to create or manage service connections. The product team is working actively to enable more regions.
 
-You can still see Service Connector CLI command or portal node in the region that Service Connector does support. But you cannot create or manage service connections in these regions. The product team is working actively to enable more regions.