Sensitivity Labels Are Missing In Outlook, Outlook On The Web, & Other Office Apps

By Ashwin Venugopal -

 







Symptoms

To categorize and safeguard user documents and emails within your company, you have set up sensitivity labels in the Microsoft Purview platform. The sensitivity labels are absent or the Sensitivity button is unavailable when your users attempt to apply them in Outlook, Outlook on the web, or other Office applications. 

For issues related to sensitivity labels, run an automated diagnostic for sensitivity labels in the Microsoft 365 admin center. It analyzes the sensitivity labels, identifies any issues, and provides resolutions. 

Run the Diagnostic For Sensitivity Labels

  • Choose the Run Tests: Sensitivity Labels button to open the diagnostic in the Microsoft 365 admin center.

  • Enter Label name and User Principal Name (UPN) or email address of the user. 

  • Select Run Tests.

Outlook

This issue occurs for one of the following reasons:
  1. The user account that's signed in to Outlook isn't a Microsoft 365 subscriber.
  2. The security labels aren't published in the Microsoft Purview portal.
  3. The Outlook version doesn't support the built-in labeling.
  4. The label policy distribution process isn't successful. 

Resolution

To resolve this issue, use one or more of the following methods:
  • Verify that the user account that's signed in to Outlook is a Microsoft 365 subscriber. 

  • Verify that the sensitivity labels are published in the Microsoft Purview portal. 

  • Verify that the Outlook version meets the requirements that are listed in Sensitivity label capabilities in Outlook.

  • Verify that the label policy distribution is successful.

  • Verify that the Outlook client is using built-in labeling.

  • Reset Office built-in labeling.

Outlook on the Web

If the sensitivity labels are set up improperly, this problem arises. You can look at this problem by reproducing it with a network trace or Fiddler. 

Other Office Apps

This issue occurs for one or more of the following reasons:
  1. The user account that's signed in to the Office apps isn't a Microsoft 365 subscriber.
  2. The security labels aren't published in the Microsoft Purview portal.
  3. There's no valid subscription to the Office edition.
  4. Office file types aren't supported.
  5. Office built-in labeling is turned off through Group Policy.
  6. The licenses aren't assigned to the affected users. 

Resolution

To resolve this issue, use one or more of the following methods:
  • Verify that the user account that's signed in to the Office apps is a Microsoft 365 subscriber. 

  • Verify that the sensitivity labels are published in the Microsoft Purview portal. 

  • Verify that the Office app version meets the requirements that are listed in Sensitivity label capabilities in Word, Excel, and PowerPoint.

  • Verify that Office file types are supported for built-in labeling.

  • Verify that the Office apps are using built-in labeling.

  • Verify that the appropriate licenses are assigned to the affected users per Microsoft 365 guidance for security & compliance.

  • Check whether there are any known issues that affect sensitivity labels in the Office apps.

Conclusion

The issue regarding the sensitivity labels is resolved. 



















Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Deployment (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 3, please click  here Microsoft Sentinel Content Hub Content in Microsoft Sentinel includes any of the following types: Data connectors offer log ingestion from different sources into Microsoft Sentinel. Parsers give log formatting/transformation into ASIM formats, supporting usage across various Microsoft Sentinel content types and scenarios. Workbooks provide monitoring, visualization, and interactively with data in Microsoft Sentinel, highlighting meaningful insights for users.  Analytics rules give alerts that point to relevant SOC actions via incidents.  Hunting Queries are used by SOC teams to proactively hunt for threats in Microsoft Sentinel. Notebooks help SOC teams in using advanced hunting features in Jupyter and Azure Notebooks. Watchlists support the ingestion of specific data for enhanced threat detection and reduced alert fatigue.  Playbooks and Azure Logic Apps Custom Connectors provide featu...
Read more