Делите путем

Automatically apply a sensitivity label to Microsoft 365 data

  • Чланак

Microsoft 365 licensing guidance for security & compliance.

Note

For information about automatically applying a sensitivity label to data stored outside Microsoft 365 and in the data map, see Labeling in Microsoft Purview Data Map.

When you create a sensitivity label, you can automatically assign that label to Microsoft 365 items such as files and emails when the data matches conditions that you specify.

This ability to apply sensitivity labels to content automatically is important because:

  • You don't need to train your users when to use each of your classifications.

  • You don't need to rely on users to classify all content correctly.

  • Users no longer need to know about your policies—they can instead focus on their work.

There are two different methods for automatically applying a sensitivity label to content in Microsoft 365:

  • Client-side labeling when users edit documents or compose (also reply or forward) emails: Use a label that's configured for auto-labeling for files and emails (includes Word, Excel, PowerPoint, and Outlook).

    This method supports recommending a label to users, as well as automatically applying a label. But in both cases, the user decides whether to accept or reject the label, to help ensure the correct labeling of content. This client-side labeling has minimal delay for documents because the label can be applied even before the document is saved. However, not all client apps support auto-labeling.

    For configuration instructions, see How to configure auto-labeling for Office apps on this page.

  • Service-side labeling when content is already saved (in SharePoint or OneDrive) or emailed (processed by Exchange Online): Use an auto-labeling policy.

    You might also hear this method referred to as auto-labeling for data at rest (documents in SharePoint and OneDrive) and data in transit (email that is sent or received by Exchange). For Exchange, it doesn't include emails at rest (mailboxes).

    Because this labeling is applied by services rather than by applications, you don't need to worry about what apps users have and what version. As a result, this capability is immediately available throughout your organization and suitable for labeling at scale. Auto-labeling policies don't support recommended labeling because the user doesn't interact with the labeling process. Instead, the administrator runs the policies in simulation to help ensure the correct labeling of content before actually applying the label.

    For configuration instructions, see How to configure auto-labeling policies for SharePoint, OneDrive, and Exchange on this page.

    Specific to auto-labeling for SharePoint and OneDrive:

    • PDF documents and Office files for Word (.docx), PowerPoint (.pptx), and Excel (.xlsx) are supported.
      • These files can be auto-labeled at rest before or after the auto-labeling policies are created. Files can't be auto-labeled if they're part of an open session (the file is open).
      • Currently, attachments to list items aren't supported and won't be auto-labeled.
    • Maximum of 100,000 automatically labeled files in your tenant per day.
    • Maximum of 100 auto-labeling policies per tenant, each targeting up to 100 locations (SharePoint sites or OneDrive individual users or groups) when you specify specific locations by using the Included or Excluded options. If you keep the default configuration of All, this configuration is exempt from the 100 locations maximum.
    • Existing values for modified, modified by, and the date aren't changed as a result of auto-labeling policies—for both simulation mode and when labels are applied.
    • When the label applies encryption, the Rights Management issuer and Rights Management owner is the account that last modified the file.

    Specific to auto-labeling for Exchange:

    • PDF attachments and Office attachments are scanned for the conditions you specify in your auto-labeling policy. When there's a match, the email is labeled but not the attachment.
      • For PDF files, if the label applies encryption, these files are encrypted by using Message encryption when your tenant is enabled for PDF attachments.
      • For these Office files, Word, PowerPoint, and Excel are supported. If the label applies encryption and these files are unencrypted, they're now encrypted by using Message encryption. The encryption settings are inherited from the email.
    • To label and protect emails that contain Teams voicemail messages, see the configuration instructions in Enable protected voicemail in your organization.
    • If you have Exchange mail flow rules or Microsoft Purview Data Loss Prevention (DLP) policies that apply IRM encryption: When content is identified by these rules or policies and an auto-labeling policy, the label is applied. If that label applies encryption, the IRM settings from the Exchange mail flow rules or DLP policies are ignored. However, if that label doesn't apply encryption, the IRM settings from the mail flow rules or DLP policies are applied in addition to the label.
    • Email that has IRM encryption with no label will be replaced by a label with any encryption settings when there's a match by using auto-labeling.
    • Incoming email is labeled when there's a match with your auto-labeling conditions. For this outcome to apply to senders outside your organization, the Exchange location must be set to All included and None excluded. If the label is configured for encryption:
      • That encryption is always applied when the sender is from your organization.
      • By default, that encryption isn't applied when the sender is outside your organization but can be applied by configuring Additional settings for email and specifying a Rights Management owner.
    • When the label applies encryption, the Rights Management issuer and Rights Management owner is the person who sends the email when the sender is from your own organization. When the sender is outside your organization, you can specify a Rights Management owner for incoming email that's labeled and encrypted by your policy.
    • If the label is configured to apply content markings with variables, be aware that for incoming email, this configuration can result in displaying the names of people outside your organization.

Note

For some new customers, we're offering the automatic configuration of default auto-labeling settings for both client-side labeling and service-side labeling. Even if you're not eligible for this automatic configuration, you might find it useful to reference their configuration. For example, you can manually configure existing labels and create your own auto-labeling policies with the same settings to help accelerate your labeling deployment.

For more information, see Default labels and policies for Microsoft Purview Information Protection.

Tip

If you're not an E5 customer, use the 90-day Microsoft Purview solutions trial to explore how additional Purview capabilities can help your organization manage data security and compliance needs. Start now at the Microsoft Purview compliance portal trials hub. Learn details about signing up and trial terms.

Compare auto-labeling for Office apps with auto-labeling policies

Use the following table to help you identify the differences in behavior for the two complementary automatic labeling methods:

Feature or behavior Label setting: Auto-labeling for files and emails Policy: Auto-labeling
App dependency Yes (minimum versions) No *
Restrict by location No Yes
Conditions: Sharing options and additional options for email No Yes
Conditions: Exceptions No Yes
Support for PDF files No Yes
Support for images No Yes
Recommendations, policy tooltip, and user overrides Yes No
Simulation mode No Yes
Exchange attachments checked for conditions No Yes
Apply visual markings Yes Yes (email only)
Override IRM encryption applied without a label Yes if the user has the minimum usage right of Export Yes (email only)
Label incoming email No Yes
Assign a Rights Management owner for emails sent from another organization No Yes
For emails, replace existing label that has same or lower priority No Yes (configurable)

* Auto-labeling isn't currently available in all regions because of a backend Azure dependency. If your tenant can't support this functionality, the Auto-labeling page isn't visible in the Microsoft Purview portal or the Microsoft Purview compliance portal. For more information, see Azure dependency availability by country.

How multiple conditions are evaluated when they apply to more than one label

The labels are ordered for evaluation according to their position that you specify in the Microsoft Purview portal or the Microsoft Purview compliance portal: The label positioned first has the lowest position (least sensitive, so lowest priority) and the label positioned last has the highest position (most sensitive, so highest priority). The label with the highest order number is selected.

This behavior is also true for service-side auto-labeling (auto-labeling policies) when sublabels share the same parent label: If after evaluation and ordering, more than one sublabel from the same parent label meets the auto-labeling conditions, the sublabel with the highest order number is selected and applied.

However, the behavior is a little different for client-side auto-labeling (auto-labeling settings in the label). If multiple sublabels from the same parent label match the conditions:

  • If a file is not already labeled, the highest order sublabel that's configured for automatic labeling is always selected, rather than the highest order sublabel that's configured for recommended labeling. If none of these sublabels are configured for automatic labeling but only recommended labeling, the highest order sublabel is selected and recommended.

  • If a file is already labeled with a sublabel from the same parent, no action is taken and the existing sublabel remains. This behavior applies even if the existing sublabel was a default label or automatically applied.

For more information about label priority, see Label priority (order matters).

Considerations for label configurations

The following considerations apply to both client-side labeling and service-side labeling.

Remember, you can't apply a parent label (a label with sublabels) to content. Make sure that you don't configure a parent label to be auto-applied or recommended in Office apps, and don't select a parent label for an auto-labeling policy. If you do, the parent label won't be applied to content.

To use automatic labeling with sublabels, make sure you publish both the parent label and the sublabel.

For more information on parent labels and sublabels, see Sublabels (grouping labels).

Label scoping that excludes files or emails

To automatically apply a sensitivity label to content, the label's scope must include Files & other data assets to automatically apply a label to documents, and Emails to automatically apply a label to emails.

For more information when you select just one of these label scopes, see Scope labels to just files or emails.

Will an existing label be overridden?

Although there are some scenarios where a sensitivity label can be overridden with another sensitivity label, an auto-labeling policy will never remove a sensitivity label so the content becomes unlabeled.

Default behavior whether automatic labeling will override an existing label:

  • When content has been manually labeled, that label won't be replaced by automatic labeling.

  • Automatic labeling will replace a lower priority sensitivity label that was automatically applied, but not a higher priority label.

    Tip

    For example, the sensitivity label at the top of the list in the Microsoft Purview portal or the Microsoft Purview compliance portal is named Public with an order number (priority) of 0, and the sensitivity label at the bottom of the list is named Highly Confidential with an order number (priority of 4). The Highly Confidential label can override the Public label but not the other way around.

For email auto-labeling policies only, you can select a setting to always override an existing sensitivity label, regardless of how it was applied.

Existing label Override with label setting: Auto-labeling for files and emails Override with policy: Auto-labeling
Manually applied, any priority Word, Excel, PowerPoint: No

Outlook: No		 SharePoint and OneDrive: No

Exchange: No by default, but configurable
Automatically applied or default label from policy, lower priority Word, Excel, PowerPoint: Yes *

Outlook: Yes *		 SharePoint and OneDrive: Yes

Exchange: Yes
Automatically applied or default label from policy, higher priority Word, Excel, PowerPoint: No

Outlook: No		 SharePoint and OneDrive: No

Exchange: No by default, but configurable

* There's an exception for sublabels that share the same parent label

The configurable setting for email auto-labeling policies is on the Additional settings for email page. This page displays after you've selected a sensitivity label for an auto-labeling policy that includes the Exchange location.

How to configure auto-labeling for Office apps

Check the minimum versions required for automatic labeling in Office apps.

The auto-labeling settings for Office apps are available when you create or edit a sensitivity label. Make sure the label scope Files & other data assets is selected to auto-label documents, and Emails is selected to auto-label emails. For example:

Sensitivity label scope options for Items that include Files and Email.

As you move through the configuration, you see the Auto-labeling for files and emails page where you can choose from a list of sensitive info types or trainable classifiers:

Label conditions for auto-labeling in Office apps.

When this sensitivity label is automatically applied, the user sees a notification in their Office app. For example:

Notification that a document had a label applied automatically.

Configuring sensitive info types for a label

When you select the Sensitive info types option, you see the same list of sensitive information types as when you create a data loss prevention (DLP) policy. So you can, for example, automatically apply a Highly Confidential label to any content that contains customers' personal information, such as credit card numbers, social security numbers, or passport numbers:

Sensitive info types for auto-labeling in Office apps.

Similarly to when you configure DLP policies, you can then refine your condition by changing the instance count and match accuracy. For example:

Options for match accuracy and instance count.

You can learn more about confidence levels from the DLP documentation: More on confidence levels

Important

Sensitive information types have two different ways of defining the max unique instance count parameters. To learn more, see Instance count supported values for SIT.

Also similarly to DLP policy configuration, you can choose whether a condition must detect all sensitive information types, or just one of them. And to make your conditions more flexible or complex, you can add groups and use logical operators between the groups.

Custom sensitive information types with Exact Data Match

You can configure a sensitivity label to use exact data match based sensitive information types for custom sensitive information types. However, currently, you must also specify at least one sensitive information type that doesn't use EDM. For example, one of the built-in sensitive information types, such as Credit card number.

If you configure a sensitivity label with only EDM for your sensitive information type conditions, the auto-labeling setting is automatically turned off for the label.

Configuring trainable classifiers for a label

If you use this option with Microsoft 365 Apps for Windows version 2106 or lower, or Microsoft 365 Apps for Mac version 16.50 or lower, make sure you've published in your tenant at least one other sensitivity label that's configured for auto-labeling and the sensitive info types option. This requirement isn't necessary when you use later versions on these platforms.

When you select the Trainable classifiers option, select one or more of the pretrained or custom trainable classifiers:

Options for trainable classifiers and sensitivity labels.

The available pretrained classifiers are often updated, so there might be more entries to select than the ones displayed in this screenshot.

For more information about these classifiers, see Learn about trainable classifiers.

Recommend that the user applies a sensitivity label

If you prefer, you can recommend to your users that they apply the label. With this option, your users can accept the classification and any associated protection, or dismiss the recommendation if the label isn't suitable for their content.

Option for recommending a sensitivity label to users.

When you use built-in labeling with the desktop versions of Word, users have an additional option to Show sensitive content with the recommended label prompt. When they select this button, the Editor pane steps the user through each detection. The user can then remove the sensitive data or leave it with a better understanding of why the sensitivity label was recommended. When they have this extra information, users have more confidence to select the Apply sensitivity button. For example:

Prompt to apply a recommended label and show sensitive content.

This example shows the default recommended label prompt, but as with automatic labeling, you can customize this text to be more meaningful or specific for your users. For example, include your organization's name or reference your IT department to increase visibility and give users more confidence that this isn't a generic message that might not be applicable to them.

Tip

Although recommending a sensitivity label interrupts a user's workflow, it's a very efficient way to educate users in the moment about sensitive data that they work with. To see this in action, watch the video: Automatically Classify & Protect Documents & Data

Recommended labeling is particularly powerful when it's coupled with this option to step the users through each instance of sensitive content that's detected. It can lead to more accurate labeling, not just for the immediate item, but also for future items that require manual labeling, or for modified items that might now need relabeling.

Not all Office apps support automatic and recommended labeling. For more information, see Support for sensitivity label capabilities in apps.

Other considerations:

  • You can't use automatic labeling for documents and emails that were previously manually labeled, or previously automatically labeled with a higher sensitivity. Remember, you can only apply a single sensitivity label to a document or email (in addition to a single retention label).

  • You can't use recommended labeling for documents or emails that were previously labeled with a higher sensitivity. When the content's already labeled with a higher sensitivity, the user won't see the prompt with the recommendation and policy tip.

  • For recommended labels in the desktop versions of Word, the sensitive content that triggered the recommendation is flagged so that users can review and remove the sensitive content instead of applying the recommended sensitivity label.

For details about how these labels are applied in Office apps, example screenshots, and how sensitive information is detected, see Automatically apply or recommend sensitivity labels to your files and emails in Office.

Convert your label settings into an auto-labeling policy

If the label includes sensitive info types for the configured conditions, you'll see an option at the end of the label creation or editing process to automatically create an auto-labeling policy that's based on the same auto-labeling settings.

However, if the label contains trainable classifiers as a label condition:

  • When the label conditions contain just trainable classifiers, you won't see the option to automatically create an auto-labeling policy.

  • When the label conditions contain trainable classifiers and sensitivity info types, an auto-labeling policy will be created for just the sensitive info types.

Although an auto-labeling policy is automatically created for you by auto-populating the values that you would have to select manually if you created the policy from scratch, you can still view and edit the values before they are saved.

By default, all locations for SharePoint, OneDrive, and Exchange are included in the auto-label policy, and when the policy is saved, it runs in simulation mode. There's no check that you've enabled sensitivity labels for Office files in SharePoint and OneDrive, which is one of the prerequisites for auto-labeling to apply to content in SharePoint and OneDrive.

How to configure auto-labeling policies for SharePoint, OneDrive, and Exchange

Note

Don't use Exchange auto-labeling policies to send encrypted emails for mass mailing distributions. These policies aren't designed for this purpose and can result in sending failures and non-delivery receipts. For this scenario, the label setting to automatically send emails is more suitable.

Make sure you're aware of the prerequisites before you configure auto-labeling policies.

Prerequisites for auto-labeling policies

  • Simulation mode:

    • Auditing for Microsoft 365 must be turned on. If you need to turn on auditing or you're not sure whether auditing is already on, see Turn audit log search on or off.
    • To view file or email contents in the source view, you must have the Data Classification Content Viewer role, which is included in the Content Explorer Content Viewer role group, or Information Protection and Information Protection Investigators role groups. Without the required role, you don't see the preview pane when you select an item from the Items to review tab. Global admins don't have this role by default.

  • To auto-label files in SharePoint and OneDrive:

    • You have enabled sensitivity labels for Office files in SharePoint and OneDrive.
    • At the time the auto-labeling policy runs, the file mustn't be open by another process or user. A file that's checked out for editing falls into this category.
    • If you plan to use sensitive information types:
      • The sensitive information types you select will apply only to content that's created or modified after these information types are created or modified. This restriction applies to all custom sensitive information types and any new built-in information types.
      • To test new custom sensitive information types, create them before you create your auto-labeling policy, and then create new documents with sample data for testing.
    • If you plan to use document properties as a condition (Document property is), this option uses SharePoint managed properties in the same way as they are used for DLP policies. Use exact string matches; regex patterns aren't supported. For more information about managed properties as a search method, see Manage the search schema in SharePoint.

  • One or more sensitivity labels created and published (to at least one user) that you can select for your auto-labeling policies. For these labels:

    • It doesn't matter if the auto-labeling in Office apps label setting is turned on or off, because that label setting supplements auto-labeling policies, as explained in the introduction.
    • If the labels you want to use for auto-labeling are configured to use visual markings (headers, footers, watermarks), note that these aren't applied to documents.
    • If the labels apply encryption:
      • When the auto-labeling policy includes locations for SharePoint or OneDrive, the label must be configured for the Assign permissions now setting, and User access to content expires must be set to Never.
      • When the auto-labeling policy is just for Exchange, the label can be configured for either Assign permissions now or Let users assign permissions (for the Do Not Forward or Encrypt-Only options). You can't auto-apply a label that's configured to apply S/MIME protection.

Learn about simulation mode

Simulation mode is supported for auto-labeling policies and woven into the workflow. You can't automatically label documents and emails until your policy has run at least one simulation.

Simulation mode supports up to 4,000,000 matched files. If more than this number of files are matched from an auto-labeling policy, you can't turn on the policy to apply the labels. In this case, you must reconfigure the auto-labeling policy so that fewer files are matched, and rerun simulation. This maximum of 4,000,000 matched files applies to simulation mode only and not to an auto-labeling policy that's already turned on to apply sensitivity labels.

Workflow for an auto-labeling policy:

  1. Create and configure an auto-labeling policy.

  2. Run the policy in simulation mode, which can take 12 hours to complete. The completed simulation triggers an email notification that's sent to the user configured to receive activity alerts.

  3. Review the results, and if necessary, refine your policy. For example, you might need to edit the policy rules to reduce false positives, or remove some sites so that the number of matched files doesn't exceed 4,000,000. Rerun simulation mode and wait for it to complete again.

  4. Repeat step 3 as needed.

  5. Deploy in production.

The simulated deployment runs like the WhatIf parameter for PowerShell, for a specific point in time. You see results reported as if the auto-labeling policy had applied your selected label, using the rules that you defined. You can then refine your rules for accuracy if needed, and rerun the simulation. However, because auto-labeling for Exchange applies to emails that are sent and received, rather than emails stored in mailboxes, don't expect results for email in a simulation to be consistent unless you can send and receive the exact same email messages.

Simulation mode also lets you gradually increase the scope of your auto-labeling policy before deployment. For example, you might start with a single location, such as a SharePoint site, with a single document library. Then, with iterative changes, increase the scope to multiple sites, and then to another location, such as OneDrive.

Finally, you can use simulation mode to provide an approximation of the time needed to run your auto-labeling policy, to help you plan and schedule when to run it without simulation mode.

Note

If the simulation results don't include files that you expect, based on your configured auto-policy conditions and the current file contents, it might be because the files were updated after the simulation ran. Check if the files were updated and run simulation again to confirm they will be labeled.

Creating an auto-labeling policy

For this configuration, you can use either the Microsoft Purview portal or the Microsoft Purview compliance portal.

  1. Depending on the portal you're using, navigate to one of the following locations:

    Note

    If you don't see the option for auto-labeling, this functionality isn't currently available in your region because of a backend Azure dependency. For more information, see Azure dependency availability by country.

  2. Select + Create auto-labeling policy. This starts the New policy configuration:

    New policy configuration for auto-labeling.

  3. For the Choose a label to auto-apply page: Select + Choose a label, select a label from the Choose a sensitivity label pane, and then select Next.

  4. For the page Choose info you want this label applied to: Select one of the templates, such as Financial or Privacy. You can refine your search by using the search or dropdown box for countries or regions. Or, select Custom policy if the templates don't meet your requirements. Select Next.

  5. For the page Name your auto-labeling policy: Provide a unique name, and optionally a description to help identify the automatically applied label, locations, and conditions that identify the content to label.

  6. For the page Assign admin units: If your organization is using administrative units in Microsoft Entra ID, auto-labeling policies for Exchange and OneDrive can be automatically restricted to specific users by selecting administrative units. If your account has been assigned administrative units, you must select one or more administrative units.

    If you don't want to restrict the policy by using administrative units, or your organization hasn't configured administrative units, keep the default of Full directory.

    Note

    If you are editing an existing policy and change the administrative units, you must now reconfigure the locations in the next step.

  7. For the page Choose locations where you want to apply the label: Select and specify locations for Exchange, SharePoint, and OneDrive. If you don't want to keep the default of All included for your chosen locations, select the link to choose specific instances to include, or select the link to choose specific instances to exclude. Then select Next.

    Choose locations page for auto-labeling configuration.

    Note

    For organizations that are using administrative units:

    • If you selected the option to use administrative units in the previous step, the location for SharePoint sites becomes unavailable. Only auto-labeling policies for Exchange and OneDrive support administrative units.
    • When you use the Included or Excluded options, you will see and can select only users from the administrative units selected in the previous step.

    If you use the Included or Excluded options:

    • For the Exchange location, the policy is applied according to the sender address of the recipients specified. Most of the time, you'll want to keep the default of All included with None excluded. This configuration is suitable even if you're testing for a subset of users. Instead of specifying your subset of users here, use the advanced rules in the next step to configure conditions to include or exclude recipients in your organization. Otherwise, when you change the default settings here:

      • If you change the default of All included and instead, choose specific users or groups, email sent from outside your organization will be exempt from the policy.
      • If you keep the default of All included but specify users or groups to exclude, email that these excluded users send will be exempt from the policy, but not email that they receive.

    • For the OneDrive location, you must specify users or groups. Previously, you had to specify sites by URLs. Any existing OneDrive URL sites in auto-labeling policies will continue to work but before you can specify new OneDrive locations, or for restricted admins, you must first delete any existing site URLs. Groups supported: distribution groups, Microsoft 365 groups, mail-enabled security groups, and security groups.

  8. For the Set up common or advanced rules page: Keep the default of Common rules to define rules that identify content to label across all your selected locations. If you need different rules per location, including some rules that are only available for Exchange, or SharePoint sites and OneDrive accounts, select Advanced rules. Then select Next.

    The rules use conditions that include sensitive information types, trainable classifiers, sharing options, and other conditions:

    • To select a sensitive information type or trainable classifier as a condition, under Content contains, select Add, and then choose Sensitive info types or Trainable classifiers.
    • To select sharing options as a condition, under Content is shared, choose either only with people inside my organization or with people outside my organization.
    • Other conditions that you can select:

    If your location is Exchange and you selected Advanced rules, there are additional conditions that you can select:

    • Sender IP address is
    • Recipient domain is
    • Recipient is
    • Attachment is password protected
    • Any email attachment's content could not be scanned
    • Any email attachment's content didn't complete scanning
    • Header matches patterns
    • Subject matches patterns
    • Recipient address contains words
    • Recipient address matches patterns
    • Sender address matches patterns
    • Sender domain is
    • Recipient is a member of
    • Sender is

    If your location is SharePoint sites or OneDrive accounts and you selected Advanced rules, there is one other condition that you can select:

    • Document created by

  9. Depending on your previous choices, you'll now have an opportunity to create new rules by using conditions and exceptions.

    The configuration options for sensitive information types are the same as those you select for auto-labeling for Office apps. If you need more information, see Configuring sensitive info types for a label.

    When you've defined all the rules you need, and confirmed their status is on, select Next to move on to choosing a label to auto-apply.

  10. If your policy includes the Exchange location: Specify optional configurations on the Additional settings for email page:

    • Automatically replace existing labels that have the same or lower priority: Applicable for both incoming and outgoing emails, when you select this setting, it ensures a matching sensitivity label will always be applied. If you don't select this setting, a matching sensitivity label won't be applied to emails that have an existing sensitivity label with a higher priority or that were manually labeled.

    • Apply encryption to email received from outside your organization: When you select this option, you must assign a Rights Management owner to ensure that an authorized person in your organization has Full Control usage rights for emails sent from your outside your organization and your policy labels with encryption. This role might be needed to later remove the encryption, or assign different usage rights for users in your organization.

      For Assign a Rights Management owner, specify a single user by an email address that's owned by your organization. Don't specify a mail contact, a shared mailbox, or any group type, because these aren't supported for this role.

  11. For the Decide if you want to test out the policy now or later page: Select Run policy in simulation mode if you're ready to run the auto-labeling policy now, in simulation mode. Then decide whether to automatically turn on the policy if it's not edited for 7 days:

    Test out the configured auto-labeling policy.

    If you're not ready to run simulation, select Leave policy turned off.

  12. For the Summary page: Review the configuration of your auto-labeling policy and make any changes that needed, and complete the configuration.

Now on the Information protection > Auto-labeling page, you see your auto-labeling policy in the Simulation or Off section, depending on whether you chose to run it in simulation mode or not. Select your policy to see the details of the configuration and status (for example, Policy simulation is still running). For policies in simulation mode, select the Items to review tab to see which emails or documents matched the rules that you specified.

You can modify your policy directly from this interface:

  • For a policy in the Off section, select the Edit policy button.

  • For policy in the Simulation section, select the Edit policy option at the top of the page, from either tab.

    Edit auto-labeling policy option.

    When you're ready to run the policy without simulation, select the Turn on policy option.

    Note

    Files with no content (i.e. zero bytes in size) may not be labeled.

Auto-labeling policies run continuously until they're deleted. For example, new and modified files will be included with the current policy settings.

Monitoring your auto-labeling policy

After your auto-labeling policy is turned on, you can view the labeling progress for files in your chosen SharePoint and OneDrive locations. Emails aren't included in the labeling progress because they're automatically labeled as they're sent.

The labeling progress includes the files to be labeled by the policy, the files labeled in the last seven days, and the total files labeled. Because of the maximum of labeling 100,000 files a day, this information provides you with visibility into the current labeling progress for your policy and how many files are still to be labeled.

When you first turn on your policy, you initially see a value of 0 for files to be labeled until the latest data is retrieved. This progress information updates every 48 hours, so you can expect to see the most current data about every other day. When you select an auto-labeling policy, you can see more details about the policy in a flyout pane, which includes the labeling progress by the top 10 sites. The information on this flyout pane might be more current than the aggregated policy information displayed on the Auto-labeling main page.

You can also see the results of your auto-labeling policy by using content explorer when you have the appropriate permissions:

  • Content Explorer List Viewer role group lets you see a file's label but not the file's contents.
  • Content Explorer Content Viewer role group, and Information Protection and Information Protection Investigators role groups let you see the file's contents.

However currently, restricted admins won't be able to see labeling activities for OneDrive in activity explorer.

Tip

You can also use content explorer to identify locations that have documents with sensitive information, but are unlabeled. Using this information, consider adding these locations to your auto-labeling policy, and include the identified sensitive information types as rules.

Use PowerShell for auto-labeling policies

You can use Security & Compliance PowerShell to create and configure auto-labeling policies. This means you can fully script the creation and maintenance of your auto-labeling policies, which also provides a more efficient method of specifying multiple locations for SharePoint and OneDrive.

Before you run the commands in PowerShell, you must first connect to Security & Compliance PowerShell.

To create a new auto-labeling policy:

New-AutoSensitivityLabelPolicy -Name <AutoLabelingPolicyName> -SharePointLocation "<SharePointSiteLocation>" -ApplySensitivityLabel <Label> -Mode TestWithoutNotifications

This command creates an auto-labeling policy for a SharePoint site that you specify. For a OneDrive location, use the OneDriveLocation parameter, instead.

To add more sites to an existing auto-labeling policy:

$spoLocations = @("<SharePointSiteLocation1>","<SharePointSiteLocation2>")
Set-AutoSensitivityLabelPolicy -Identity <AutoLabelingPolicyName> -AddSharePointLocation $spoLocations -ApplySensitivityLabel <Label> -Mode TestWithoutNotifications

This command specifies the new SharePoint URLs in a variable that is then added to an existing auto-labeling policy. To add OneDrive locations instead, use the AddOneDriveLocation parameter with a different variable, such as $OneDriveLocations.

To create a new auto-labeling policy rule:

New-AutoSensitivityLabelRule -Policy <AutoLabelingPolicyName> -Name <AutoLabelingRuleName> -ContentContainsSensitiveInformation @{"name"= "a44669fe-0d48-453d-a9b1-2cc83f2cba77"; "mincount" = "2"} -Workload SharePoint

For an existing auto-labeling policy, this command creates a new policy rule to detect the sensitive information type of U.S. social security number (SSN), which has an entity ID of a44669fe-0d48-453d-a9b1-2cc83f2cba77. To find the entity IDs for other sensitive information types, refer to Sensitive information type entity definitions.

For more information about the PowerShell cmdlets that support auto-labeling policies, their available parameters and some examples, see the following cmdlet help:

Tips to increase labeling reach

Although auto-labeling is one of the most efficient ways to classify, label, and protect Office and PDF files that your organization owns, check whether you can supplement it with any of the following methods to increase your labeling reach:

Additionally, consider marking new files as sensitive by default in SharePoint to prevent guests from accessing newly added files until at least one DLP policy scans the content of the file.