You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -67,29 +67,29 @@ The following are the current limitations and known issues with PowerShell runbo
67
67
> [!NOTE]
68
68
> Currently, PowerShell 7.4 runtime version is supported for both Cloud and Hybrid jobs in all Public regions except Brazil Southeast and Gov clouds.
69
69
70
-
- For the PowerShell 7.4 runtime version, the module activities aren't extracted for the imported modules. Use Azure Automation extension for VS Code to simplify runbook authoring experience.
70
+
- For the PowerShell 7.4 runtime version, the module activities aren't extracted for the imported modules. Use [Azure Automation extension for VS Code](automation-runbook-authoring.md) to simplify runbook authoring experience.
71
71
- PowerShell 7.x doesn't support workflows. For more information, see [PowerShell workflow](/powershell/scripting/whats-new/differences-from-windows-powershell#powershell-workflow) for more details.
72
72
- PowerShell 7.x currently doesn't support signed runbooks.
73
73
- Source control integration doesn't support PowerShell 7.4. Also, PowerShell 7.4 runbooks in source control get created in Automation account as Runtime 5.1.
74
74
- Az module 12.3.0 is installed by default. The complete list of component modules of selected Az module version is shown once Az version is configured again using Azure portal or API.
75
75
- The imported PowerShell 7.4 module would be validated during job execution. Ensure that all dependencies for the selected module are also imported for successful job execution.
76
-
- Azure runbook doesn't support Start-Job with -credential.
77
-
- Azure doesn't support all PowerShell input parameters. Learn more.
76
+
- Azure runbook doesn't support `Start-Job` with `-credential`.
77
+
- Azure doesn't support all PowerShell input parameters. [Learn more](runbook-input-parameters.md).
78
78
79
79
**Known issues**
80
80
81
-
- Runbooks taking dependency on internal file paths such as `C:\modules` might fail due to changes in service backend infrastructure. Change runbook code to ensure there are no dependencies on internal file paths and use `Get-ChildItem` to get the required module information.
82
-
-`Get-AzStorageAccount` cmdlet might fail with an error: The `Get-AzStorageAccount` command was found in the module `Az.Storage`, but the module could not be loaded.
83
-
- Executing child scripts using `.\child-runbook.ps1` is not supported.
84
-
**Workaround**: Use `Start-AutomationRunbook` (internal cmdlet) or `Start-AzAutomationRunbook` (from Az.Automation module) to start another runbook from parent runbook.
81
+
- Runbooks taking dependency on internal file paths such as `C:\modules` might fail due to changes in service backend infrastructure. Change runbook code to ensure there are no dependencies on internal file paths and use [Get-ChildItem](/powershell/module/microsoft.powershell.management/get-childitem?view=powershell-7.3&preserve-view=true) to get the required module information.
82
+
-`Get-AzStorageAccount` cmdlet might fail with an error: *The `Get-AzStorageAccount` command was found in the module `Az.Storage`, but the module could not be loaded*.
83
+
- Executing child scripts using `.\child-runbook.ps1` is not supported.</br>
84
+
**Workaround**: Use `Start-AutomationRunbook` (internal cmdlet) or `Start-AzAutomationRunbook` (from *Az.Automation* module) to start another runbook from parent runbook.
85
85
- When you use [ExchangeOnlineManagement](/powershell/exchange/exchange-online-powershell?view=exchange-ps&preserve-view=true) module version: 3.0.0 or higher, you can experience errors. To resolve the issue, ensure that you explicitly upload [PowerShellGet](/powershell/module/powershellget/) and [PackageManagement](/powershell/module/packagemanagement/) modules.
86
86
- When you utilize the `New-AzAutomationVariable` cmdlet within Az.Automation Module to upload a variable of type **object**, the operation doesn't function as expected.
87
87
**Workaround**: Convert the object to a JSON string using the ConvertTo-Json cmdlet and then upload the variable with the JSON string as its value. This workaround ensures proper handling of the variable within the Azure Automation environment as a JSON string.
88
88
89
89
**Example** - Create a PowerShell object that has stored information around Azure VMs
90
90
91
91
```
92
-
Azure PowerShellCopy
92
+
azurepowershell
93
93
94
94
# Retrieve Azure virtual machines with status information for the 'northeurope' region
@@ -114,7 +114,7 @@ The following are the current limitations and known issues with PowerShell runbo
114
114
> [!NOTE]
115
115
> PowerShell 7.2 version is no longer supported by parent product PowerShell.
116
116
117
-
- For the PowerShell 7.2 runtime version, the module activities aren't extracted for the imported modules. Use [Azure Automation extension for VS Code](automation-runbook-authoring.md) to simplify runbook authoring experience.
117
+
- For the PowerShell 7.2 runtime version, the module activities aren't extracted for the imported modules.
118
118
- PowerShell 7.x doesn't support workflows. For more information, see [PowerShell workflow](/powershell/scripting/whats-new/differences-from-windows-powershell#powershell-workflow) for more details.
119
119
- PowerShell 7.x currently doesn't support signed runbooks.
120
120
- Source control integration doesn't support PowerShell 7.2. Also, PowerShell 7.2 runbooks in source control get created in Automation account as Runtime 5.1.
@@ -261,7 +261,7 @@ The following are the current limitations and known issues with PowerShell runbo
261
261
- Executing child scripts using `.\child-runbook.ps1` isn't supported in this preview.
262
262
**Workaround**: Use `Start-AutomationRunbook` (internal cmdlet) or `Start-AzAutomationRunbook` (from `Az.Automation` module) to start another runbook from parent runbook.
To list all the Runtime environments from the Automation account, follow these steps:
151
+
To list all the Runtime environments from the Automation account, follow this step:
144
152
145
153
1. In your Automation account, under **Process Automation**, select **Runtime Environments**.
146
154
@@ -205,7 +213,7 @@ To update a Runtime environment, follow these steps:
205
213
206
214
#### [REST API](#tab/update-runtime-rest)
207
215
208
-
Update the Az module version of an existing Runtime environment:
216
+
Update the Az module version of an existing Runtime environment.
209
217
210
218
```rest
211
219
PATCH
@@ -240,7 +248,7 @@ To create a new runbook linked to the Runtime environment, follow these steps:
240
248
241
249
1. In your Automation account, under **Process Automation**, select **Runbooks**.
242
250
1. Select **Create**.
243
-
1.In the **Basics** tab, you can either create a new runbook or upload a file from your local computer or from PowerShell gallery.
251
+
1.On the **Basics** tab, you can either create a new runbook or upload a file from your local computer or from PowerShell gallery.
244
252
1. Enter a **Name** for the runbook. It must begin with a letter and can contain only letters, numbers, underscores, and dashes.
245
253
1. From the **Runbook type** dropdown, select the type of runbook that you want to create.
246
254
1. Select **Runtime environment** to be configured for the runbook. You can either **Select from existing** Runtime environments or **Create new** Runtime environment and link it to the Runbook. The list of runtime environments is populated based on the *Runbook type* selected in step b.
@@ -38,14 +38,14 @@ To create Runtime environment in Azure portal, follow these steps:
38
38
1. Enter appropriate **Description**.
39
39
1. On the **Packages** tab, in the **Package version** dropdown list, you would see **Az version 12.3.0** and **Azure CLI version 2.64.0** already present.
40
40
1. Select **+Add from gallery** to add more packages from gallery and select **Next**.
41
-
1. On **Review + create** tab, review the entries and select **Create**.
41
+
1. On the **Review + create** tab, review the entries and select **Create**.
42
42
43
43
A notification appears to confirm that a Runtime environment is successfully created.
44
44
45
45
46
46
#### [REST API](#tab/create-runtime-env-rest)
47
47
48
-
Azure CLI version 2.56.0 is available only for PowerShell 7.2 Runtime environment.
48
+
49
49
50
50
```rest
51
51
PUT
@@ -83,13 +83,13 @@ To create a runbook, follow these steps:
83
83
1. Enter appropriate **Description**.
84
84
85
85
86
-
1. Add runbook code on the **Edit Runbook page** and select **Save**.
86
+
1. Add runbook code on the **Edit Runbook** page and select **Save**.
87
87
88
88
1.**Test** runbook execution in Test pane. After you confirm the results, select **Publish** to publish the runbook and execute it.
89
89
90
90
#### [REST API](#tab/create-runbook-rest)
91
91
92
-
You can create runbooks and link with PowerShell 7.2 Runtime environment.
Copy file name to clipboardExpand all lines: articles/automation/whats-new.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Significant updates to Azure Automation updated each month.
4
4
services: automation
5
5
ms.subservice:
6
6
ms.topic: overview
7
-
ms.date: 02/01/2025
7
+
ms.date: 06/27/2025
8
8
ms.custom: references_regions
9
9
ms.author: v-jasmineme
10
10
author: jasminemehndir
@@ -29,7 +29,7 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
29
29
30
30
Azure Automation announces General Availability of PowerShell 7.4 and Python 3.10 runbooks in all Public regions except Brazil southeast and Gov clouds. PowerShell 7.1 and 7.2 versions and Python 2.7 and 3.8 versions are announced retired by parent products PowerShell and Python respectively, and hence not recommended. [Learn more](automation-runbook-types.md).
31
31
32
-
### General Availability: Azure Automation Runtime environment and support for Azure CLI commands in runbooks.
32
+
### General Availability: Azure Automation Runtime environment
33
33
34
34
Azure Automation announces General Availability of [Runtime Environment](runtime-environment-overview.md) in all Public regions except Brazil southeast and Gov clouds. You can seamlessly [update](quickstart-update-runbook-in-runtime-environment.md) your outdated PowerShell 7.1, PowerShell 7.2, Python 2.7 and Python 3.8 runbooks to latest runtime versions, thereby enhancing security. This feature provides complete control to configure the script execution environment, without worrying about conflicting module versions in a single Automation account. All existing runbooks are automatically available in the new Runtime environment experience with zero manual effort. [Learn more](manage-runtime-environment.md).
0 commit comments