Skip to content

Commit 69837b1

Browse files
committed
added new issue, cause and resolution
1 parent 4cc3386 commit 69837b1

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

articles/automation/troubleshoot/runbooks.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Troubleshoot Azure Automation runbook issues
33
description: This article tells how to troubleshoot and resolve issues with Azure Automation runbooks.
44
services: automation
5-
ms.date: 08/18/2023
5+
ms.date: 05/08/2024
66
ms.topic: troubleshooting
77
ms.custom: has-adal-ref, devx-track-azurepowershell
88
---
@@ -12,6 +12,18 @@ ms.custom: has-adal-ref, devx-track-azurepowershell
1212
This article describes runbook issues that might occur and how to resolve them. For general information, see [Runbook execution in Azure Automation](../automation-runbook-execution.md).
1313

1414

15+
## New functions added to custom module aren't displayed in textual and graphical PowerShell runbooks.
16+
17+
### Issue
18+
After you add new functions to a custom module and reimport the module, the functions aren't getting displayed in textual and graphical PowerShell runbooks.
19+
20+
### Cause
21+
To improve the security posture of PowerShell runbooks, the service no longer installs PowerShell modules due to which functions aren't displayed on runbook edit page in textual and graphical PowerShell runbooks.
22+
23+
### Resolution
24+
There is no impact on execution of existing runbooks. Use Azure automation extension for VScode for authoring and editing PowerShell runbooks, that leverages GitHub Copilot to simplify runbook authoring experience. We recommend to use textual runbooks instead of graphical PowerShell runbooks to overcome this issue.
25+
26+
1527
## Start-AzAutomationRunbook fails with "runbookName does not match expected pattern" error message
1628

1729
### Issue

0 commit comments

Comments
 (0)