Period: today · Items: 1 · Source: Azure official updates RSS
Today’s Azure updates are not extensive, but there is one fairly important signal from an operations automation perspective. There is no news about new feature releases; instead, the focus is on a runtime support policy change. At first glance, it may look like a simple announcement, but in practice it raises broader questions about how to manage the execution foundations of Runbooks and how regularly platform dependencies should be reviewed.
· Azure Automation Runtime Lifecycle — the Python/PowerShell runtimes that Automation Runbooks depend on are also subject to lifecycle management
· The difference between end of support and continued execution — “can continue running” and “is supported” are completely different, with security updates and bug fixes being the key distinction
· Runbook modernization — building an operational habit of reviewing and migrating older scripts against current PowerShell/Python versions
· Operations automation risk management — automation assets may be less visible, but they are areas where outage and security risks can easily accumulate
· Technical debt review cycles — not only infrastructure code, but also Automation runtime versions should be added to regular review checklists
1 item
· In Azure Automation, support for Python 2.7, Python 3.8, PowerShell 7.1, and 7.2 will end on September 30, 2026.
· Starting October 1, 2026, those versions will no longer receive security updates, bug fixes, or any other support.
· The wording indicates that existing Runbooks may continue to run, but this is closer in meaning to “they remain in an unsupported state after support ends.”
· From an operations perspective, the key is not “immediate disruption,” but rather putting a migration plan in place ahead of time.
· Especially for very old runtimes such as Python 2.7, this announcement is a good opportunity to review script compatibility, module dependencies, and test frameworks together.
What it is: This is a formal end-of-support announcement for specific Python/PowerShell runtime versions used by Azure Automation Runbooks. The important point is that the version of the execution engine can affect operational stability and security just as much as the workload itself.
Why it matters: Many teams tend to treat Automation as something that is “built once and left alone for a long time,” and announcements like this are a reminder that those automation assets also require ongoing management. For engineers, this is a good opportunity to go beyond simple migration and build the habit of inventorying which automations are tied to which runtimes.
Try it: In the Azure portal, open Automation Account > Runbooks and create a list of the runtime version and script language (PowerShell/Python) currently used by each Runbook.
Source: https://azure.microsoft.com/updates?id=567556