Fix more dependencies

Author: ADOYLEMSFT

articles/automation/automation-create-standalone-account.md

@@ -107,7 +107,7 @@ When the Automation account is successfully created, several resources are autom
 
 ## Manage Automation account keys
 
-When you create an Automation account, Azure generates two 512-bit automation account access keys for that account. These keys are shared access keys that are used as registration keys for registering [DSC nodes](./automation-dsc-onboarding.md#use-dsc-metaconfiguration-to-register-hybrid-machines) as well as [Windows](./automation-windows-hrw-install.md) and [Linux](./automation-linux-hrw-install.md#manually-run-powershell-commands) Hybrid runbook workers. These keys are only used while registering DSC nodes and Hybrid workers. Existing machines configured as DSC nodes or hybrid workers won’t be affected after rotation of these keys. 
+When you create an Automation account, Azure generates two 512-bit automation account access keys for that account. These keys are shared access keys that are used as registration keys for registering [DSC nodes](./automation-dsc-onboarding.md#use-dsc-metaconfiguration-to-register-hybrid-machines) These keys are only used while registering DSC nodes. Existing machines configured as DSC nodes or hybrid workers won’t be affected after rotation of these keys. 
 
 ### View Automation account keys
 

articles/automation/automation-runbook-execution.md

@@ -37,9 +37,6 @@ You can also use a [Hybrid Runbook Worker](automation-hybrid-runbook-worker.md)
 
 Enabling the Azure Firewall on [Azure Storage](../storage/common/storage-network-security.md), [Azure Key Vault](/azure/key-vault/general/network-security), or [Azure SQL](/azure/azure-sql/database/firewall-configure) blocks access from Azure Automation runbooks for those services. Access will be blocked even when the firewall exception to allow trusted Microsoft services is enabled, as Automation isn't a part of the trusted services list. With an enabled firewall, access can only be made by using a Hybrid Runbook Worker and a [virtual network service endpoint](../virtual-network/virtual-network-service-endpoints-overview.md).
 
->[!NOTE]
->- 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).
-
 The following table lists some runbook execution tasks with the recommended execution environment listed for each.
 
 |Task|Recommendation|Notes|

articles/automation/manage-runbooks.md

@@ -366,7 +366,6 @@ To use a custom script:
 
 1. Create an Automation account.
 2. Deploy the [Hybrid Runbook Worker](automation-hybrid-runbook-worker.md) role.
-3. If on a Linux machine, you need elevated privileges. Sign in to [turn off signature checks](automation-linux-hrw-install.md#turn-off-signature-validation).
 
 ## Test a runbook
 

articles/automation/whats-new-archive.md

@@ -124,7 +124,7 @@ The script is available for download from our [GitHub repository](https://github
 
 **Type.** New feature
 
-The Hybrid Runbook Worker feature supports CentOS 8.x, REHL 8.x, and SLES 15 distributions for only process automation on Hybrid Runbook Workers. See [Supported operating systems](automation-linux-hrw-install.md#supported-linux-operating-systems) for updates to the documentation to reflect these changes.
+The Hybrid Runbook Worker feature supports CentOS 8.x, REHL 8.x, and SLES 15 distributions for only process automation on Hybrid Runbook Workers.
 
 ### Update Management and Change Tracking availability in Australia East, East Asia, West US, and Central US regions
 

articles/update-manager/migration-using-runbook-scripts.md

@@ -70,7 +70,6 @@ Migration automation runbook ignores resources that aren't onboarded to Arc. It'
  - Creates an automation variable with name AutomationAccountAzureEnvironment which will store the Azure Cloud Environment to which Automation Account belongs.
  - Creation of User Identity in the same Subscription and resource group as the Automation Account. The name of User Identity will be like *AutomationAccount_aummig_umsi*. 
  - Attaching the User Identity to the Automation Account.
- - The script assigns the following permissions to the user managed identity: [Update Management Permissions Required](../automation/automation-role-based-access-control.md#update-management-permissions).
 
 
      1. For this, the script fetches all the machines onboarded to Automation Update Management under this automation account and parse their subscription IDs to be given the required RBAC to the User Identity.