What this means:​

• February 29th, 2024
  • Classic components were officially deprecated.
  • Continuous Export was officially deprecated as part of the classic Application Insights deprecation.
• Starting March 1st 2024
  • Classic components remain, and are able to receive and ingestion telemetry.
  • There is no longer any ability to create a Classic Application Insights Component, one can only create Log Analytics Workspace based Component.
  • Classic resources are 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 to migrate to the workspace-based component.
  • A forced migration plan for existing Classic components is being worked on, however what that looks like is still being decided. When details become available they will be added here, so please check back for current status.

What is impacted:​

Application Insights will still exist for Fusion. They will be stored, retained and viewed through the Log Analytics Workspace. A migration of existing Application Insights to reference the new Log Analytics Workspace will need to be performed.

How to migrate:​

Migration through Azure Portal​

This Microsoft article provides information on a manual migration.

During deployment of Fusion a Log Analytics Workspace will already have been created. You will be able to select and associate it to Application Insights. The naming convention will be log-fusion-companyName-environmentType (eg. log-fusion-mycompany-test).

Migration through Azure CLI​

The following Azure CLI command can be executed to migrate an existing Fusion Application Insights. az monitor app-insights component update --app [your-app-insights-resource-name] -g [your_resource_group] --workspace "/subscriptions/[00000000-0000-0000-0000-000000000000]/resourcegroups/[resourcegroupname]/providers/microsoft.operationalinsights/workspaces/[workspacename]"

During deployment of Fusion a Log Analytics Workspace will already have been created. You will be able to select and associate it to Application Insights. The naming convention will be log-fusion-companyName-environmentType (eg. log-fusion-mycompany-test).

When running this command you may be prompted to install the application-insights extension. You can choose to install this when running the command, or add the extension before executing the above command.

To install the extension run: az extension add -n application-insights

Migration through Fusion Terraform​

In the fusion.tf file, under the "azurerm_application_insights" "modelsAppInsights" resource definition, the following line can be added and a terraform apply can be run.

workspace_id = module.fusion_log_analytics_workspace.id