Skip to content

Commit 4e15953

Browse files
Merge pull request #298087 from SnehaSudhirG/11Apr-RunAsEdit
Info deleted for relevance
2 parents 2ca5b89 + 4a007d8 commit 4e15953

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/delete-run-as-account.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Delete an Azure Automation Run As account
33
description: This article tells how to delete a Run As account with PowerShell or from the Azure portal.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 04/08/2025
6+
ms.date: 04/11/2025
77
ms.topic: how-to
88
ms.service: azure-automation
99
---
@@ -13,7 +13,7 @@ ms.service: azure-automation
1313
> [!IMPORTANT]
1414
> Azure Automation Run as accounts, including Classic Run as accounts have retired on **30 September 2023** and replaced with [Managed Identities](automation-security-overview.md#managed-identities). You would no longer be able to create or renew Run as accounts through the Azure portal. For more information, see [migrating from an existing Run As accounts to managed identity](migrate-run-as-accounts-managed-identity.md?tabs=run-as-account#sample-scripts).
1515
16-
Run As accounts in Azure Automation provide authentication for managing resources on the Azure Resource Manager or Azure Classic deployment model using Automation runbooks and other Automation features. This article describes how to delete a Run As or Classic Run As account. When you perform this action, the Automation account is retained. After you delete the Run As account, you can re-create it in the Azure portal or with the provided PowerShell script.
16+
Run As accounts in Azure Automation provide authentication for managing resources on the Azure Resource Manager or Azure Classic deployment model using Automation runbooks and other Automation features. This article describes how to delete a Run As or Classic Run As account. When you perform this action, the Automation account is retained.
1717

1818
## Permissions for Run As accounts and Classic Run As accounts
1919

0 commit comments

Comments
 (0)