Azure Automation Service Management REST APIs are being retired January 30, 2020
Updated: February 11, 2020
We have extended the retirement to January 30, 2020.
Azure Service Management (ASM) REST APIs for Azure Automation will be retired and no longer supported after January 30, 2020. Azure Resource Manager, our next-generation cloud infrastructure stack, fully replaces these APIs and provides many additional benefits, including:
- Increased security with role-based access control (RBAC)
- Support for resource grouping and tags
- A streamlined deployment and management process
This only impacts APIs related to Azure Automation. For example, only the PowerShell cmdlets with “AzureAutomation” in the name are affected - the cmdlets listed here beginning with Get-AzureAutomationAccount. Only the REST APIs listed in the “Operations on Automation (classic)” are impacted. Other cmdlets in the Azure module are not impacted by this announcement.
How this will affect you:
If you’re unsure whether you’re using Service Management REST APIs, check the URI referenced in your code or service. If it’s https://management.core.windows.net, you’re using Service Management REST APIs and you should migrate to Resource Manager REST APIs.
If you’re unsure whether you’re using Service Management PowerShell cmdlets, check whether the cmdlet name includes AzureRM (for example,
Get-AzureRmAutomationAccount) or Az (for example,
Get-AzAutomationAccount). If it doesn’t include AzureRM or Az (for example,
Get-AzureAutomationAccount), you should migrate to Resource Manager PowerShell cmdlets.
Migrate any Azure Automation Service Management REST APIs and PowerShell cmdlets for Azure Automation to Resource Manager REST APIs or the latest PowerShell cmdlets by January 30, 2020, to take advantage of advanced capabilities and avoid any service disruptions.