![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 60%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,669 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 39%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
@Naik, Siddesh Here is the information you are looking for.
- February 29th, 2024
- classic components will be officially deprecated
- Continuous Export will be officially deprecated as part of the classic Application Insights deprecation.
- classic components will be officially deprecated
- Starting March 1st 2024
- Classic components will still remain and be able to receive and ingestion telemetry
- there will no longer be any ability to create a Classic Application Insights Component, one will only be able to create Log Analytics Workspace based Component.
- Classic resources will be treated like traditional software that is out of support; there will be no fixes, no new compute resources, etc., in other words if there is an issue on the Component side the first step will be to see if that issue exists under a workspace-based component or migrate to the workspace-based component.
- Forced migration plan for existing Classic components is being planned however what and how that looks is still being decided. When details come available they will be added here, so please check back for current status.
