Skip to content

Commit 6311909

Browse files
authored
Add data residency statement
1 parent f642d62 commit 6311909

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/logic-apps/single-tenant-overview-compare.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,12 @@ The **Logic App (Standard)** resource type and single-tenant Azure Logic Apps ru
6868

6969
When you use the new built-in operations, you create connections called *built-in connections* or *service provider connections*. Their managed connection counterparts are called *API connections*, which are created and run separately as Azure resources that you also have to then deploy by using ARM templates. Built-in operations and their connections run locally in the same process that runs your workflows. Both are hosted on the single-tenant Azure Logic Apps runtime. As a result, built-in operations and their connections provide better performance due to proximity with your workflows. This design also works well with deployment pipelines because the service provider connections are packaged into the same build artifact.
7070

71+
<a name="data-residency"></a>
72+
73+
### Data residency
74+
75+
Logic app resources created with the **Logic App (Standard)** resource type are hosted in single-tenant Azure Logic Apps, which [doesn't store, process, or replicate data outside the region where you deploy these logic app resources](https://azure.microsoft.com/global-infrastructure/data-residency), meaning data in your logic app workflows stay in the same region where you create and deploy their parent resources.
76+
7177
## Create, build, and deploy options
7278

7379
To create a logic app based on the environment that you want, you have multiple options, for example:

0 commit comments

Comments
 (0)