What is the Azure Information Protection classic scanner?

Applies to: Azure Information Protection, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2


To provide a unified and streamlined customer experience, Azure Information Protection client (classic) and Label Management in the Azure Portal are being deprecated as of March 31, 2021. This time-frame allows all current Azure Information Protection customers to transition to our unified labeling solution using the Microsoft Information Protection Unified Labeling platform. Learn more in the official deprecation notice.

If you're using the unified labeling client, see What is the Azure Information Protection unified labeling scanner?.

Use the information in this section to learn about the Azure Information Protection scanner, and then how to successfully install, configure, run and if necessary, troubleshoot it.

The AIP scanner runs as a service on Windows Server and lets you discover, classify, and protect files on the following data stores:

  • UNC paths for network shares that use the Server Message Block (SMB) protocol.

  • SharePoint document libraries and folder for SharePoint Server 2019 through SharePoint Server 2013.


To scan and label files on cloud repositories, use Cloud App Security instead of the scanner.

Azure Information Protection classic scanner overview

The AIP scanner can inspect any files that Windows can index. If you've configured labels that apply automatic classification, the scanner can label discovered files to apply that classification, and optionally apply or remove protection.

The following image shows the AIP scanner architecture, where the scanner discovers files across your on-premises and SharePoint servers.

Azure Information Protection classic scanner architecture

To inspect your files, the scanner uses IFilters installed on the computer. To determine whether the files need labeling, the scanner uses the Microsoft 365 built-in data loss prevention (DLP) sensitivity information types and pattern detection, or Microsoft 365 regex patterns.

The scanner uses the Azure Information Protection client, and can classify and protect the same types of files as the client. For more information, see File types supported by the Azure Information Protection client.

Do any of the following to configure your scans as needed:

  • Run the scanner in discovery mode only to create reports that check to see what happens when your files are labeled.
  • Run the scanner to discover files with sensitive information, without configuring labels that apply automatic classification.
  • Run the scanner automatically to apply labels as configured.
  • Define a file types list to specify specific files to scan or to exclude.


The scanner does not discover and label in real time. It systematically crawls through files on data stores that you specify. Configure this cycle to run once, or repeatedly.

AIP scanning process

When scanning files, the AIP scanner runs through the following steps:

1. Determine whether files are included or excluded for scanning

2. Inspect and label files

3. Label files that can't be inspected


For more information, see Files not labeled by the scanner.

1. Determine whether files are included or excluded for scanning

The scanner automatically skips files that are excluded from classification and protection, such as executable files and system files. For more information, see File types that are excluded from classification and protection.

The scanner also considers any file lists explicitly defined to scan, or exclude from scanning. File lists apply for all data repositories by default, and can also be defined for specific repositories only.

To define file lists for scanning or exclusion, use the File types to scan setting in the content scan job. For example:

Configure file types to scan for the Azure Information Protection scanner

For more information, see Deploying the Azure Information Protection scanner to automatically classify and protect files.

2. Inspect and label files

After identifying excluded files, the scanner filters again to identify files supported for inspection.

These additional filters are the same ones used by the operating system for Windows Search and indexing, and require no additional configuration. Windows IFilter is also used to scan file types that are used by Word, Excel, and PowerPoint, and for PDF documents and text files.

For a full list of file types supported for inspection, and additional instructions for configuring filters to include .zip and .tiff files, see File types supported for inspection.

After inspection, supported file types are labeled using the conditions specified for your labels. If you're using discovery mode, these files can either be reported to contain the conditions specified for your labels, or reported to contain any known sensitive information types.

3. Label files that can't be inspected

For any file types that can't be inspected, the AIP scanner applies the default label in the Azure Information Protection policy, or the default label configured for the scanner.

Files not labeled by the scanner

The AIP scanner cannot label files under the following circumstances:

  • When the label applies classification, but not protection, and the file type does not support classification-only by the client. For more information, see Classic client file types.

  • When the label applies classification and protection, but the scanner does not support the file type.

    By default, the scanner protects only Office file types, and PDF files when they are protected by using the ISO standard for PDF encryption.

    Other types of files can be added for protection when you change the types of files to protect.

Example: After inspecting .txt files, the scanner can't apply a label that's configured for classification only, because the .txt file type doesn't support classification only.

However, if the label is configured for both classification and protection, and the .txt file type is included for the scanner to protect, the scanner can label the file.

Next steps

For more information about deploying the scanner, see the following articles:

More information: