edited note with revised date and blog info

SnehaSudhirG · SnehaSudhirG · commit 2d8f00347b0d · 2022-07-26T23:38:51.000+05:30
diff --git a/articles/automation/automation-hrw-run-runbooks.md b/articles/automation/automation-hrw-run-runbooks.md
@@ -11,8 +11,7 @@ ms.custom: devx-track-azurepowershell
 # Run Automation runbooks on a Hybrid Runbook Worker
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on September 16, 2025 and will be replaced with Managed Identities.
-While we continue to support Run As account for both existing and new Automation accounts from the Azure portal and PowerShell, we recommend you to switch to [Managed identities](/automation-security-overview.md#managed-identities) for runbook authentication. For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts).
+> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
 
 
 Runbooks that run on a [Hybrid Runbook Worker](automation-hybrid-runbook-worker.md) typically manage resources on the local computer or against resources in the local environment where the worker is deployed. Runbooks in Azure Automation typically manage resources in the Azure cloud. Even though they are used differently, runbooks that run in Azure Automation and runbooks that run on a Hybrid Runbook Worker are identical in structure.
diff --git a/articles/automation/automation-security-guidelines.md b/articles/automation/automation-security-guidelines.md
@@ -10,9 +10,7 @@ ms.topic: conceptual
 # Security best practices in Azure Automation
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on September 16, 2025 and will be replaced with Managed Identities.
-While we continue to support Run As account for both existing and new Automation accounts from the Azure portal and PowerShell, we recommend you to switch to [Managed identities](/automation-security-overview.md#managed-identities) for runbook authentication. For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts).
-
+> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
 
 This article details the best practices to securely execute the automation jobs.
 [Azure Automation](./overview.md) provides you the platform to orchestrate frequent, time consuming, error-prone infrastructure management and operational tasks, as well as mission-critical operations. This service allows you to execute scripts, known as automation runbooks seamlessly across cloud and hybrid environments. 
diff --git a/articles/automation/automation-security-overview.md b/articles/automation/automation-security-overview.md
@@ -12,8 +12,7 @@ ms.custom: devx-track-azurepowershell
 # Azure Automation account authentication overview
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on September 16, 2025 and will be replaced with Managed Identities.
-While we continue to support Run As account for both existing and new Automation accounts from the Azure portal and PowerShell, we recommend you to switch to [Managed identities](/automation-security-overview.md#managed-identities) for runbook authentication. For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts).
+> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
 
 Azure Automation allows you to automate tasks against resources in Azure, on-premises, and with other cloud providers such as Amazon Web Services (AWS). You can use runbooks to automate your tasks, or a Hybrid Runbook Worker if you have business or operational processes to manage outside of Azure. Working in any one of these environments require permissions to securely access the resources with the minimal rights required.
 
diff --git a/articles/automation/create-run-as-account.md b/articles/automation/create-run-as-account.md
@@ -10,8 +10,7 @@ ms.topic: conceptual
 # How to create an Azure Automation Run As account
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on September 16, 2025 and will be replaced with Managed Identities.
-While we continue to support Run As account for both existing and new Automation accounts from the Azure portal and PowerShell, we recommend you to switch to [Managed identities](/automation-security-overview.md#managed-identities) for runbook authentication. For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts).
+> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
 
 
 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 create a Run As or Classic Run As account from the Azure portal or Azure PowerShell.
diff --git a/articles/automation/delete-run-as-account.md b/articles/automation/delete-run-as-account.md
@@ -10,9 +10,7 @@ ms.topic: conceptual
 # Delete an Azure Automation Run As account
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on September 16, 2025 and will be replaced with Managed Identities.
-While we continue to support Run As account for both existing and new Automation accounts from the Azure portal and PowerShell, we recommend you to switch to [Managed identities](/automation-security-overview.md#managed-identities) for runbook authentication. For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts).
-
+> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
 
 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.
 
diff --git a/articles/automation/manage-run-as-account.md b/articles/automation/manage-run-as-account.md
@@ -11,8 +11,7 @@ ms.custom: devx-track-azurepowershell
 # Manage an Azure Automation Run As account
 
 > [!IMPORTANT]
-> Azure Automation Run As Account will retire on September 16, 2025 and will be replaced with Managed Identities.
-While we continue to support Run As account for both existing and new Automation accounts from the Azure portal and PowerShell, we recommend you to switch to [Managed identities](/automation-security-overview.md#managed-identities) for runbook authentication. For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts).
+> Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
 
 
 
diff --git a/articles/automation/whats-new.md b/articles/automation/whats-new.md
@@ -28,8 +28,10 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
 
 **Type:** Plan for change
 
-Azure Automation Run As Account will retire on September 16, 2025 and will be replaced with Managed Identities. We recommend you to switch to Managed identities for runbook authentication. For more information, see [migrating from an existing Run As accounts to managed identity](/azure/automation/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts).
- 
+
+Azure Automation Run As Account will retire on September 30, 2025 and will be replaced with Managed Identities.Before that date, you'll need to start migrating your runbooks to use [managed identities](/automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](/migrate-run-as-accounts-managed-identity?tabs=ua-managed-identity#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2025. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2025/preview/).
+
+
 ## March 2022
 
 ###  Forward diagnostic audit data to Azure Monitor logs
