You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-connector/concept-region-support.md
+24-11Lines changed: 24 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,28 +9,41 @@ ms.date: 10/29/2021
9
9
ms.custom: ignite-fall-2021, references_regions
10
10
---
11
11
12
-
# Service Connector region support
12
+
# Service Connector Preview region support
13
13
14
-
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.
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 Public Preview.
15
15
16
16
## Supported regions with regional endpoint
17
17
18
18
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.
19
19
20
+
- Australia East
21
+
- East US
22
+
- East US 2 EUAP
23
+
- Japan East
24
+
- North Europe
25
+
- UK South
20
26
- West Central US
21
27
- West Europe
22
-
- North Europe
23
-
- East US
24
28
- West US 2
25
29
26
30
## Supported regions with geographical endpoint
27
31
28
-
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.
29
-
30
-
- East US 2
31
-
- West US 3
32
-
- South Central US
33
-
34
-
## Not supported regions in public preview
32
+
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.
33
+
34
+
|Region | Support Region|
35
+
|-------------------|---------------|
36
+
|Australia Central |Australia East |
37
+
|Australia Southeast|Australia East |
38
+
|Central US |West US 2 |
39
+
|East US 2 |East US |
40
+
|Japan West |Japan East |
41
+
|UK West |UK South |
42
+
|North Central US |East US |
43
+
|West US |East US |
44
+
|West US 3 |West US 2 |
45
+
|South Central US |West US 2 |
46
+
47
+
## Regions not supported in the public preview
35
48
36
49
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.
0 commit comments