Merge pull request #229556 from SnehaSudhirG/06Mar-TSRunbooks

edited the cause and workaround for runbooks that don't match pattern

Author: prmerger-automator[bot]

articles/automation/troubleshoot/runbooks.md

@@ -2,7 +2,7 @@
 title: Troubleshoot Azure Automation runbook issues
 description: This article tells how to troubleshoot and resolve issues with Azure Automation runbooks.
 services: automation
-ms.date: 02/21/2023
+ms.date: 03/06/2023
 ms.topic: troubleshooting
 ms.custom: has-adal-ref, devx-track-azurepowershell
 ---
@@ -26,13 +26,12 @@ It fails with the following error:
 
 ### Cause
 
-Code that was introduced in [1.9.0 version](https://www.powershellgallery.com/packages/Az.Automation/1.9.0) of the Az.Automation module verifies the names of the runbooks to start and incorrectly flags runbooks with multiple "-" characters or with an "_" character in the name as invalid.
+The naming convention is not being followed. Ensure that your runbook name starts with a letter and can contain letters, numbers, underscores, and dashes. The naming convention requirements are now being enforced starting with the Az module version 1.9 through the portal and cmdlets.
 
 ### Workaround
-We recommend that you revert to [1.8.0 version](https://www.powershellgallery.com/packages/Az.Automation/1.8.0) of the module.
 
-### Resolution
-Currently, we are working to deploy a fix to address this issue.
+We recommend that you follow the runbook naming convention or revert to [1.8.0 version](https://www.powershellgallery.com/packages/Az.Automation/1.8.0) of the module where the naming convention isn't enforced.
+
 
 ## Diagnose runbook issues