Added a note in graphical runbook article

Author: SnehaSudhirG

articles/automation/automation-graphical-authoring-intro.md

@@ -10,6 +10,9 @@ ms.custom: devx-track-azurepowershell
 
 # Author graphical runbooks in Azure Automation
 
+> [!IMPORTANT]
+> Azure Automation Run As Account will retire on September 30, 2023 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.md#sample-scripts) to start migrating the runbooks from Run As account to managed identities before 30 September 2023. See the official announcement [here](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2023/preview/).
+
 All runbooks in Azure Automation are Windows PowerShell workflows. Graphical runbooks and graphical PowerShell Workflow runbooks generate PowerShell code that the Automation workers run but that you cannot view or modify. You can convert a graphical runbook to a graphical PowerShell Workflow runbook, and vice versa. However, you can't convert these runbooks to a textual runbook. Additionally, the Automation graphical editor can't import a textual runbook.
 
 Graphical authoring allows you to create runbooks for Azure Automation without the complexities of the underlying Windows PowerShell or PowerShell Workflow code. You can add activities to the canvas from a library of cmdlets and runbooks, link them together, and configure them to form a workflow. If you have ever worked with System Center Orchestrator or Service Management Automation (SMA), graphical authoring should look familiar. This article provides an introduction to the concepts you need to get started creating a graphical runbook.