Skip to content

Commit 21f4142

Browse files
committed
Fixing links
1 parent a7d5a6b commit 21f4142

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/automation-runbook-execution.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ When runbooks are designed to authenticate and run against resources in Azure, t
3737
You can also use a [Hybrid Runbook Worker](automation-hybrid-runbook-worker.md) to run runbooks directly on the computer that hosts the role and against local resources in the environment. Azure Automation stores and manages runbooks and then delivers them to one or more assigned computers.
3838

3939
>[!NOTE]
40-
>To run on a Linux Hybrid Runbook Worker, your scripts must be signed and the worker configured accordingly. Alternatively, [signature validation must be turned off](automation-linux-hrw-install#turn-off-signature-validation).
40+
>To run on a Linux Hybrid Runbook Worker, your scripts must be signed and the worker configured accordingly. Alternatively, [signature validation must be turned off](automation-linux-hrw-install.md#turn-off-signature-validation).
4141
4242
The following table lists some runbook execution tasks with the recommended execution environment listed for each.
4343

@@ -103,7 +103,7 @@ The logs available for the Log Analytics agent and the **nxautomation** account
103103
104104
## Runbook permissions
105105

106-
A runbook needs permissions for authentication to Azure, through credentials. See [Manage Azure Automation Run As accounts](https://docs.microsoft.com/en-us/azure/automation/manage-runas-account).
106+
A runbook needs permissions for authentication to Azure, through credentials. See [Manage Azure Automation Run As accounts](manage-runas-account.md).
107107

108108
## Modules
109109

0 commit comments

Comments
 (0)