Merge pull request #222855 from SnehaSudhirG/04Jan-StartStopVM

StartStopVM-Feedback incorporated, removed article

Author: BCS2022

.openpublishing.redirection.json

@@ -5988,6 +5988,11 @@
             "redirect_url": "/azure/automation/create-azure-automation-account-portal",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/automation/automation-solution-vm-management-enable.md",
+            "redirect_url": "/azure/automation/automation-solution-vm-management",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/update-center/enable-machines.md",
             "redirect_url": "/azure/update-center/updates-maintenance-schedules",

articles/automation/TOC.yml

@@ -292,8 +292,6 @@
           href: automation-solution-vm-management.md
         - name: Support regions for linked Log Analytics workspace
           href: how-to/region-mappings.md
-        - name: Enable Start/Stop VMs during off-hours
-          href: automation-solution-vm-management-enable.md
         - name: Configure Stop/Start VMs during off-hours
           href: automation-solution-vm-management-config.md
         - name: Query logs from Start/Stop VMs during off-hours

articles/automation/automation-solution-vm-management-config.md

@@ -3,16 +3,15 @@ title: Configure Azure Automation Start/Stop VMs during off-hours
 description: This article tells how to configure the Start/Stop VMs during off-hours feature to support different use cases or scenarios.
 services: automation
 ms.subservice: process-automation
-ms.date: 11/29/2022
+ms.date: 01/04/2023
 ms.topic: conceptual
 ms.custom: engagement-fy23
 ---
 
 # Configure Start/Stop VMs during off-hours
 
 > [!NOTE]
-> Start/Stop VM during off-hours, version 1 is deprecated and unavailable in the marketplace now. We recommend that you start using [version 2](../azure-functions/start-stop-vms/overview.md), which is now generally available.
-The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until further announcement.
+> Start/Stop VM during off-hours, version 1 is going to retire soon by CY23 and is unavailable in the marketplace now. We recommend that you start using [version 2](/articles/azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until retirement in CY23. The details on announcement will be shared soon.
 
 This article describes how to configure the [Start/Stop VMs during off-hours](automation-solution-vm-management.md) feature to support the described scenarios. You can also learn how to:
 
@@ -159,7 +158,7 @@ The feature allows you to add VMs to be targeted or excluded.
 
 There are two ways to ensure that a VM is included when the feature runs:
 
-* Each of the parent [runbooks](automation-solution-vm-management.md#runbooks) of the feature has a `VMList` parameter. You can pass a comma-separated list of VM names (without spaces) to this parameter when scheduling the appropriate parent runbook for your situation, and these VMs will be included when the feature runs.
+* Each of the parent runbooksof the feature has a `VMList` parameter. You can pass a comma-separated list of VM names (without spaces) to this parameter when scheduling the appropriate parent runbook for your situation, and these VMs will be included when the feature runs.
 
 * To select multiple VMs, set `External_Start_ResourceGroupNames` and `External_Stop_ResourceGroupNames` with the resource group names that contain the VMs you want to start or stop. You can also set the variables to a value of `*` to have the feature run against all resource groups in the subscription.
 
@@ -183,6 +182,11 @@ Configuring the feature to just stop VMs at a certain time is supported. In this
 
 1. Select **OK** to save your changes.
 
+
+## Create alerts
+
+Start/Stop VMs during off-hours doesn't include a predefined set of Automation job alerts. Review [Forward job data to Azure Monitor Logs](automation-manage-send-joblogs-log-analytics.md#azure-monitor-log-records) to learn about log data forwarded from the Automation account related to the runbook job results and how to create job failed alerts to support your DevOps or operational processes and procedures.
+
 ## Next steps
 
 * To monitor the feature during operation, see [Query logs from Start/Stop VMs during off-hours](automation-solution-vm-management-logs.md).

articles/automation/automation-solution-vm-management-enable.md

@@ -3,105 +3,26 @@ title: Remove Azure Automation Start/Stop VMs during off-hours overview
 description: This article describes how to remove the Start/Stop VMs during off-hours feature and unlink an Automation account from the Log Analytics workspace.
 services: automation
 ms.subservice: process-automation
-ms.date: 11/29/2022
+ms.date: 01/04/2023
 ms.topic: conceptual
 ms.custom: engagement-fy23
 ---
 
 # Remove Start/Stop VMs during off-hours from Automation account
 
 > [!NOTE]
-> Start/Stop VM during off-hours, version 1 is deprecated and unavailable in the marketplace now. We recommend that you start using [version 2](../azure-functions/start-stop-vms/overview.md), which is now generally available.
-The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until further announcement.
+> Start/Stop VM during off-hours, version 1 is going to retire soon by CY23 and is unavailable in the marketplace now. We recommend that you start using [version 2](/articles/azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until retirement in CY23. The details on announcement will be shared soon.
 
 After you enable the Start/Stop VMs during off-hours feature to manage the running state of your Azure VMs, you may decide to stop using it. Removing this feature can be done using one of the following methods based on the supported deployment models:
 
-* Delete the resource group containing the Automation account and linked Azure Monitor Log Analytics workspace, each dedicated to support this feature.
-* Unlink the Log Analytics workspace from the Automation account and delete the Automation account dedicated for this feature.
-* Delete the feature from an Automation account and linked workspace that are supporting other management and monitoring objectives.
-
-Deleting this feature only removes the associated runbooks, it doesn't delete the schedules or variables that were created during deployment or any custom-defined ones created after.
 
 > [!NOTE]
-> Before proceeding, verify there aren't any [Resource Manager locks](../azure-resource-manager/management/lock-resources.md) applied at the subscription, resource group, or resource which prevents accidental deletion or modification of critical resources. When you deploy the Start/Stop VMs during off-hours solution, it sets the lock level to **CanNotDelete** against several dependent resources in the Automation account (specifically its runbooks and variables). Any locks need to be removed before you can delete the Automation account.
+> Before proceeding, verify there aren't any [Resource Manager locks](../azure-resource-manager/management/lock-resources.md) applied at the subscription, resource group, or resource which prevents accidental deletion or modification of critical resources. When you deploy the Start/Stop VMs during off-hours solution, it sets the lock level to **Cannot Delete** against several dependent resources in the Automation account (specifically its runbooks and variables). Any locks need to be removed before you can delete the Automation account.
 
 ## Delete the dedicated resource group
 
 To delete the resource group, follow the steps outlined in the [Azure Resource Manager resource group and resource deletion](../azure-resource-manager/management/delete-resource-group.md) article.
 
-## Delete the Automation account
-
-To delete your Automation account dedicated to Start/Stop VMs during off-hours, perform the following steps.
-
-1. Sign in to Azure at [https://portal.azure.com](https://portal.azure.com).
-
-2. Navigate to your Automation account, and select **Linked workspace** under **Related resources**.
-
-3. Select **Go to workspace**.
-
-4. Click **Solutions** under **General**.
-
-5. On the Solutions page, select **Start-Stop-VM[Workspace]**.
-
-6. On the **VMManagementSolution[Workspace]** page, select **Delete** from the menu.
-
-7. While the information is verified and the feature is deleted, you can track the progress under **Notifications**, chosen from the menu. You're returned to the Solutions page after the removal process.
-
-### Unlink workspace from Automation account
-
-There are two options for unlinking the Log Analytics workspace from your Automation account. You can perform this process from the Automation account or from the linked workspace.
-
-To unlink from your Automation account, perform the following steps.
-
-1. In the Azure portal, select **Automation Accounts**.
-
-2. Open your Automation account and select **Linked workspace** under **Related Resources** on the left.
-
-3. On the **Unlink workspace** page, select **Unlink workspace** and respond to prompts.
-
-   ![Unlink workspace page](media/automation-solution-vm-management-remove/automation-unlink-workspace-blade.png)
-
-    While it attempts to unlink the Log Analytics workspace, you can track the progress under **Notifications** from the menu.
-
-To unlink from the workspace, perform the following steps.
-
-1. In the Azure portal, select **Log Analytics workspaces**.
-
-2. From the workspace, select **Automation Account** under **Related Resources**.
-
-3. On the Automation Account page, select **Unlink account** and respond to prompts.
-
-While it attempts to unlink the Automation account, you can track the progress under **Notifications** from the menu.
-
-### Delete Automation account
-
-1. In the Azure portal, select **Automation Accounts**.
-
-2. Open your Automation account and select **Delete** from the menu.
-
-While the information is verified and the account is deleted, you can track the progress under **Notifications**, chosen from the menu.
-
-## Delete the feature
-
-To delete Start/Stop VMs during off-hours from your Automation account, perform the following steps. The Automation account and Log Analytics workspace aren't deleted as part of this process. If you don't want to keep the Log Analytics workspace, you must manually delete it. For more information about deleting your workspace, see [Delete and recover Azure Log Analytics workspace](../azure-monitor/logs/delete-workspace.md).
-
-1. Navigate to your Automation account, and select **Linked workspace** under **Related resources**.
-
-2. Select **Go to workspace**.
-
-3. Click **Solutions** under **General**.
-
-4. On the Solutions page, select **Start-Stop-VM[Workspace]**.
-
-5. On the **VMManagementSolution[Workspace]** page, select **Delete** from the menu.
-
-    ![Delete VM management feature](media/automation-solution-vm-management/vm-management-solution-delete.png)
-
-6. In the Delete Solution window, confirm that you want to delete the feature.
-
-7. While the information is verified and the feature is deleted, you can track the progress under **Notifications**, chosen from the menu. You're returned to the Solutions page after the removal process.
-
-8. If you don't want to keep the [resources](automation-solution-vm-management.md#components) created by the feature or by you afterwards (such as, variables, schedules, etc.), you have to manually delete them from the account.
 
 ## Next steps