Merge pull request #204531 from KrishnaG-MSFT/patch-213

(AzureCXP) Microsoft Q&A forum Question ID 918563

Author: PRMerger16

articles/automation/automation-child-runbooks.md

@@ -38,12 +38,16 @@ The parameters of a child runbook called inline can be of any data type, includi
 
 ### Runbook types
 
-Currently, PowerShell 5.1 and 7.1 (preview) are supported and only certain runbook types can call each other:
+Currently, PowerShell 5.1 is supported and only certain runbook types can call each other:
 
 * A [PowerShell runbook](automation-runbook-types.md#powershell-runbooks) and a [graphical runbook](automation-runbook-types.md#graphical-runbooks) can call each other inline, because both are PowerShell based.
 * A [PowerShell Workflow runbook](automation-runbook-types.md#powershell-workflow-runbooks) and a graphical PowerShell Workflow runbook can call each other inline, because both are PowerShell Workflow based.
 * The PowerShell types and the PowerShell Workflow types can't call each other inline. They must use `Start-AzAutomationRunbook`.
 
+> [!IMPORTANT]
+> Executing child scripts using `.\child-runbook.ps1` is not supported in PowerShell 7.1 preview. 
+  **Workaround**: Use `Start-AutomationRunbook` (internal cmdlet) or `Start-AzAutomationRunbook` (from *Az.Automation* module) to start another runbook from parent runbook.
+
 The publish order of runbooks matters only for PowerShell Workflow and graphical PowerShell Workflow runbooks.
 
 When your runbook calls a graphical or PowerShell Workflow child runbook by using inline execution, it uses the name of the runbook. The name must start with `.\\` to specify that the script is in the local directory.