fixed warnings

Author: SnehaSudhirG

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

@@ -158,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.
 

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

@@ -0,0 +1,27 @@
+---
+title: Enable Azure Automation Start/Stop VMs during off-hours
+description: This article tells how to enable the Start/Stop VMs during off-hours feature for your Azure VMs.
+services: automation
+ms.subservice: process-automation
+ms.date: 11/29/2022
+ms.topic: conceptual
+ms.custom: engagement-fy23
+---
+
+# Enable Start/Stop VMs during off-hours
+
+> [!NOTE]
+>- 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.
+>- It is no longer possible to deploy the Start/Stop solution v1.
+
+For more information on version 2, see [Deploy Start/Stop VMs v2 to an Azure subscription](../azure-functions/start-stop-vms/deploy.md)
+
+
+## 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 set up the feature, see [Configure Stop/Start VMs during off-hours](automation-solution-vm-management-config.md).
+* To resolve feature errors, see [Troubleshoot Start/Stop VMs during off-hours issues](troubleshoot/start-stop-vm.md).

articles/automation/troubleshoot/start-stop-vm.md

@@ -73,7 +73,6 @@ Review the following fixes for potential resolutions:
 
    To learn more about errors when you register providers, see [Resolve errors for resource provider registration](../../azure-resource-manager/templates/error-register-resource-provider.md).
 * If you have a lock on your Log Analytics workspace, go to your workspace in the Azure portal and remove any locks on the resource.
-* If these resolutions don't solve your issue, follow the instructions under [Update the feature](../automation-solution-vm-management.md#update-the-feature) to redeploy Start/Stop VMs during off-hours.
 
 ## <a name="all-vms-fail-to-startstop"></a>Scenario: All VMs fail to start or stop
 
@@ -221,7 +220,7 @@ Many times errors can be caused by using an old and outdated version of the feat
 
 ### Resolution
 
-To resolve many errors, remove and [update Start/Stop VMs during off-hours](../automation-solution-vm-management.md#update-the-feature). You also can check the [job streams](../automation-runbook-execution.md#job-statuses) to look for any errors. 
+You can check the [job streams](../automation-runbook-execution.md#job-statuses) to look for any errors. 
 
 ## Next steps
 

articles/automation/update-management/operating-system-requirements.md

@@ -3,7 +3,7 @@ title: Azure Automation Update Management Supported Clients
 description: This article describes the supported Windows and Linux operating systems with Azure Automation Update Management.
 services: automation
 ms.subservice: update-management
-ms.date: 10/12/2021
+ms.date: 01/04/2023
 ms.topic: conceptual
 ---
 
@@ -18,7 +18,7 @@ The following table lists the supported operating systems for update assessments
 All operating systems are assumed to be x64. x86 is not supported for any operating system.
 
 > [!NOTE]
-> - Update assessment of Linux machines is only supported in certain regions as listed in the Automation account and Log Analytics workspace [mappings table](../how-to/region-mappings.md#supported-mappings).
+> - Update assessment of Linux machines is only supported in certain regions as listed in the Automation account and Log Analytics workspace [mappings table](../how-to/region-mappings.md#supported-mappings-for-version-1).
 > - Update Management does not support CIS hardened images.
 
 # [Windows operating system](#tab/os-win)
@@ -31,7 +31,7 @@ All operating systems are assumed to be x64. x86 is not supported for any operat
 # [Linux operating system](#tab/os-linux)
 
 > [!NOTE]
-> Update assessment of Linux machines is only supported in certain regions as listed in the Automation account and Log Analytics workspace [mappings table](../how-to/region-mappings.md#supported-mappings).
+> Update assessment of Linux machines is only supported in certain regions as listed in the Automation account and Log Analytics workspace [mappings table](../how-to/region-mappings.md#supported-mappings-for-version-1).
 
 |Operating system  |Notes  |
 |---------|---------|
@@ -86,7 +86,7 @@ By default, Windows VMs that are deployed from Azure Marketplace are set to rece
 - The Update Management feature depends on the system Hybrid Runbook Worker role, and you should confirm its [system requirements](../automation-linux-hrw-install.md#prerequisites). Because Update Management uses Automation runbooks to initiate assessment and update of your machines, review the [version of Python required](../automation-linux-hrw-install.md#supported-runbook-types) for your supported Linux distro.
 
 > [!NOTE]
-> Update assessment of Linux machines is supported in certain regions only. See the Automation account and Log Analytics workspace [mappings table](../how-to/region-mappings.md#supported-mappings).
+> Update assessment of Linux machines is supported in certain regions only. See the Automation account and Log Analytics workspace [mappings table](../how-to/region-mappings.md#supported-mappings-for-version-1).
 
 
 For hybrid machines, we recommend installing the Log Analytics agent for Linux by first connecting your machine to [Azure Arc-enabled servers](../../azure-arc/servers/overview.md), and then use Azure Policy to assign the [Deploy Log Analytics agent to Linux Azure Arc machines](../../governance/policy/samples/built-in-policies.md#monitoring) built-in policy definition. Alternatively, to monitor the machines use the [Enable Azure Monitor for VMs](../../governance/policy/samples/built-in-initiatives.md#monitoring) instead of Azure Monitor for VMs.

articles/automation/whats-new-archive.md

@@ -204,7 +204,7 @@ Automation account and State Configuration availability in Brazil South East. Fo
 
 **Type:** New feature
 
-Azure Automation region mapping updated to support Update Management feature in South Central US region. See [Supported region mapping](how-to/region-mappings.md#supported-mappings) for updates to the documentation to reflect this change.
+Azure Automation region mapping updated to support Update Management feature in South Central US region. See [Supported region mapping](how-to/region-mappings.md#supported-mappings-for-version-1) for updates to the documentation to reflect this change.
 
 ## September 2020
 
@@ -272,7 +272,7 @@ The New-OnPremiseHybridWorker runbook has been updated to support Az modules. Fo
 
 **Type:** New feature
 
-Azure Automation region mapping updated to support Update Management feature in China East 2 region. See [Supported region mapping](how-to/region-mappings.md#supported-mappings) for updates to the documentation to reflect this change.
+Azure Automation region mapping updated to support Update Management feature in China East 2 region. See [Supported region mapping](how-to/region-mappings.md#supported-mappings-for-version-1) for updates to the documentation to reflect this change.
 
 ## May 2020
 

articles/automation/whats-new.md

@@ -201,7 +201,7 @@ Start/Stop VMs during off-hours (v1) will deprecate on May 21, 2022. Customers s
 
 **Type:** New feature
 
-Region mapping has been updated to support Update Management and Change Tracking in Norway East, UAE North, North Central US, Brazil South, and Korea Central. For more information, see [Supported mappings](./how-to/region-mappings.md#supported-mappings).
+Region mapping has been updated to support Update Management and Change Tracking in Norway East, UAE North, North Central US, Brazil South, and Korea Central. For more information, see [Supported mappings](./how-to/region-mappings.md#supported-mappings-for-version-1).
 
 ### Support for system-assigned Managed Identities