Source map support for JavaScript applications

Application Insights supports the uploading of source maps to your own Storage Account Blob Container. Source maps can be used to unminify call stacks found on the end to end transaction details page. Any exception sent by the JavaScript SDK or the Node.js SDK can be unminified with source maps.

Unminify a Call Stack by linking with a Storage Account

Create a new storage account and Blob container

If you already have an existing storage account or blob container, you can skip this step.

  1. Create a new storage account
  2. Create a blob container inside your storage account. Be sure to set the "Public access level" to Private, to ensure that your source maps are not publicly accessible.

Your container access level must be set to Private

Push your source maps to your Blob container

You should integrate your continuous deployment pipeline with your storage account by configuring it to automatically upload your source maps to the configured Blob container.

Source maps can be uploaded to your Blob Storage Container with the same folder structure they were compiled & deployed with. A common use case is to prefix a deployment folder with its version, e.g. 1.2.3/static/js/main.js. When unminifying via an Azure Blob container called sourcemaps, it will try to fetch a source map located at sourcemaps/1.2.3/static/js/

If you are using Azure Pipelines to continuously build and deploy your application, add an Azure File Copy task to your pipeline to automatically upload your source maps.

Add an Azure File Copy task to your Pipeline to upload your source maps to Azure Blob Storage

Configure your Application Insights resource with a Source Map storage account

From the end-to-end transaction details page

From the end-to-end transaction details tab, you can click on Unminify and it will display a prompt to configure if your resource is unconfigured.

  1. In the Portal, view the details of an exception that is minified.
  2. Select Unminify.
  3. If your resource has not been configured, a message will appear, prompting you to configure.

From the properties page

If you would like to configure or change the storage account or Blob container that is linked to your Application Insights Resource, you can do it by viewing the Application Insights resource's Properties tab.

  1. Navigate to the Properties tab of your Application Insights resource.
  2. Select Change source map blob container.
  3. Select a different Blob container as your source maps container.
  4. Select Apply.

Reconfigure your selected Azure Blob Container by navigating to the Properties pane


Required Azure role-based access control (Azure RBAC) settings on your Blob container

Any user on the Portal using this feature must be at least assigned as a Storage Blob Data Reader to your Blob container. You must assign this role to anyone else that will be using the source maps through this feature.


Depending on how the container was created, this may not have been automatically assigned to you or your team.

Source map not found

  1. Verify that the corresponding source map is uploaded to the correct blob container
  2. Verify that the source map file is named after the JavaScript file it maps to, suffixed with .map.
    • For example, /static/js/main.4e2ca5fa.chunk.js will search for the blob named
  3. Check your browser's console to see if any errors are being logged. Include this in any support ticket.

Next Steps