Merge pull request #285895 from SnehaSudhirG/30Aug-CTRetirement

v-regandowner · web-flow · commit efafb13d66dd · 2024-08-30T11:04:58.000-04:00
[BULK] updated the announcement in all CT and AUM subservice articles
diff --git a/articles/automation/change-tracking/configure-alerts.md b/articles/automation/change-tracking/configure-alerts.md
@@ -3,13 +3,14 @@ title: How to create alerts for Azure Automation Change Tracking and Inventory
 description: This article tells how to configure Azure alerts to notify about the status of changes detected by Change Tracking and Inventory.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 07/22/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
 
 # How to create alerts for Change Tracking and Inventory
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
 Alerts in Azure proactively notify you of results from runbook jobs, service health issues, or other scenarios related to your Automation account. Azure Automation does not include pre-configured alert rules, but you can create your own based on data that it generates. This article provides guidance on creating alert rules based on changes identified by Change Tracking and Inventory.
 
 If you're not familiar with Azure Monitor alerts, see [Overview of alerts in Microsoft Azure](../../azure-monitor/alerts/alerts-overview.md) before you start. To learn more about alerts that use log queries, see [Log alerts in Azure Monitor](../../azure-monitor/alerts/alerts-unified-log.md).
diff --git a/articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md b/articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md
@@ -5,7 +5,7 @@ author: snehasudhirG
 services: automation
 ms.subservice: change-inventory-management
 ms.topic: conceptual
-ms.date: 05/01/2024
+ms.date: 08/30/2024
 ms.author: sudhirsneha
 ms.custom:
 ms.service: azure-automation
diff --git a/articles/automation/change-tracking/manage-change-tracking.md b/articles/automation/change-tracking/manage-change-tracking.md
@@ -10,6 +10,8 @@ ms.service: azure-automation
 
 # Manage Change Tracking and Inventory
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 When you add a new file or registry key to track, Azure Automation enables it for [Change Tracking and Inventory](overview.md). This article describes how to configure tracking, review tracking results, and handle alerts when changes are detected.
 
 Before using the procedures in this article, ensure that you've enabled Change Tracking and Inventory on your VMs using one of these techniques:
diff --git a/articles/automation/change-tracking/manage-scope-configurations.md b/articles/automation/change-tracking/manage-scope-configurations.md
@@ -3,13 +3,15 @@ title: Limit Azure Automation Change Tracking and Inventory deployment scope
 description: This article tells how to work with scope configurations to limit the scope of a Change Tracking and Inventory deployment.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 07/22/2024
+ms.date: 08/31/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
 
 # Limit Change Tracking and Inventory deployment scope
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 This article describes how to work with scope configurations when using the [Change Tracking and Inventory](overview.md) feature to deploy changes to your VMs. For more information, see [Targeting monitoring solutions in Azure Monitor (Preview)](/previous-versions/azure/azure-monitor/insights/solution-targeting).
 
 ## About scope configurations
diff --git a/articles/automation/change-tracking/remove-feature.md b/articles/automation/change-tracking/remove-feature.md
@@ -3,13 +3,15 @@ title: Remove Azure Automation Change Tracking and Inventory feature
 description: This article tells how to stop using Change Tracking and Inventory, and unlink an Automation account from the Log Analytics workspace. 
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 07/22/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
 
 # Remove Change Tracking and Inventory from Automation account
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 After you enable management of your virtual machines using Azure Automation Change Tracking and Inventory, you may decide to stop using it and remove the configuration from the account and linked Log Analytics workspace. This article tells you how to completely remove Change Tracking and Inventory from the managed VMs, your Automation account, and Log Analytics workspace.
 
 ## Sign into the Azure portal
diff --git a/articles/automation/change-tracking/remove-vms-from-change-tracking.md b/articles/automation/change-tracking/remove-vms-from-change-tracking.md
@@ -4,12 +4,14 @@ description: This article tells how to remove Azure and non-Azure machines from
 services: automation
 ms.subservice: change-inventory-management
 ms.topic: conceptual
-ms.date: 07/22/2024
+ms.date: 08/30/2024
 ms.service: azure-automation
 ---
 
 # Remove machines from Change Tracking and Inventory
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 When you're finished tracking changes on your Azure or non-Azure machines in your environment, you can stop managing them with the [Change Tracking and Inventory](overview.md) feature. To stop managing them, you will edit the saved search query `MicrosoftDefaultComputerGroup` in your Log Analytics workspace that is linked to your Automation account.
 
 ## Sign into the Azure portal
diff --git a/articles/automation/how-to/region-mappings.md b/articles/automation/how-to/region-mappings.md
@@ -1,7 +1,7 @@
 ---
 title: Supported regions for linked Log Analytics workspace
 description: This article describes the supported region mappings between an Automation account and a Log Analytics workspace as it relates to certain features of Azure Automation.
-ms.date: 07/22/2024
+ms.date: 08/30/2024
 services: automation
 ms.topic: conceptual
 ms.custom: references_regions
@@ -12,6 +12,8 @@ ms.custom: references_regions
 > [!NOTE]
 > Start/Stop VMs v1 is retired and we recommend you to start using [Start/Stop VMs v2](../../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.
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 In Azure Automation, you can enable the Update Management, Change Tracking and Inventory, and Start/Stop VMs during off-hours features for your servers and virtual machines. These features have a dependency on a Log Analytics workspace, and therefore require linking the workspace with an Automation account. However, only certain regions are supported to link them together. In general, the mapping is *not* applicable if you plan to link an Automation account to a workspace that won't have these features enabled.
 
 The mappings discussed here applying only to linking the Log Analytics Workspace to an Automation account. They don't apply to the virtual machines (VMs) that are connected to the workspace that's linked to the Automation Account. VMs aren't limited to the regions supported by a given Log Analytics workspace. They can be in any region. Keep in mind that having the VMs in a different region may affect state, local, and country/regional regulatory requirements, or your company's compliance requirements. Having VMs in a different region could also introduce data bandwidth charges.
diff --git a/articles/automation/includes/log-analytics-retirement-announcement.md b/articles/automation/includes/log-analytics-retirement-announcement.md
@@ -0,0 +1,9 @@
+---
+author: SnehaSudhir
+ms.author: sudhirsneha
+ms.topic: include
+ms.date: 08/30/2024
+---
+
+> [!Important]
+> Change Tracking and Inventory using Log Analytics agent has retired on **31 August 2024** and we recommend that you use Azure Monitoring Agent as the new supporting agent. Follow the guidelines for [migration from Change Tracking and inventory using Log Analytics to Change Tracking and inventory using Azure Monitoring Agent version](../change-tracking/guidance-migration-log-analytics-monitoring-agent.md).
diff --git a/articles/automation/troubleshoot/change-tracking.md b/articles/automation/troubleshoot/change-tracking.md
@@ -4,13 +4,15 @@ description: This article tells how to troubleshoot and resolve issues with the
 services: automation
 ms.subservice: change-inventory-management
 ms.custom: linux-related-content
-ms.date: 02/15/2021
+ms.date: 08/30/2024
 ms.topic: troubleshooting
 ms.service: azure-automation
 ---
 
 # Troubleshoot Change Tracking and Inventory issues
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 This article describes how to troubleshoot and resolve Azure Automation Change Tracking and Inventory issues. For general information about Change Tracking and Inventory, see [Change Tracking and Inventory overview](../change-tracking/overview.md).
 
 ## General errors
diff --git a/articles/automation/troubleshoot/onboarding.md b/articles/automation/troubleshoot/onboarding.md
@@ -2,12 +2,14 @@
 title: Troubleshoot Azure Automation feature deployment issues
 description: This article tells how to troubleshoot and resolve issues that arise when deploying Azure Automation features.
 services: automation
-ms.date: 02/11/2021
+ms.date: 08/30/2024
 ms.topic: troubleshooting
 ---
 
 # Troubleshoot feature deployment issues
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 You might receive error messages when you deploy the Azure Automation Update Management feature or the Change Tracking and Inventory feature on your VMs. This article describes the errors that might occur and how to resolve them.
 
 ## Known issues
diff --git a/articles/automation/troubleshoot/update-agent-issues-linux.md b/articles/automation/troubleshoot/update-agent-issues-linux.md
@@ -2,7 +2,7 @@
 title: Troubleshooting Linux update agent issues in Azure Automation
 description: This article tells how to troubleshoot and resolve issues with the Linux Windows update agent in Update Management.
 services: automation
-ms.date: 11/01/2021
+ms.date: 08/30/2024
 ms.topic: troubleshooting
 ms.subservice: update-management
 ms.custom: linux-related-content
@@ -11,6 +11,9 @@ ms.service: azure-automation
 
 # Troubleshoot Linux update agent issues
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
+
 There can be many reasons why your machine isn't showing up as ready (healthy) in Update Management. You can check the health of a Linux Hybrid Runbook Worker agent to determine the underlying problem. The following are the three readiness states for a machine:
 
 * Ready: The Hybrid Runbook Worker is deployed and was last seen less than one hour ago.
diff --git a/articles/automation/troubleshoot/update-agent-issues.md b/articles/automation/troubleshoot/update-agent-issues.md
@@ -2,14 +2,16 @@
 title: Troubleshoot Windows update agent issues in Azure Automation
 description: This article tells how to troubleshoot and resolve issues with the Windows update agent during Update Management.
 services: automation
-ms.date: 01/25/2020
+ms.date: 08/30/2024
 ms.topic: troubleshooting
 ms.subservice: update-management
 ms.service: azure-automation
 ---
 
 # Troubleshoot Windows update agent issues
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 There can be many reasons why your machine isn't showing up as ready (healthy) during an Update Management deployment. You can check the health of a Windows Hybrid Runbook Worker agent to determine the underlying problem. The following are the three readiness states for a machine:
 
 * Ready: The Hybrid Runbook Worker is deployed and was last seen less than one hour ago.
diff --git a/articles/automation/troubleshoot/update-management.md b/articles/automation/troubleshoot/update-management.md
@@ -3,7 +3,7 @@ title: Troubleshoot Azure Automation Update Management issues
 description: This article tells how to troubleshoot and resolve issues with Azure Automation Update Management.
 services: automation
 ms.subservice: update-management
-ms.date: 06/29/2024
+ms.date: 08/30/2024
 ms.topic: troubleshooting
 ms.custom: devx-track-azurepowershell, linux-related-content
 ms.service: azure-automation
@@ -14,6 +14,8 @@ ms.service: azure-automation
 > [!CAUTION]
 > This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 This article discusses issues that you might run into when using the Update Management feature to assess and manage updates on your machines. There's an agent troubleshooter for the Hybrid Runbook Worker agent to help determine the underlying problem. To learn more about the troubleshooter, see [Troubleshoot Windows update agent issues](update-agent-issues.md) and [Troubleshoot Linux update agent issues](update-agent-issues-linux.md). For other feature deployment issues, see [Troubleshoot feature deployment issues](onboarding.md).
 
 >[!NOTE]
diff --git a/articles/automation/update-management/configure-alerts.md b/articles/automation/update-management/configure-alerts.md
@@ -3,13 +3,15 @@ title: How to create alerts for Azure Automation Update Management
 description: This article tells how to configure Azure alerts to notify about the status of update assessments or deployments.
 services: automation
 ms.subservice: update-management
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
 
 # How to create alerts for Update Management
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 Alerts in Azure proactively notify you of results from runbook jobs, service health issues, or other scenarios related to your Automation account. Azure Automation does not include pre-configured alert rules, but you can create your own based on data that it generates. This article provides guidance on creating alert rules using the metrics included with Update Management
 
 ## Available metrics
diff --git a/articles/automation/update-management/deploy-updates.md b/articles/automation/update-management/deploy-updates.md
@@ -3,7 +3,7 @@ title: How to create update deployments for Azure Automation Update Management
 description: This article describes how to schedule update deployments and review their status.
 services: automation
 ms.subservice: update-management
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
@@ -13,6 +13,8 @@ ms.service: azure-automation
 > [!CAUTION]
 > This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 This article describes how to schedule an update deployment and review the process after the deployment is complete. You can configure an update deployment from a selected Azure virtual machine, from the selected Azure Arc-enabled server, or from the Automation account across all configured machines and servers.
 
 Under each scenario, the deployment you create targets that selected machine or server, or in the case of creating a deployment from your Automation account, you can target one or more machines. When you schedule an update deployment from an Azure VM or Azure Arc-enabled server, the steps are the same as deploying from your Automation account, with the following exceptions:
diff --git a/articles/automation/update-management/enable-from-automation-account.md b/articles/automation/update-management/enable-from-automation-account.md
@@ -3,14 +3,16 @@ title: Enable Azure Automation Update Management from Automation account
 description: This article tells how to enable Update Management from an Automation account.
 services: automation
 ms.subservice: update-management
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.custom: mvc
 ms.service: azure-automation
 ---
 
 # Enable Update Management from an Automation account
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 This article describes how you can use your Automation account to enable the [Update Management](overview.md) feature for VMs in your environment, including machines or servers registered with [Azure Arc-enabled servers](../../azure-arc/servers/overview.md). To enable Azure VMs at scale, you must enable an existing Azure VM using Update Management.
 
 > [!NOTE]
diff --git a/articles/automation/update-management/enable-from-portal.md b/articles/automation/update-management/enable-from-portal.md
@@ -3,14 +3,16 @@ title: Enable Azure Automation Update Management from the Azure portal
 description: This article tells how to enable Update Management from the Azure portal.
 services: automation
 ms.subservice: update-management
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.custom: mvc
 ms.service: azure-automation
 ---
 
 # Enable Update Management from the Azure portal
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 This article describes how you can enable the [Update Management](overview.md) feature for VMs by browsing the Azure portal. To enable Azure VMs at scale, you must enable an existing Azure VM using Update Management.
 
 The number of resource groups that you can use for managing your VMs is limited by the [Resource Manager deployment limits](../../azure-resource-manager/templates/deploy-to-resource-group.md). Resource Manager deployments, not to be confused with Update deployments, are limited to five resource groups per deployment. Two of these resource groups are reserved to configure the Log Analytics workspace, Automation account, and related resources. This leaves you with three resource groups to select for management by Update Management. This limit only applies to simultaneous setup, not the number of resource groups that can be managed by an Automation feature.
diff --git a/articles/automation/update-management/enable-from-runbook.md b/articles/automation/update-management/enable-from-runbook.md
@@ -4,13 +4,15 @@ description: This article tells how to enable Update Management from a runbook.
 services: automation
 ms.subservice: update-management
 ms.topic: conceptual
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.custom: mvc
 ms.service: azure-automation
 ---
 
 # Enable Update Management from a runbook
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 This article describes how you can use a runbook to enable the [Update Management](overview.md) feature for VMs in your environment. To enable Azure VMs at scale, you must enable an existing VM with Update Management.
 
 > [!NOTE]
diff --git a/articles/automation/update-management/enable-from-template.md b/articles/automation/update-management/enable-from-template.md
@@ -5,12 +5,14 @@ services:  automation
 ms.subservice: update-management
 ms.custom: devx-track-arm-template
 ms.topic: conceptual
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.service: azure-automation
 ---
 
 # Enable Update Management using Azure Resource Manager template
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 You can use an [Azure Resource Manager template](../../azure-resource-manager/templates/syntax.md) to enable the Azure Automation Update Management feature in your resource group. This article provides a sample template that automates the following:
 
 * Automates the creation of an Azure Monitor Log Analytics workspace.
diff --git a/articles/automation/update-management/enable-from-vm.md b/articles/automation/update-management/enable-from-vm.md
@@ -3,14 +3,16 @@ title: Enable Azure Automation Update Management for an Azure VM
 description: This article tells how to enable Update Management for an Azure VM.
 services: automation
 ms.subservice: update-management
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.custom: mvc
 ms.service: azure-automation
 ---
 
 # Enable Update Management for an Azure VM
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 This article describes how you can enable the [Update Management](overview.md) feature on one or more Azure virtual machines (VM). To enable Azure VMs at scale, you must enable an existing Azure VM using Update Management.
 
 > [!NOTE]
diff --git a/articles/automation/update-management/manage-updates-for-vm.md b/articles/automation/update-management/manage-updates-for-vm.md
@@ -5,7 +5,7 @@ services: automation
 ms.subservice: update-management
 ms.custom: linux-related-content
 ms.topic: conceptual
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.service: azure-automation
 ---
 
@@ -14,6 +14,8 @@ ms.service: azure-automation
 > [!CAUTION]
 > This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
+[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
+
 Software updates in Azure Automation Update Management provides a set of tools and resources that can help manage the complex task of tracking and applying software updates to machines in Azure and hybrid cloud. An effective software update management process is necessary to maintain operational efficiency, overcome security issues, and reduce the risks of increased cyber security threats. However, because of the changing nature of technology and the continual appearance of new security threats, effective software update management requires consistent and continual attention.
 
 > [!NOTE]
diff --git a/articles/automation/update-management/mecmintegration.md b/articles/automation/update-management/mecmintegration.md
diff --git a/articles/automation/update-management/operating-system-requirements.md b/articles/automation/update-management/operating-system-requirements.md
diff --git a/articles/automation/update-management/overview.md b/articles/automation/update-management/overview.md
diff --git a/articles/automation/update-management/plan-deployment.md b/articles/automation/update-management/plan-deployment.md
diff --git a/articles/automation/update-management/pre-post-scripts.md b/articles/automation/update-management/pre-post-scripts.md
diff --git a/articles/automation/update-management/remove-feature.md b/articles/automation/update-management/remove-feature.md
diff --git a/articles/automation/update-management/remove-vms.md b/articles/automation/update-management/remove-vms.md
diff --git a/articles/automation/update-management/view-update-assessments.md b/articles/automation/update-management/view-update-assessments.md
