Skip to content

Commit b470cda

Browse files
committed
Fixing links
1 parent 9582465 commit b470cda

File tree

3 files changed

+3
-5
lines changed

3 files changed

+3
-5
lines changed

articles/automation/automation-runbook-gallery.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.topic: conceptual
88
---
99
# Runbook and module galleries for Azure Automation
1010

11-
Rather than creating your own runbooks and modules in Azure Automation, you can access scenarios that have already been built by Microsoft and the community. You can get PowerShell runbooks and [modules](#modules-in-powershell-gallery) from the PowerShell Gallery and [Python runbooks](#python-runbooks) from the Script Center Gallery. You can also contribute to the community by sharing [scenarios that you develop](#add-a-powershell-runbook-to-the-gallery).
11+
Rather than creating your own runbooks and modules in Azure Automation, you can access scenarios that have already been built by Microsoft and the community. You can get PowerShell runbooks and [modules](#modules-in-powershell-gallery) from the PowerShell Gallery and [Python runbooks](#use-python-runbooks) from the Script Center Gallery. You can also contribute to the community by sharing [scenarios that you develop](#add-a-powershell-runbook-to-the-gallery).
1212

1313
## Runbooks in PowerShell Gallery
1414

@@ -56,8 +56,6 @@ The list below contains a few runbooks that provide solutions to common scenario
5656

5757
Microsoft encourages you to add runbooks to the PowerShell Gallery that you think would be useful to other customers. The PowerShell Gallery accepts PowerShell modules and PowerShell scripts. You can add a runbook by [uploading it to the PowerShell Gallery](/powershell/scripting/gallery/how-to/publishing-packages/publishing-a-package).
5858

59-
60-
6159
## Import a module from the module gallery with the Azure portal
6260

6361
1. In the Azure portal, open your Automation account.

articles/automation/automation-update-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ VMs that were created from the on-demand Red Hat Enterprise Linux (RHEL) images
121121

122122
## Permissions
123123

124-
To create and manage update deployments, you need specific permissions. To learn about these permissions, see [Role-based access – Update Management](automation-role-based-access-control.md#update-management).
124+
To create and manage update deployments, you need specific permissions. To learn about these permissions, see [Role-based access – Update Management](automation-role-based-access-control.md#update-management-permissions).
125125

126126
## Solution components
127127

articles/automation/troubleshoot/onboarding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ This error is caused by incorrect or missing permissions on the virtual machine,
6969

7070
#### Resolution
7171

72-
Ensure you have correct permissions to onboard the virtual machine. Review the [permissions needed to onboard machines](../automation-role-based-access-control.md#onboarding) and try to onboard the solution again. If you receive the error `The solution cannot be enabled on this VM because the permission to read the workspace is missing`, ensure you have the `Microsoft.OperationalInsights/workspaces/read` permission to be able to find if the VM is onboarded to a workspace.
72+
Ensure you have correct permissions to onboard the virtual machine. Review the [permissions needed to onboard machines](../automation-role-based-access-control.md#onboarding-permissions) and try to onboard the solution again. If you receive the error `The solution cannot be enabled on this VM because the permission to read the workspace is missing`, ensure that you have the `Microsoft.OperationalInsights/workspaces/read` permission to be able to find if the VM is onboarded to a workspace.
7373

7474
### <a name="diagnostic-logging"></a>Scenario: Onboarding fails with the message - Failed to configure Automation Account for diagnostic logging
7575

0 commit comments

Comments
 (0)