New Outlook Sensitivity Labels: How It Works for Classic Outlook Users

If you are a Classic Outlook user, you may have noticed that Sensitivity Labels behave differently in the new Outlook for Windows. The new Outlook applies sensitivity labels through a modern cloud-based platform, while Classic Outlook uses a local add-in or built-in Microsoft 365 integration. This article explains the technical differences between the two versions, how sensitivity labels are applied and enforced, and what Classic Outlook users need to know before switching to the new Outlook. You will learn the exact steps to configure and verify label policies, and how to handle common compatibility issues.

How Sensitivity Labels Work in New Outlook vs Classic Outlook

Sensitivity labels are a Microsoft 365 compliance feature that lets you classify and protect email content based on data sensitivity. In both new and Classic Outlook, labels are defined in the Microsoft 365 Compliance Center and then published to users through label policies. The difference lies in the client-side infrastructure that reads and enforces these labels.

The new Outlook for Windows is a web-based client that connects directly to Microsoft 365 cloud services. It uses the built-in sensitivity labeling engine from the Microsoft 365 web apps. This means no additional software or add-in is required. Labels appear as a button in the ribbon, and they apply instantly to messages and attachments.

Classic Outlook relies on the Azure Information Protection (AIP) Unified Labeling client or the built-in Microsoft 365 sensitivity labeling feature that was introduced in Outlook version 2205. If your organization uses the Unified Labeling client, it must be installed and enabled as a COM add-in. If you use the built-in labeling, it is controlled by a registry key or Group Policy setting. In both cases, Classic Outlook processes labels locally and syncs with the cloud.

Prerequisites for Sensitivity Labels

Before labels appear in either version, the following must be in place:

• A Microsoft 365 E3 or E5 subscription (or equivalent standalone plans).
• Sensitivity labels created and published in the Microsoft 365 Compliance Center.
• Users assigned a license that includes Azure Information Protection.
• For Classic Outlook: either the Unified Labeling client (version 2.9 or later) or Outlook build 2205 or later with built-in labeling enabled.
• For new Outlook: no additional client software is required; it works with the same cloud policies.

Steps to Configure Sensitivity Labels for Both Outlook Versions

These steps assume you are an administrator with access to the Microsoft 365 Compliance Center. If you are an end user, share this with your IT team.

1. Create and publish sensitivity labels in the Compliance Center
   Go to Microsoft 365 Compliance Center > Solutions > Information Protection > Labels. Click Create a label and follow the wizard to define the label name, description, and protection settings (encryption, content marking, or both). After creating the label, click Publish labels and select the label policy name, labels to include, and users or groups. Publish the policy.
2. Verify label policy assignment for users
   In the Compliance Center, go to Information Protection > Label policies. Select your published policy and check the assigned users. If users are missing, edit the policy and add them. Wait up to 24 hours for the policy to propagate, or force sync by running Start-SyncPolicy in the Exchange Online PowerShell.
3. Enable the Unified Labeling client in Classic Outlook (if using the add-in)
   Open Classic Outlook. Go to File > Options > Add-ins. In the Manage dropdown, select COM Add-ins and click Go. Check the box for Microsoft Office Sensitivity Labeling and click OK. Restart Outlook. If the add-in is missing, download and install the Unified Labeling client from the Microsoft Download Center.
4. Enable built-in labeling in Classic Outlook (Outlook 2205 and later)
   If you prefer not to use the add-in, enable built-in labeling via Group Policy: set the policy Enable Sensitivity Label support in Outlook to Enabled. The registry path is HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Common\Identity with DWORD value EnableADAL = 1 and DisableAADIntegration = 0. Restart Outlook. Labels will appear in the ribbon.
5. Apply a sensitivity label in new Outlook
   Open the new Outlook. Compose a new email. On the ribbon, click the Sensitivity button and select a label from the dropdown. The label applies immediately to the message and any attachments that support labeling (Office documents).
6. Apply a sensitivity label in Classic Outlook
   Open Classic Outlook. Compose a new email. On the ribbon, click the Sensitivity button (or File > Info > Set Sensitivity). Select a label. The label is applied after you send the message, or immediately if the Unified Labeling client is active.

If Sensitivity Labels Do Not Appear in Either Version

Labels are missing from the ribbon in new Outlook

This usually means the label policy has not propagated to the user. Check that the user is assigned to the published label policy in the Compliance Center. Also verify that the user has a valid Microsoft 365 E3 or E5 license with Azure Information Protection. In the new Outlook, go to File > Options > General > Sensitivity and ensure the feature is not disabled. If it is grayed out, contact your administrator.

Labels are missing from the ribbon in Classic Outlook

If you use the Unified Labeling client, open Classic Outlook and go to File > Options > Add-ins > COM Add-ins. Confirm that Microsoft Office Sensitivity Labeling is checked. If it is not listed, reinstall the Unified Labeling client from the Microsoft Download Center. If you use built-in labeling, check that the registry key or Group Policy is correctly configured. Also ensure that Outlook is updated to version 2205 or later.

Labels apply but encryption does not work

In new Outlook, encryption is handled by the cloud. If a label has encryption settings, they are enforced when the message is sent. In Classic Outlook, the Unified Labeling client must be able to connect to Azure Information Protection. Check that the user can authenticate to Azure AD. In Classic Outlook, go to File > Account Settings > Manage Profiles and verify the user profile is connected to the correct Microsoft 365 tenant. If encryption fails, the label may still appear but will not protect the message.

Labels do not sync between new and Classic Outlook

Labels are stored in the cloud, so they should appear the same in both versions. If a label is applied in new Outlook, it will be visible in Classic Outlook only if the user opens the same message in Classic Outlook. However, the label button in Classic Outlook may not show the same label until you click the Sensitivity button again. This is a display refresh issue. Close and reopen the message to see the correct label.

New Outlook vs Classic Outlook: Sensitivity Label Feature Comparison

Item	New Outlook for Windows	Classic Outlook
Client type	Web-based (Microsoft 365 cloud)	Desktop application with local processing
Labeling engine	Built-in cloud engine from Microsoft 365	Unified Labeling client add-in or built-in (Outlook 2205+)
Additional software required	None	Unified Labeling client (if not using built-in)
Label application method	Ribbon button: Sensitivity	Ribbon button: Sensitivity or File > Info > Set Sensitivity
Encryption support	Full cloud-based encryption	Requires AIP client connection to Azure
Attachment labeling	Applies to Office documents automatically	Applies only if Unified Labeling client is active
Policy sync delay	Up to 24 hours (cloud propagation)	Up to 24 hours plus local client sync

Now you understand the differences between how sensitivity labels work in new Outlook and Classic Outlook. Start by verifying that your label policies are correctly published to all users in the Microsoft 365 Compliance Center. If you are a Classic Outlook user, enable the Unified Labeling client or update to Outlook 2205 to use built-in labeling. For administrators, consider testing the new Outlook with a pilot group before migrating all users. The new Outlook eliminates the need for the Unified Labeling client, which reduces deployment complexity.