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
Azure DevOps Remote MCP Server (public preview)
When we released the local Azure DevOps MCP Server, it gave customers a way to connect Azure DevOps data with tools like Visual Studio and Vis...
Azure Cosmos DB at FOSSASIA Summit 2026: Sessions, Conversations, and Community
The FOSSASIA Summit 2026 was an incredible gathering of developers, open-source contributors, startups, and technology enthusiasts from across...
Dataverse: Avoid Concurrency issues by using Azure Service Bus Queue and Azure Functions
Another blog post to handle the concurrency issue. Previously, I shared how to do concurrency via a plugin in this blog post and also how to f...
March Patches for Azure DevOps Server
We are releasing patches for our self‑hosted product, Azure DevOps Server. We strongly recommend that all customers stay on the latest, most s...
Azure Developer CLI (azd): Debug hosted AI agents from your terminal
New azd ai agent show and monitor commands help you diagnose hosted AI agent failures directly from the CLI. The post Azure Developer CLI (azd...
A Look Ahead at Azure Cosmos DB Conf 2026: From AI Agents to Global Scale
Join us for Azure Cosmos DB Conf 2026, a free global, virtual developer event focused on building modern applications with Azure Cosmos DB. Da...
Announcing general availability of Azure Confidential Computing (ACC) virtual machines for U.S. government environments
Government agencies have an increased need for secure, verifiable, and compliant cloud environments that adhere to data sovereignty regulation...
What is Azure SRE Agent
Power Platform – Alerts for Microsoft Power Automate work queues is now available for public preview
We are announcing the ability to configure alerts for Microsoft Power Automate work queues from the Monitor section of the Power Platform admi...