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/logic-apps/create-parameters-workflows.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,25 +12,27 @@ ms.date: 02/03/2022
12
12
13
13
In Azure Logic Apps, you can abstract values that might change in workflows across development, test, and production environments by defining *parameters*. When you use parameters rather than environment-specific variables, you can initially focus more on designing your workflows, and insert your environment-specific variables later.
14
14
15
-
This article introduces how to create, use, and edit parameters for multi-tenant Consumption logic app workflows and for single-tenant Standard logic app workflows. You'll also learn how to manage environment variables. For more information about the differences between logic app (single-tenant-overview-compare.md).
15
+
This article introduces how to create, use, and edit parameters for multi-tenant Consumption logic app workflows and for single-tenant Standard logic app workflows. You'll also learn how to manage environment variables.
16
+
17
+
For more information about multi-tenant and single-tenant Azure Logic Apps, review [Single-tenant versus multi-tenant and integration service environment for Azure Logic Apps](single-tenant-overview-compare.md).
16
18
17
19
## Prerequisites
18
20
19
21
* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
20
22
21
23
* A Consumption or Standard logic app workflow
22
24
23
-
If you don't have a logic app workflow yet, review the following documentation:
24
-
25
-
*[Create your Consumption logic app workflow in the Azure portal] or in Visual Studio.
25
+
If you don't have a logic app workflow yet, review [Create your first Consumption logic app workflow using the Azure portal](quickstart-create-first-logic-app-workflow.md) or [Create your first Standard logic app workflow using the Azure portal](create-single-tenant-workflows-azure-portal.md).
26
26
27
-
*[Create your Standard logic app in the Azure portal](create-single-tenant-workflows-azure-portal.md) or [in Visual Studio Code](create-single-tenant-workflows-visual-studio-code.md).
27
+
> [!NOTE]
28
+
> Currently, you can create parameters for Consumption logic app workflows only by using the Azure portal.
29
+
> You can create parameters for Standard logic app workflows only by using the Azure portal or Visual Studio Code.
28
30
29
31
<aname="parameters-introduction"></a>
30
32
31
-
## Parameter differences between multi-tenant versus single-tenant
33
+
## Parameters for Consumption versus Standard logic app workflows
32
34
33
-
In both multi-tenant and single-tenant Azure Logic Apps, you can define parameters while using workflow designer. After you define the parameter, you can reference that parameter from any workflow or connection that's in the *same* logic app resource.
35
+
For both Consumption and Standard logic app workflows, you can define parameters using the designer. After you define the parameter, you can reference that parameter from any workflow or connection that's in the *same* logic app resource.
34
36
35
37
In multi-tenant Consumption logic app workflows, after you create and use parameters in the designer, you define and set the environment variables in your Azure Resource Manager template (ARM template) and template parameters files. In this scenario, you have to define and set the parameters *at deployment*, which means that even if you only have to change one variable, you have to redeploy your logic app's ARM template.
0 commit comments