Skip to content

Commit d9ad676

Browse files
authored
Merge pull request #211559 from maud-lv/ml-sc-regions
Update regions
2 parents 5d5389e + 02eeee1 commit d9ad676

File tree

1 file changed

+26
-19
lines changed

1 file changed

+26
-19
lines changed

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

Lines changed: 26 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -5,49 +5,56 @@ author: maud-lv
55
ms.author: malev
66
ms.service: service-connector
77
ms.topic: conceptual
8-
ms.date: 05/03/2022
8+
ms.date: 09/19/2022
99
ms.custom: references_regions, event-tier1-build-2022
1010
---
1111

1212
# Service Connector region support
1313

14-
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.
14+
When you connect Cloud services together 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.
1515

1616
## Supported regions with regional endpoint
1717

1818
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.
1919

20+
- Australia Central
2021
- Australia East
22+
- Australia Southeast
23+
- Brazil South
2124
- Canada Central
25+
- Canada East
26+
- Central India
27+
- Central US
2228
- East Asia
2329
- East US
24-
- East US 2 EUAP
30+
- East US 2
31+
- France Central
2532
- Germany West Central
2633
- Japan East
34+
- Japan West
2735
- Korea Central
36+
- North Central US
2837
- North Europe
38+
- Norway East
39+
- South Africa North
40+
- South Central US
41+
- South India
42+
- UAE North
2943
- UK South
44+
- UK West
3045
- West Central US
3146
- West Europe
47+
- West US
3248
- West US 2
49+
- West US 3
3350

34-
## Supported regions with geographical endpoint
51+
## Regions not supported
3552

36-
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'll 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.
53+
In regions where Service Connector isn't supported, you will still find Service Connector in the Azure portal and the Service Connector commands will appear in the Azure CLI, but you won't be able to create or manage service connections. The product team is working actively to enable more regions.
3754

38-
|Region | Support Region|
39-
|-------------------|---------------|
40-
|Australia Central |Australia East |
41-
|Australia Southeast|Australia East |
42-
|Central US |West US 2 |
43-
|East US 2 |East US |
44-
|Japan West |Japan East |
45-
|UK West |UK South |
46-
|North Central US |East US |
47-
|West US |East US |
48-
|West US 3 |West US 2 |
49-
|South Central US |West US 2 |
55+
## Next steps
5056

51-
## Regions not supported
57+
Go to the concept article below to learn more about Service Connector.
5258

53-
In regions where Service Connector isn't supported, you'll 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.
59+
> [!div class="nextstepaction"]
60+
> [High availability](./concept-availability.md)

0 commit comments

Comments
 (0)