Skip to content

Commit c4ddaa3

Browse files
committed
fixed links
1 parent ec52a1f commit c4ddaa3

File tree

1 file changed

+22
-22
lines changed

1 file changed

+22
-22
lines changed

articles/automation/learn/automation-tutorial-runbook-graphical.md

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -10,23 +10,23 @@ ms.topic: conceptual
1010
# Tutorial: My first graphical runbook
1111

1212
> [!div class="op_single_selector"]
13-
> * [Graphical](automation-first-runbook-graphical.md)
14-
> * [PowerShell](automation-first-runbook-textual-powershell.md)
15-
> * [PowerShell Workflow](automation-first-runbook-textual.md)
16-
> * [Python](automation-first-runbook-textual-python2.md)
13+
> * [Graphical](automation-tutorial-runbook-graphical.md)
14+
> * [PowerShell](automation-tutorial-runbook-textual-powershell.md)
15+
> * [PowerShell Workflow](automation-tutorial-runbook-textual.md)
16+
> * [Python](automation-tutorial-runbook-textual-python2.md)
1717
>
1818
19-
This tutorial walks you through the creation of a [graphical runbook](automation-runbook-types.md#graphical-runbooks) in Azure Automation. Start with a simple runbook that you can test and publish, while learning how to track the status of the runbook job. Then modify the runbook to actually manage Azure resources, in this case starting an Azure virtual machine. Complete the tutorial to make the runbook more robust by adding runbook parameters and conditional links.
19+
This tutorial walks you through the creation of a [graphical runbook](../automation-runbook-types.md#graphical-runbooks) in Azure Automation. Start with a simple runbook that you can test and publish, while learning how to track the status of the runbook job. Then modify the runbook to actually manage Azure resources, in this case starting an Azure virtual machine. Complete the tutorial to make the runbook more robust by adding runbook parameters and conditional links.
2020

2121
>[!NOTE]
22-
>This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](automation-update-azure-modules.md).
22+
>This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md).
2323
2424
## Prerequisites
2525

2626
To complete this tutorial, you need the following:
2727

2828
* Azure subscription. If you don't have one yet, you can [activate your MSDN subscriber benefits](https://azure.microsoft.com/pricing/member-offers/msdn-benefits-details/) or sign up for a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
29-
* [Automation account](automation-offering-get-started.md) to hold the runbook and authenticate to Azure resources. This account must have permission to start and stop the virtual machine.
29+
* [Automation account](../automation-offering-get-started.md) to hold the runbook and authenticate to Azure resources. This account must have permission to start and stop the virtual machine.
3030
* An Azure virtual machine. Since you stop and start this machine, it shouldn't be a production VM.
3131

3232
## Step 1 - Create runbook
@@ -43,15 +43,15 @@ Start by creating a simple runbook that outputs the text `Hello World`.
4343

4444
4. Give the runbook the name **MyFirstRunbook-Graphical**.
4545

46-
5. In this case, you're going to create a [graphical runbook](automation-graphical-authoring-intro.md). Select **Graphical** for **Runbook type**.<br> ![New runbook](media/automation-tutorial-runbook-graphical/create-new-runbook.png)<br>
46+
5. In this case, you're going to create a [graphical runbook](../automation-graphical-authoring-intro.md). Select **Graphical** for **Runbook type**.<br> ![New runbook](../media/automation-tutorial-runbook-graphical/create-new-runbook.png)<br>
4747

4848
6. Click **Create** to create the runbook and open the graphical editor.
4949

5050
## Step 2 - Add activities
5151

5252
The Library control on the left side of the editor allows you to select activities to add to your runbook. You're going to add a `Write-Output` cmdlet to output text from the runbook.
5353

54-
1. In the Library control, click in the search field and type `write-output`. Search results are shown in the following image. <br> ![Microsoft.PowerShell.Utility](media/automation-tutorial-runbook-graphical/search-powershell-cmdlet-writeoutput.png)
54+
1. In the Library control, click in the search field and type `write-output`. Search results are shown in the following image. <br> ![Microsoft.PowerShell.Utility](../media/automation-tutorial-runbook-graphical/search-powershell-cmdlet-writeoutput.png)
5555

5656
2. Scroll down to the bottom of the list. Right-click **Write-Output** and select **Add to canvas**. Alternatively, you can click the ellipsis (...) next to the cmdlet name and then select **Add to canvas**.
5757

@@ -81,13 +81,13 @@ Before you publish the runbook to make it available in production, you should te
8181

8282
2. Click **Start** to start the test. This should be the only enabled option.
8383

84-
3. Note that a [runbook job](automation-runbook-execution.md) is created and its status is displayed in the pane.
84+
3. Note that a [runbook job](../automation-runbook-execution.md) is created and its status is displayed in the pane.
8585

8686
The job status starts as `Queued`, indicating that the job is waiting for a runbook worker in the cloud to become available. The status changes to `Starting` when a worker claims the job. Finally, the status becomes `Running` when the runbook actually starts to run.
8787

8888
4. When the runbook job completes, the Test pane displays its output. In this case, you see `Hello World`.
8989

90-
![Hello World](media/automation-tutorial-runbook-graphical/runbook-test-results.png)
90+
![Hello World](../media/automation-tutorial-runbook-graphical/runbook-test-results.png)
9191

9292
5. Close the Test pane to return to the canvas.
9393

@@ -159,15 +159,15 @@ Now that you have a variable to hold the subscription ID, you can configure the
159159

160160
6. Add `Connect-AzAccount` to the canvas.
161161

162-
7. 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> ![Create link between activities](media/automation-tutorial-runbook-graphical/runbook-link-auth-activities.png)
162+
7. 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> ![Create link between activities](../media/automation-tutorial-runbook-graphical/runbook-link-auth-activities.png)
163163

164164
8. On the canvas, select `Connect-AzAccount`. In the Configuration control pane, type **Login to Azure** in the **Label** field.
165165

166166
9. Click **Parameters**, and the Activity Parameter Configuration page appears.
167167

168168
10. 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**.
169169

170-
11. The parameters for this parameter set are displayed on the Activity Parameter Configuration page. Click **APPLICATIONID**.<br> ![Add Azure account parameters](media/automation-tutorial-runbook-graphical/Add-AzureRmAccount-params.png)
170+
11. The parameters for this parameter set are displayed on the Activity Parameter Configuration page. Click **APPLICATIONID**.<br> ![Add Azure account parameters](../media/automation-tutorial-runbook-graphical/Add-AzureRmAccount-params.png)
171171

172172
12. On the Parameter Value page, make the following settings and then click **OK**.
173173

@@ -205,7 +205,7 @@ Now that you have a variable to hold the subscription ID, you can configure the
205205

206206
23. Hover over `Login to Azure` until a circle appears on the bottom of the shape. Click the circle and drag the arrow to `Specify Subscription Id`. Your runbook should look like the following at this point.
207207

208-
![Runbook authentication configuration](media/automation-tutorial-runbook-graphical/runbook-auth-config.png)
208+
![Runbook authentication configuration](../media/automation-tutorial-runbook-graphical/runbook-auth-config.png)
209209

210210
## Step 7 - Add activity to start a virtual machine
211211

@@ -229,7 +229,7 @@ Now you must add a `Start-AzVM` activity to start a virtual machine. You can pic
229229

230230
9. Click **Start** to begin the test. Once it completes, make sure that the VM has started. Your runbook should look like the following at this point.
231231

232-
![Runbook authentication configuration](media/automation-tutorial-runbook-graphical/runbook-startvm.png)
232+
![Runbook authentication configuration](../media/automation-tutorial-runbook-graphical/runbook-startvm.png)
233233

234234
## Step 8 - Add additional input parameters
235235

@@ -244,13 +244,13 @@ Your runbook currently starts the VM in the resource group that you specified fo
244244
* **Type** -- keep the string setting.
245245
* **Mandatory** -- change the value to **Yes**.
246246

247-
4. Create a second mandatory input parameter called `ResourceGroupName` and then click **OK** to close the Input and Output pane.<br> ![Runbook Input Parameters](media/automation-tutorial-runbook-graphical/start-azurermvm-params-outputs.png)
247+
4. Create a second mandatory input parameter called `ResourceGroupName` and then click **OK** to close the Input and Output pane.<br> ![Runbook Input Parameters](../media/automation-tutorial-runbook-graphical/start-azurermvm-params-outputs.png)
248248

249249
5. Select the `Start-AzVM` activity and then click **Parameters**.
250250

251251
6. Change the **Data source** field for **Name** to **Runbook input**. Then select **VMName**.
252252

253-
7. Change the **Data source** field for **ResourceGroupName** to **Runbook input** and then select **ResourceGroupName**.<br> ![Start-AzVM Parameters](media/automation-tutorial-runbook-graphical/start-azurermvm-params-runbookinput.png)
253+
7. Change the **Data source** field for **ResourceGroupName** to **Runbook input** and then select **ResourceGroupName**.<br> ![Start-AzVM Parameters](../media/automation-tutorial-runbook-graphical/start-azurermvm-params-runbookinput.png)
254254

255255
8. Save the runbook and open the Test pane. You can now provide values for the two input variables that you use in the test.
256256

@@ -311,7 +311,7 @@ You can now modify the runbook so that it only attempts to start the VM if it is
311311
312312
16. Create a link from `Get Status` to `Start-AzVM`.
313313
314-
![Runbook with Code Module](media/automation-tutorial-runbook-graphical/runbook-startvm-get-status.png)
314+
![Runbook with Code Module](../media/automation-tutorial-runbook-graphical/runbook-startvm-get-status.png)
315315
316316
17. Select the link and, in the Configuration pane, change **Apply condition** to **Yes**. Note that the link becomes a dashed line, indicating that the target activity only runs if the condition resolves to true.
317317
@@ -339,16 +339,16 @@ You can now modify the runbook so that it only attempts to start the VM if it is
339339
340340
29. For the **Condition expression** field, type `$ActivityOutput['Start-AzVM'].IsSuccessStatusCode -ne $true`. This `Write-Output` control now only runs if the VM is not successfully started. Your runbook should look like the following image.
341341
342-
![Runbook with Write-Output](media/automation-tutorial-runbook-graphical/runbook-startazurermvm-complete.png)
342+
![Runbook with Write-Output](../media/automation-tutorial-runbook-graphical/runbook-startazurermvm-complete.png)
343343
344344
30. Save the runbook and open the Test pane.
345345
346346
31. Start the runbook with the VM stopped, and the machine should start.
347347
348348
## Next steps
349349
350-
* To learn more about graphical authoring, see [Graphical authoring in Azure Automation](automation-graphical-authoring-intro.md).
351-
* To get started with PowerShell runbooks, see [My first PowerShell runbook](automation-first-runbook-textual-powershell.md).
352-
* To get started with PowerShell Workflow runbooks, see [My first PowerShell workflow runbook](automation-first-runbook-textual.md).
350+
* To learn more about graphical authoring, see [Graphical authoring in Azure Automation](../automation-graphical-authoring-intro.md).
351+
* To get started with PowerShell runbooks, see [My first PowerShell runbook](automation-tutorial-runbook-textual-powershell.md).
352+
* To get started with PowerShell Workflow runbooks, see [My first PowerShell workflow runbook](automation-tutorial-runbook-textual.md).
353353
* For a PowerShell cmdlet reference, see [Az.Automation](https://docs.microsoft.com/powershell/module/az.automation/?view=azps-3.7.0#automation
354354
).

0 commit comments

Comments
 (0)