fixed warnings

Author: SnehaSudhirG

.openpublishing.redirection.json

@@ -2291,15 +2291,10 @@
             "redirect_document_id": false
         },
         {
-            "source_path_from_root": "articles/automation/automation-solution-vm-management.md",
+            "source_path_from_root": "/articles/automation/automation-solution-vm-management.md",
             "redirect_url":"/azure/azure-functions/start-stop-vms/overview",
             "redirect_document_id": false
         },
-        {
-             "source_path_from_root": "/articles/automation/how-to/region-mappings.md",
-             "redirect_url": "/azure/azure-functions/start-stop-vms/overview",
-             "redirect_document_id": false
-        },
         {
              "source_path_from_root": "/articles/automation/automation-solution-vm-management-config.md",
              "redirect_url": "/azure/azure-functions/start-stop-vms/deploy",

articles/automation/change-tracking/region-mappings-monitoring-agent.md

@@ -42,4 +42,4 @@ The following table shows the supported mappings:
 
 * Learn about Update Management in [Update Management overview](../update-management/overview.md).
 * Learn about Change Tracking and Inventory in [Change Tracking and Inventory overview](../change-tracking/overview.md).
-* Learn about Start/Stop VMs during off-hours in [Start/Stop VMs during off-hours overview](../automation-solution-vm-management.md).
+

articles/automation/delete-account.md

@@ -77,7 +77,7 @@ To unlink from your Automation account, perform the following steps.
 
 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)
+   ![Unlink workspace page](media/delete-account/automation-unlink-workspace-blade.png)
 
     While it attempts to unlink the Log Analytics workspace, you can track the progress under **Notifications** from the menu.
 
@@ -141,7 +141,7 @@ To unlink from your Automation account, perform the following steps.
 
 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)
+   ![Unlink workspace page](media/delete-account/automation-unlink-workspace-blade.png)
 
     While it attempts to unlink the Log Analytics workspace, you can track the progress under **Notifications** from the menu.
 

articles/automation/index.yml

@@ -29,8 +29,6 @@ landingContent:
             url: ./learn/powershell-runbook-managed-identity.md
       - linkListType: deploy
         links:
-          - text: Start/Stop VMs during off-hours
-            url: automation-solution-vm-management.md
           - text: Change tracking and inventory using Azure Monitoring Agent
             url:  change-tracking/overview-monitoring-agent.md
 

articles/automation/media/delete-account/automation-unlink-workspace-blade.png

@@ -53,7 +53,8 @@ The default modules are also known as global modules. In the Azure portal, the *
 ![Screenshot of global module property in Azure Portal](../media/modules/automation-global-modules.png)
 
 > [!NOTE]
-> We don't recommend altering modules and runbooks in Automation accounts used for deployment of the [Start/Stop VMs during off-hours](../automation-solution-vm-management.md) feature.
+> We don't recommend altering modules and runbooks in Automation accounts used for deployment of the [Start/Stop VMs during off-hours](./azure-functions/start-stop-vms/overview.md) feature.
+
 
 |Module name|Version|
 |---|---|

articles/automation/shared-resources/modules.md

@@ -215,7 +215,7 @@ Azure Automation region mapping updated to support Update Management feature in
 
 **Type:** New feature
 
-Start/Stop VM runbooks have been updated to use Az modules in place of Azure Resource Manager modules. See [Start/Stop VMs during off-hours](automation-solution-vm-management.md) overview for updates to the documentation to reflect these changes.
+Start/Stop VM runbooks have been updated to use Az modules in place of Azure Resource Manager modules. 
 
 ## August 2020
 

articles/automation/whats-new-archive.md

@@ -12,7 +12,7 @@ ms.date: 09/23/2022
 
 The Start/Stop VMs v2 feature starts or stops Azure Virtual Machines instances across multiple subscriptions. It starts or stops virtual machines on user-defined schedules, provides insights through [Azure Application Insights](../../azure-monitor/app/app-insights-overview.md), and send optional notifications by using [action groups](../../azure-monitor/alerts/action-groups.md). For most scenarios, Start/Stop VMs can manage virtual machines deployed and managed both by Azure Resource Manager and by Azure Service Manager (classic), which is [deprecated](../../virtual-machines/classic-vm-deprecation.md).
 
-This new version of Start/Stop VMs v2 provides a decentralized low-cost automation option for customers who want to optimize their VM costs. It offers all of the same functionality as the [original version](../../automation/automation-solution-vm-management.md) available with Azure Automation, but it's designed to take advantage of newer technology in Azure. The Start/Stop VMs v2 relies on mutiple Azure services and it will be charged based on the service that are deployed and consumed.
+This new version of Start/Stop VMs v2 provides a decentralized low-cost automation option for customers who want to optimize their VM costs. It offers all of the same functionality as the original version that was available with Azure Automation, but it's designed to take advantage of newer technology in Azure. The Start/Stop VMs v2 relies on multiple Azure services and it will be charged based on the service that are deployed and consumed.
 
 ## Important Start/Stop VMs v2 Updates
 
@@ -25,7 +25,7 @@ This new version of Start/Stop VMs v2 provides a decentralized low-cost automati
     
 ## Overview
 
-Start/Stop VMs v2 is redesigned and it doesn't depend on Azure Automation or Azure Monitor Logs, as required by the [previous version](../../automation/automation-solution-vm-management.md). This version relies on [Azure Functions](../../azure-functions/functions-overview.md) to handle the VM start and stop execution.
+Start/Stop VMs v2 is redesigned and it doesn't depend on Azure Automation or Azure Monitor Logs, as required by the previous version. This version relies on [Azure Functions](../../azure-functions/functions-overview.md) to handle the VM start and stop execution.
 
 A managed identity is created in Microsoft Entra ID for this Azure Functions application and allows Start/Stop VMs v2 to easily access other Microsoft Entra protected resources, such as the logic apps and Azure VMs. For more about managed identities in Microsoft Entra ID, see [Managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md).
 

articles/azure-functions/start-stop-vms/overview.md

@@ -48,7 +48,7 @@ When you first start working with a service, consider the following points:
 At this point, you have setup autoscaling and autostop behaviors. As you move beyond the basics, consider the following points:
 
 - Automate the process of automatically scaling or stopping resources that don't support it or have more complex requirements.
-  - Consider using automation services, like [Azure Automation](../../automation/automation-solution-vm-management.md) or [Azure Functions](../../azure-functions/start-stop-vms/overview.md).
+- Consider using [Azure Functions](../../azure-functions/start-stop-vms/overview.md).
 - [Assign an "Env" or Environment tag](../../azure-resource-manager/management/tag-resources.md) to identify which resources are for development, testing, staging, production, etc.
   - Prefer assigning tags at a subscription or resource group level. Then enable the [tag inheritance policy for Azure Policy](../../governance/policy/samples/built-in-policies.md#tags) and [Cost Management tag inheritance](../costs/enable-tag-inheritance.md) to cover resources that don't emit tags with usage data.
   - Consider setting up automated scripts to stop resources with specific up-time profiles (for example, stop developer VMs during off-peak hours if they haven't been used in 2 hours).