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/automation/automation-first-runbook-graphical.md
+5-4
Original file line number
Diff line number
Diff line change
@@ -126,23 +126,24 @@ Now that you have a variable to hold the subscription ID, you can configure the
126
126
1. Hover over **Get Run As Connection** until a circle appears on the bottom of the shape. Click the circle and drag the arrow to `Connect-AzAccount` to form a link. The runbook starts with `Get Run As Connection` and then runs `Connect-AzAccount`.<br> 
127
127
1. On the canvas, select `Connect-AzAccount`. In the Configuration control pane, type **Login to Azure** in the **Label** field.
128
128
1. Click **Parameters**, and the Activity Parameter Configuration page appears.
129
-
1. The `Connect-AzAccount` cmdlet has multiple parameter sets, and you need to select one before providing parameter values. Click **Parameter Set** and then select **ServicePrincipalCertificate**.
129
+
1. The `Connect-AzAccount` cmdlet has multiple parameter sets, and you need to select one before providing parameter values. Click **Parameter Set** and then select **ServicePrincipalCertificateWithSubscriptionId**.
130
130
1. The parameters for this parameter set are displayed on the Activity Parameter Configuration page. Click **APPLICATIONID**.<br> 
131
131
1. On the Parameter Value page, make the following settings and then click **OK**.
132
132
133
133
***Data source** -- select **Activity output**.
134
-
* Data source list -- select **Get Run As Connection**.
134
+
* Data source list -- select **Get Automation Connection**.
135
135
***Field path** -- type `ApplicationId`. You are specifying the name of the property for the field path because the activity outputs an object with multiple properties.
136
+
136
137
1. Click **CERTIFICATETHUMBPRINT**, and on the Parameter Value page, make the following settings and then click **OK**.
137
138
138
139
***Data source** -- select **Activity output**.
139
-
* Data source list -- select **Get Run As Connection**.
140
+
* Data source list -- select **Get Automation Connection**.
140
141
***Field path** -- type `CertificateThumbprint`.
141
142
1. Click **SERVICEPRINCIPAL**, and on the Parameter Value page, select **ConstantValue** for the **Data source** field; click the option **True**; and then click **OK**.
142
143
1. Click **TENANTID**, and make the following settings on the Parameter Value page. When finished, click **OK** twice.
143
144
144
145
***Data source** -- select **Activity output**.
145
-
* Data source list -- select **Get Run As Connection**.
146
+
* Data source list -- select **Get Automation Connection**.
146
147
***Field path** -- type `TenantId`.
147
148
1. In the Library control, type `Set-AzContext` in the search field.
Copy file name to clipboardExpand all lines: articles/automation/automation-graphical-authoring-intro.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ The Test control is not displayed when the graphical editor is first started. It
52
52
53
53
Activities are the building blocks of a runbook. An activity can be a PowerShell cmdlet, a child runbook, or a workflow. You can add an activity to the runbook by right-clicking it in the Library control and selecting **Add to canvas**. You can then click and drag the activity to place it anywhere on the canvas that you like. The location of the activity on the canvas does not affect the operation of the runbook. You can lay out your runbook any way you find most suitable to visualize its operation.
54
54
55
-

55
+

56
56
57
57
Select an activity on the canvas to configure its properties and parameters in the Configuration blade. You can change the label of the activity to a name that you find descriptive. The runbook still runs the original cmdlet. You are simply changing the display name that the graphical editor uses. Note that the label must be unique within the runbook.
58
58
@@ -62,7 +62,7 @@ A parameter set defines the mandatory and optional parameters that accept values
62
62
63
63
In the following example, the [Get-AzVM](https://docs.microsoft.com/powershell/module/az.compute/get-azvm?view=azps-3.5.0) cmdlet has three parameter sets. The example uses one set called **ListVirtualMachineInResourceGroupParamSet**, with a single optional parameter, for returning all virtual machines in a resource group. The example also uses the **GetVirtualMachineInResourceGroupParamSet** parameter set for specifying the virtual machine to return. This set has two mandatory parameters and one optional parameter.
@@ -146,7 +146,7 @@ A link in a graphical runbook connects two activities. It is displayed on the ca
146
146
147
147
You can create a link between two activities by selecting the source activity and clicking the circle at the bottom of the shape. Drag the arrow to the destination activity and release.
148
148
149
-

149
+

150
150
151
151
Select the link to configure its properties in the Configuration blade. Properties include the link type, which is described in the following table.
152
152
@@ -407,7 +407,7 @@ You can only export the published version of a graphical runbook. If the runbook
407
407
408
408
You can import a graphical or graphical PowerShell Workflow runbook file by selecting the **Import** option when adding a runbook. When you select the file to import, you can keep the same name or provide a new one. The **Runbook Type** field displays the type of runbook after it assesses the file selected. If you attempt to select a different type that is not correct, the graphical editor presents a message noting that there are potential conflicts and there might be syntax errors during conversion.
0 commit comments