How to update my runbooks to supported runtime versions of Python and PowerShell.

Hello Silvia Baruzzo Thank you for posting your query on Microsoft Q&A platform.

Thanks for reaching out, and I completely understand the confusion and the quick start guide assumes you're already on the new Runtime Environment experience, but by default most Automation accounts still show the classic (old) experience, which is why you only see up to PowerShell 7.2 and can't find the runtime upgrade option.

Here's exactly how to proceed:

Step 1: Switch to the Runtime Environment experience.

1. Open your Automation Account in the Azure portal.
2. Go to Overview and click "Try Runtime environment experience".
3. Under Process Automation, a new blade called Runtime Environments will appear. (Modules and Python packages under Shared resources will be replaced by this.)

Reference: Manage Runtime environment and associated runbooks

Step 2 : Create a new Runtime Environment for the supported version

1. Go to Process Automation → Runtime Environments → + Create.
2. Fill in:
   • Name (letters, numbers, _ or - only)
   • Language: PowerShell or Python
   • Runtime version:
   1. For PowerShell → select 7.4
   2. For Python → select 3.10
3. Click Review + Create.

Step 3: Link your existing runbook to the new Runtime Environment.

1. Go to Automation Account → Runbooks and open the runbook currently running on PS 7.1/7.2 or Python 2.7/3.8.
2. Click Edit in portal.
3. From the Runtime environment dropdown, select the new environment you just created (only compatible ones will be listed).
4. Update the runbook code if needed for the new version.
5. Click Test pane to validate → then Publish.

Reference: Update runbook from PowerShell 7.1 to PowerShell 7.4

Please have a look into below points:

• PowerShell 7.1, 7.2 and Python 2.7, 3.8 are end-of-support by their parent products, which is why Azure Automation is asking you to migrate. The currently supported targets are PS 5.1 / 7.4 and Python 3.10.
• A single Runtime Environment can be linked to multiple runbooks, so you don't need to create one per runbook.
• Runtime Environments are supported in all public regions except Brazil Southeast and Gov clouds, if your Automation account is in either, the option will not appear.
• You can always toggle back using "Switch to Old Experience" from the Overview blade; your changes persist across both views.

Official Microsoft documentation:

• Runtime Environment overview
• Quickstart: Update runbook to a supported runtime version
• Manage Runtime environment and associated runbooks

Please give the above a try and let me know how it goes, happy to help further if you hit any issue during the migration.

If this answer helped, please consider marking it as "upvote".

Thanks,

Suchitra.

Thank you, switching to new Runtime Environment experience I'm able to see the box to update the runtime version.

I'm still not able to switch to the new version, only 7.2 is available, see screenshot.

Thank you.