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
@@ -357,7 +349,7 @@ To test runbook execution before publishing Runtime environment changes, follow
357
349
358
350
Run a test job for a runbook with a different Runtime environment. This scenario is useful when a runbook needs to be tested with a Runtime environment before update.
Copy file name to clipboardExpand all lines: articles/automation/runtime-environment-overview.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,6 +84,7 @@ You can't edit these Runtime environments. However, any changes that are made in
84
84
- Runtime environment can't be configured through Azure Automation extension for Visual Studio Code.
85
85
- Deleted Runtime environments cannot be recovered.
86
86
- This feature is currently supported through Azure portal and [REST API](/rest/api/automation/runtime-environments?view=rest-automation-2024-10-23&preserve-view=true).
87
+
- Use [Packages: REST API](/rest/api/automation/package?view=rest-automation-2024-10-23) to upload custom packages.
87
88
- Management of modules for Azure Automation State Configuration is not supported through Runtime environment experience. You can continue using the old experience for managing modules and packages for Azure Automation State Configuration.
0 commit comments