Enable Snapshot Debugger for .NET apps in Azure App Service

Snapshot Debugger currently supports ASP.NET and ASP.NET Core apps that are running on Azure App Service on Windows service plans.


We recommend that you run your application on the Basic service tier, or higher, when using Snapshot Debugger. For most applications, the Free and Shared service tiers don't have enough memory or disk space to save snapshots. The Consumption tier is not currently available for Snapshot Debugger.

Enable Snapshot Debugger

Snapshot Debugger is pre-installed as part of the App Services runtime, but you need to turn it on to get snapshots for your App Service app. To enable Snapshot Debugger for an app, follow the instructions below:


If you're using a preview version of .NET Core, or your application references Application Insights SDK (directly or indirectly via a dependent assembly), follow the instructions for Enable Snapshot Debugger for other environments to include the Microsoft.ApplicationInsights.SnapshotCollector NuGet package with the application.


Codeless installation of Application Insights Snapshot Debugger follows the .NET Core support policy. For more information about supported runtimes, see .NET Core Support Policy.

After you've deployed your .NET app:

  1. Go to the Azure control panel for your App Service.

  2. Go to the Settings > Application Insights page.

    Screenshot showing the Enable App Insights on App Services portal.

  3. Either follow the instructions on the page to create a new resource or select an existing App Insights resource to monitor your app.

  4. Switch Snapshot Debugger toggles to On.

    Screenshot showing how to add App Insights site extension.

  5. Snapshot Debugger is now enabled using an App Services App Setting.

    Screenshot showing App Setting for Snapshot Debugger.

If you're running a different type of Azure service, here are instructions for enabling Snapshot Debugger on other supported platforms:

Enable Snapshot Debugger for other clouds

Currently the only regions that require endpoint modifications are Azure Government and Microsoft Azure operated by 21Vianet through the Application Insights Connection String.

Connection String Property US Government Cloud China Cloud
SnapshotEndpoint https://snapshot.monitor.azure.us https://snapshot.monitor.azure.cn

For more information about other connection overrides, see Application Insights documentation.

Enable Microsoft Entra authentication for snapshot ingestion

Application Insights Snapshot Debugger supports Microsoft Entra authentication for snapshot ingestion. This means, for all snapshots of your application to be ingested, your application must be authenticated and provide the required application settings to the Snapshot Debugger agent.

As of today, Snapshot Debugger only supports Microsoft Entra authentication when you reference and configure Microsoft Entra ID using the Application Insights SDK in your application.

To turn-on Microsoft Entra ID for snapshot ingestion:

  1. Create and add the managed identity you want to use to authenticate against your Application Insights resource to your App Service.

    1. For System-Assigned Managed identity, see the following documentation.

    2. For User-Assigned Managed identity, see the following documentation.

  2. Configure and turn on Microsoft Entra ID in your Application Insights resource. For more information, see the following documentation

  3. Add the following application setting, used to let Snapshot Debugger agent know which managed identity to use:

For System-Assigned Identity:

App Setting Value

For User-Assigned Identity:

App Setting Value
APPLICATIONINSIGHTS_AUTHENTICATION_STRING Authorization=AD;ClientID={Client ID of the User-Assigned Identity}

Disable Snapshot Debugger

To disable Snapshot Debugger, repeat the steps for enabling. However, switch the Snapshot Debugger toggles to Off.

Azure Resource Manager template

For an Azure App Service, you can set app settings within the Azure Resource Manager template to enable Snapshot Debugger and Profiler. For example:

  "apiVersion": "2015-08-01",
  "name": "[parameters('webSiteName')]",
  "type": "Microsoft.Web/sites",
  "location": "[resourceGroup().location]",
  "dependsOn": [
  "tags": { 
    "[concat('hidden-related:', resourceId('Microsoft.Web/serverfarms', variables('hostingPlanName')))]": "empty",
    "displayName": "Website"
  "properties": {
    "name": "[parameters('webSiteName')]",
    "serverFarmId": "[resourceId('Microsoft.Web/serverfarms', variables('hostingPlanName'))]"
  "resources": [
      "apiVersion": "2015-08-01",
      "name": "appsettings",
      "type": "config",
      "dependsOn": [
        "[concat('AppInsights', parameters('webSiteName'))]"
      "properties": {
        "APPINSIGHTS_INSTRUMENTATIONKEY": "[reference(resourceId('Microsoft.Insights/components', concat('AppInsights', parameters('webSiteName'))), '2014-04-01').InstrumentationKey]",
        "DiagnosticServices_EXTENSION_VERSION": "~3",
        "ApplicationInsightsAgent_EXTENSION_VERSION": "~2"

Not Supported Scenarios

Below you can find scenarios where Snapshot Collector isn't supported:

Scenario Side Effects Recommendation
You're using the Snapshot Collector SDK in your application directly (.csproj) and have enabled the advanced option "Interop". The local Application Insights SDK (including Snapshot Collector telemetry) will be lost and no Snapshots will be available.
Your application could crash at startup with System.ArgumentException: telemetryProcessorTypedoes not implement ITelemetryProcessor.
Learn more about the Application Insights feature "Interop".
If you're using the advanced option "Interop", use the codeless Snapshot Collector injection (enabled through the Azure portal).

Next steps

  • Generate traffic to your application that can trigger an exception. Then, wait 10 to 15 minutes for snapshots to be sent to the Application Insights instance.
  • See snapshots in the Azure portal.
  • For help with troubleshooting Snapshot Debugger issues, see Snapshot Debugger troubleshooting.