Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article explains the support and retirement policy for Azure Automation language stacks such as PowerShell and Python. It helps you understand how end-of-support is determined, the runtime retirement process, its phases, and how these changes affect existing runbooks.
Overview
Azure Automation runtime workbooks include the host component and programming language-specific workers. Language runtime support for runbooks aligns with the end-of-support for a given language. To keep your runbooks up to date and supported, Azure Automation implements a phased reduction in support as language stack versions reach their end-of-support dates. Support ends on the date that occurs first from the following:
- The community end-of-support date for the language
- The end-of-support date for the underlying base operating system
Runtime retirement process
Azure Automation uses a two-phase retirement model that provides advance notice before retired runtime versions move to reduced support.
Notification phase
Azure Automation sends notification emails for language versions approaching retirement that affect your runbooks. These notifications provide advance notice of upcoming changes, including the retirement timeline and its potential impact on existing runbooks. This notice period helps you prepare to use supported runtime versions before end-of-support.
Retirement phase
Important
If you use Azure Automation runbooks with an unsupported runtime or language version, you might encounter issues and performance impacts. Using supported runtime versions helps ensure reliability, performance, and ongoing support.
You can still create, deploy, and run runbooks and environments that use retired language versions on the platform. However, they operate in a reduced-support state. These runbooks aren't eligible for new features, security updates, or performance optimizations until they're updated to a supported language version. In certain cases, the platform might also limit the number of instances allocated to these runbooks, including restricting scaling to one instance only.
Related content
- Learn about Runtime environment in Azure Automation.
- Learn how to Manage Runtime environment and associated runbooks.
- Learn how to Manage runbooks in Azure Automation.