Skip to content

Commit 00ba2b7

Browse files
authored
Clarity edits
1 parent 2fcb6ac commit 00ba2b7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/logic-apps/logic-apps-enterprise-integration-maps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ This article shows how to add a map to your integration account. If you're worki
5050

5151
* If you already have an integration account with the artifacts that you need or want to use, you can link your integration account to multiple Standard logic app resources where you want to use the artifacts. That way, you don't have to upload maps to each individual logic app. For more information, review [Link your logic app resource to your integration account](logic-apps-enterprise-integration-create-integration-account.md?tabs=standard#link-account).
5252

53-
* The **Liquid** built-in connector lets you select a map that you previously uploaded to your logic app resource or to a linked integration account, but not both. You can then use this artifact across all child workflows within the same logic app resource.
53+
* The **Liquid** built-in connector lets you select a map that you previously uploaded to your logic app resource or to a linked integration account, but not both.
5454

5555
So, if you don't have or need an integration account, you can use the upload option. Otherwise, you can use the linking option. Either way, you can use these artifacts across all child workflows within the same logic app resource.
5656

0 commit comments

Comments
 (0)