Merge pull request #285889 from MicrosoftDocs/main

Publish to live, Friday 4 AM PST, 8/30

Author: ttorble

articles/automation/change-tracking/enable-from-automation-account.md

@@ -3,13 +3,16 @@ title: Enable Azure Automation Change Tracking and Inventory from Automation acc
 description: This article tells how to enable Change Tracking and Inventory from an Automation account.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 07/22/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
 
 # Enable Change Tracking and Inventory from an Automation account
 
+> [!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](guidance-migration-log-analytics-monitoring-agent.md).
+
 This article describes how you can use your Automation account to enable [Change Tracking and Inventory](overview.md) for VMs in your environment. To enable Azure VMs at scale, you must enable an existing VM using Change Tracking and Inventory.
 
 > [!NOTE]

articles/automation/change-tracking/enable-from-portal.md

@@ -3,13 +3,16 @@ title: Enable Azure Automation Change Tracking and Inventory from the Azure port
 description: This article tells how to enable the Change Tracking and Inventory feature from the Azure portal.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 07/22/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
 
 # Enable Change Tracking and Inventory from Azure portal
 
+> [!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](guidance-migration-log-analytics-monitoring-agent.md).
+
 This article describes how you can enable [Change Tracking and Inventory](overview.md) for one or more Azure VMs in the Azure portal. To enable Azure VMs at scale, you must enable an existing VM using Change Tracking and Inventory.
 
 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 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 Change Tracking and Inventory. This limit only applies to simultaneous setup, not the number of resource groups that can be managed by an Automation feature.

articles/automation/change-tracking/enable-from-runbook.md

@@ -4,12 +4,15 @@ description: This article tells how to enable Change Tracking and Inventory 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
 ---
 
 # Enable Change Tracking and Inventory from a runbook
 
+> [!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](guidance-migration-log-analytics-monitoring-agent.md).
+
 This article describes how you can use a runbook to enable [Change Tracking and Inventory](overview.md) for VMs in your environment. To enable Azure VMs at scale, you must enable an existing VM using Change Tracking and Inventory.
 
 > [!NOTE]

articles/automation/change-tracking/overview.md

@@ -3,7 +3,7 @@ title: Azure Automation Change Tracking and Inventory overview
 description: This article describes the Change Tracking and Inventory feature, which helps you identify software and Microsoft service changes in your environment.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 08/02/2024
+ms.date: 08/30/2024
 ms.custom: linux-related-content
 ms.topic: conceptual
 ms.service: azure-automation
@@ -15,7 +15,16 @@ ms.service: azure-automation
 > 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).
 
 > [!Important]
-> - Change Tracking and Inventory using Log Analytics agent will  retire 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](guidance-migration-log-analytics-monitoring-agent.md).
+> 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](guidance-migration-log-analytics-monitoring-agent.md).
+
+> [!Important]
+> You can expect the following if you use the capability using Change Tracking & Inventory Log Analytics Agent.
+> - **Functionality**: The functional capabilities of Change Tracking with Log Analytics agent would continue to work till Feb'2025. However, the support will be limited and can lead to potential issues over time.
+> - **Installation**: The ability to configure Change Tracking & Inventory using MMA/OMS agents will be removed from the Azure portal soon.
+>- **Customer Support**: You will not be able to get support through existing channels for Change Tracking & Inventory with MMA/OMS. Microsoft will provide support on a best effort basis.
+> - **New capabilities and support matrix**:  No new capabilities will be added, including functionality for additional Windows or Linux versions.
+> - **File Integrity Monitoring**: Microsoft Defender for Servers Plan 2 will offer a new File Integrity Monitoring (FIM) solution powered by Microsoft Defender for Endpoint (MDE) integration. Microsoft Defender for Cloud recommends disabling FIM over MMA by November 2024 and onboarding your environment to the new FIM version based on Defender for Endpoint. File Integrity Monitoring based on Log Analytics Agent (MMA) is supported till November 2024. [Learn more](https://learn.microsoft.com/azure/defender-for-cloud/prepare-deprecation-log-analytics-mma-agent#migration-from-fim-over-log-analytics-agent-mma).
+
 
 This article introduces you to Change Tracking and Inventory in Azure Automation. This feature tracks changes in virtual machines hosted in Azure, on-premises, and other cloud environments to help you pinpoint operational and environmental issues with software managed by the Distribution Package Manager. Items that are tracked by Change Tracking and Inventory include:
 

articles/automation/update-management/overview.md

@@ -4,7 +4,7 @@ description: This article provides an overview of the Update Management feature
 services: automation
 ms.subservice: update-management
 ms.custom: linux-related-content
-ms.date: 07/15/2024
+ms.date: 08/30/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
@@ -15,8 +15,16 @@ ms.service: azure-automation
 > 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).
 
 > [!Important]
-> - Azure Automation Update Management will  retire on **31 August 2024**. Follow the guidelines for [migration to Azure Update Manager](../../update-manager/guidance-migration-automation-update-management-azure-update-manager.md).
-> - Azure Log Analytics agent, also known as the Microsoft Monitoring Agent (MMA) will be [retired in August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Azure Automation Update Management solution relies on this agent and may encounter issues once the agent is retired as it does not work with Azure Monitoring Agent (AMA). Therefore, if you are using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. All the capabilities of Azure Automation Update management solution will be available on Azure Update Manager before the retirement date. Follow the [guidance](../../update-center/guidance-migration-automation-update-management-azure-update-manager.md) to move your machines and schedules from Automation Update Management to Azure Update Manager.
+> - Azure Automation Update Management has retired on **31 August 2024**. Follow the guidelines for [migration to Azure Update Manager](../../update-manager/guidance-migration-automation-update-management-azure-update-manager.md).
+> - Azure Log Analytics agent, also known as the Microsoft Monitoring Agent (MMA) has [retired in August 2024](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). Azure Automation Update Management solution relies on this agent and may encounter issues once the agent is retired as it does not work with Azure Monitoring Agent (AMA). Therefore, if you are using the Azure Automation Update Management solution, we recommend that you move to Azure Update Manager for your software update needs. All the capabilities of Azure Automation Update management solution will be available on Azure Update Manager before the retirement date. Follow the [guidance](../../update-center/guidance-migration-automation-update-management-azure-update-manager.md) to move your machines and schedules from Automation Update Management to Azure Update Manager.
+
+> [!Important]
+> You can expect the following if you use the capability using Change Tracking & Inventory Log Analytics Agent.
+> - **Functionality**: The functional capabilities of Change Tracking with Log Analytics agent would continue to work till Feb'2025. However, the support will be limited and can lead to potential issues over time.
+> - **Installation**: The ability to configure Change Tracking & Inventory using MMA/OMS agents will be removed from the Azure portal soon.
+>- **Customer Support**: You will not be able to get support through existing channels for Change Tracking & Inventory with MMA/OMS. Microsoft will provide support on a best effort basis.
+> - **New capabilities and support matrix**:  No new capabilities will be added, including functionality for additional Windows or Linux versions.
+> - **File Integrity Monitoring**: Microsoft Defender for Servers Plan 2 will offer a new File Integrity Monitoring (FIM) solution powered by Microsoft Defender for Endpoint (MDE) integration. Microsoft Defender for Cloud recommends disabling FIM over MMA by November 2024 and onboarding your environment to the new FIM version based on Defender for Endpoint. File Integrity Monitoring based on Log Analytics Agent (MMA) is supported till November 2024. [Learn more](https://learn.microsoft.com/azure/defender-for-cloud/prepare-deprecation-log-analytics-mma-agent#migration-from-fim-over-log-analytics-agent-mma).
 
 You can use Update Management in Azure Automation to manage operating system updates for your Windows and Linux virtual machines in Azure, physical or VMs in on-premises environments, and in other cloud environments. You can quickly assess the status of available updates and manage the process of installing required updates for your machines reporting to Update Management. 
 

articles/azure-arc/vmware-vsphere/troubleshoot-guest-management-issues.md

@@ -20,8 +20,6 @@ This article provides information on how to troubleshoot and resolve the issues
 
 ## Troubleshoot issues while enabling Guest Management
 
-**Troubleshoot issues while enabling Guest Management on:**
-
 # [Arc agent installation fails on a domain-joined Linux VM](#tab/linux)
 
 **Error message**: Enabling Guest Management on a domain-joined Linux VM fails with the error message **InvalidGuestLogin: Failed to authenticate to the system with the credentials**.

articles/data-factory/connector-deprecation-plan.md

@@ -7,7 +7,7 @@ ms.service: azure-data-factory
 ms.subservice: data-movement
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 08/23/2024
+ms.date: 08/27/2024
 ---
 
 # Planned connector deprecations for Azure Data Factory
@@ -44,11 +44,11 @@ The following connectors are scheduled for deprecation on December 31, 2024. You
 - [Phoenix](connector-phoenix.md)
 
 
-## Connectors deprecated
+## Connectors that is deprecated
 
 The following connector was deprecated.
 
-- [Amazon Marketplace Web Service (MWS)](connector-amazon-marketplace-web-service.md)
+- [Amazon Marketplace Web Service](connector-amazon-marketplace-web-service.md)
 
 ## Options to replace deprecated connectors
 

articles/iot-hub-device-update/device-update-configuration-file.md

@@ -51,7 +51,7 @@ When installing Debian agent on an IoT Device with a Linux OS, modify the `/etc/
     "do"
   ],
   "iotHubProtocol": "mqtt",
-  "compatPropertyNames":"manufacturer,model,location,language" <The property values must be in lower case only>,
+  "compatPropertyNames":"manufacturer,model,location,environment" <The property values must be in lower case only>,
   "manufacturer": <Place your device info manufacturer here>,
   "model": <Place your device info model here>,
   "agents": [