Azure Automation Run As accounts retiring on 30 September 2023
On 30 September 2023, Azure Automation will retire Run As accounts, and completely move to Managed identities. All runbook executions using Run As accounts, including Classic Run As accounts would not be supported after this date. Moreover, starting 1 April 2023, creation of new Run As accounts in Azure Automation will not be possible. Renewing of certificates for existing RunAs accounts would be possible only till the end of support.
To ensure you are using a supported authentication method, you must migrate all your runbooks to Managed Identities.
Benefits of Managed identities
- Secure authentication to any Azure service that supports Azure AD authentication.
- Minimised management overhead with easy access to resources.
- No need of Certificate renewals as in case of Run As accounts.
- Simplified runbooks with no requirement to use multi-line code.
Take immediate action
- Review your Automation accounts, Runbooks, GitHub code samples to identify Remove all references to Run As accounts and make necessary changes to reflect Managed Identities only.
- If you have existing Azure Automation runbooks using Run As accounts, you must migrate them to Managed identities.
- If your Run As account certificate is expiring, it’s a good time to start using Managed identities for authentication instead of renewing the certificate.
- Do not create new Run As accounts, ensure to use Managed identities.
Resources
- Migrate from a Run As account to a managed identity | Microsoft Learn
- Azure Automation migration to managed identity FAQ | Microsoft Learn
If you have questions, ask community experts in Microsoft Q&A.
Published on:
Learn moreRelated posts
How to Auto-Fill Third-Party Web Forms Using Power Automate Desktop and JavaScript
In today’s digital workflows, teams across HR, operations, finance, and support deal with repetitive manual tasks every day. One of the most c...
Announcing Azure MCP Server 1.0.0 Stable Release – A New Era for Agentic Workflows
Today marks a major milestone for agentic development on Azure: the stable release of the Azure MCP Server 1.0! The post Announcing Azure MCP ...
From Backup to Discovery: Veeam’s Search Engine Powered by Azure Cosmos DB
This article was co-authored by Zack Rossman, Staff Software Engineer, Veeam; Ashlie Martinez, Staff Software Engineer, Veeam; and James Nguye...
Azure SDK Release (October 2025)
Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (October 2025)...
Microsoft Copilot (Microsoft 365): [Copilot Extensibility] No-Code Publishing for Azure AI Foundry Agents to Microsoft 365 Copilot Agent Store
Developers can now publish Azure AI Foundry Agents directly to the Microsoft 365 Copilot Agent Store with a simplified, no-code experience. Pr...
How to Design Custom Approval Buttons in Outlook Email Using Power Automate (Step-by-Step Guide)
Microsoft’s standard approval emails make it easy to send and capture user feedback directly through Outlook. However, one major limitation is...
Azure Marketplace and AppSource: A Unified AI Apps and Agents Marketplace
The Microsoft AI Apps and Agents Marketplace is set to transform how businesses discover, purchase, and deploy AI-powered solutions. This new ...
We need to talk about... Power Automate... Licensing
Next in my blog, I am going to cover a topic that has come up several times in recent conversations with clients.....Microsoft Licensing! part...
Episode 413 – Simplifying Azure Files with a new file share-centric management model
Welcome to Episode 413 of the Microsoft Cloud IT Pro Podcast. Microsoft has introduced a new file share-centric management model for Azure Fil...