Enable Change Analysis (classic)

  • Article

Important

Azure Monitor Change Analysis (classic) will be retired on October 31, 2025. The experience will be replaced by the Change Analysis API powered by Azure Resource Graph. Learn more about the future of Change Analysis (classic) and how to migrate to Resource Graph.

The Change Analysis (classic) service:

  • Computes and aggregates change data from the data sources mentioned earlier.

  • Provides a set of analytics for users to:

    • Easily move through all resource changes.
    • Identify relevant changes in the troubleshooting or monitoring context.

Register the Microsoft.ChangeAnalysis resource provider with an Azure Resource Manager subscription to make the resource properties and configuration change data available. The Microsoft.ChangeAnalysis resource provider is automatically registered when you do one of two things:

  • Enter any UI entry point, like the web app Diagnose and solve problems tool.
  • Bring up the Change Analysis (classic) standalone tab.

In this guide, you learn the two ways to enable Change Analysis (classic) for functions and web app in-guest changes:

Note

Slot-level enablement for functions or web apps isn't supported at the moment.

Enable functions and web app in-guest change collection via the Change Analysis (classic) portal

For web app in-guest changes, separate enablement is required for scanning code files within a web app. For more information, see Change Analysis (classic) in the Diagnose and solve problems tool section.

Note

You might not immediately see web app in-guest file changes and configuration changes. Prepare for downtime and restart your web app to view changes within 30 minutes. If you still can't see changes, refer to the troubleshooting guide.

  1. Go to the Change Analysis (classic) UI in the portal.

  2. Enable web app in-guest change tracking by using one of two options:

    • On the banner, select Enable now.

      Screenshot that shows the application change options on the banner.

    • On the top menu, select Configure.

      Screenshot that shows the application change options on the top menu.

  3. Toggle on Change Analysis (classic) status for applicable resources and select Save.

    Screenshot that shows the Enable Change Analysis (classic) user interface.

Enable Change Analysis (classic) at scale by using PowerShell

If your subscription includes several web apps, run the following script to enable all web apps in your subscription.

Prerequisites

PowerShell Az module. Follow the instructions in Install the Azure PowerShell module.

Run the following script

# Log in to your Azure subscription
Connect-AzAccount

# Get subscription Id
$SubscriptionId = Read-Host -Prompt 'Input your subscription Id'

# Make Feature Flag visible to the subscription
Set-AzContext -SubscriptionId $SubscriptionId

# Register resource provider
Register-AzResourceProvider -ProviderNamespace "Microsoft.ChangeAnalysis"

# Enable each web app
$webapp_list = Get-AzWebApp | Where-Object {$_.kind -eq 'app'}
foreach ($webapp in $webapp_list)
{
    $tags = $webapp.Tags
    $tags["hidden-related:diagnostics/changeAnalysisScanEnabled"]=$true
    Set-AzResource -ResourceId $webapp.Id -Tag $tags -Force
}

Frequently asked questions

This section provides answers to common questions.

How can I enable Change Analysis (classic) for a web application?

Enable Change Analysis (classic) for web application in-guest changes by using the Diagnose and solve problems tool.

Related content