Merge pull request #116690 from yuelilu33/main

Add instruction on how to migrate runbook action from "Run as account" to "run as managed identity"

Author: Court72

articles/azure-monitor/alerts/action-groups.md

@@ -602,6 +602,21 @@ Write-Host "My Azure AD Application (ObjectId): " + $myApp.ObjectId
 Write-Host "My Azure AD Application's Roles"
 Write-Host $myApp.AppRoles
 ```
+### Migrate Runbook action from "Run as account" to "Run as Managed Identity"  
+> [!NOTE]
+>
+> Azure Automation "Run as account" has [retired](https://azure.microsoft.com/updates/azure-automation-runas-account-retiring-on-30-september-2023/) on 30 September 2023, which affects actions created with action type "Automation Runbook". Existing actions linking to "Run as account" runbooks won't be supported after retirement. However, those runbooks would continue to execute until the expiry of "Run as" certificate of the Automation account.
+
+To ensure you can continue using the runbook actions, you need to:
+1.  Edit the action group by adding a new action with action type "Automation Runbook" and choose the same runbook from the dropdown. (All 5 runbooks in the dropdown have been reconfigured at the backend to authenticate using Managed Identity instead of Run as account. System-assigned Managed Identity in Automation account would be enabled with VM Contributor role at the subscription level would be assigned automatically.)
+
+    :::image type="content" source="./media/action-groups/action-group-runbook-add.png" alt-text="Screenshot of adding a runbook action to an action group.":::
+
+    :::image type="content" source="./media/action-groups/action-group-runbook-configure.png" alt-text="Screenshot of configuring the runbook action.":::
+
+2. Delete old runbook action which links to a "Run as account" runbook.
+3. Save the action group.
+
 ## Next steps
 
 - Get an [overview of alerts](./alerts-overview.md) and learn how to receive alerts.