Microsoft will be temporarily pausing all data uploads for legacy Log Analytics agents in Azure Monitor for 12 hours on January 26, 2026 (today in most time zones). This exercise is part of a validation test and will run from 12:00 AM to 12:00 PM PT; it serves as a final warning phase before Microsoft permanently shuts down the associated backend services in March 2026.
Admins need to be prepared for this 12-hour test because any data cached by the legacy agents during this time will be permanently lost and cannot be recovered once uploads resume. The disruption will impact all subscriptions still using older agent configurations rather than the updated Azure Monitor Agent (AMA).
For context, Microsoft plans to perform a backend shutdown of legacy Log Analytics agents on March 2, 2026. The agents were officially retired on August 31, 2024, but the upcoming March date represents a hard deadline for operational data flow and service availability. To migrate over to Azure Monitor Agent, you will need to implement Data Collection Rules (DCRs) which are needed to configure how AMA handles telemetry. Admins can use the AMA migration helper workbook to identify specific virtual machines and resources that are still dependent on the legacy software.
Organizations that don’t migrate before the validation test today will experience immediate gaps in their monitoring logs and security data analysis. This could affect compliance and troubleshooting efforts, but it will also act as a nudge to get the new logging in place. Azure Monitor Agent consolidates several legacy monitoring tools into a single platform, eliminating the risk of duplicate data billing and continued integration with services like Microsoft Defender for Cloud.
The decommissioning of these legacy Log Analytics agents follows a multi-year effort by Microsoft to modernize its monitoring infrastructure and replace aging components. Admins are advised to perform test migrations using the Azure portal to validate new configurations and DCRs function correctly before a full transition. Once AMA is confirmed to be successfully collecting data, admins should manually remove the legacy Log Analytics agents from their resources. Completing this step before the final shutdown in March is necessary to prevent redundant resource usage and ensure a clean environment.