Microsoft has started rolling out a preview that lets organizations apply Microsoft Purview Information Protection sensitivity labels directly to Viva Engage communities. The feature, available now for testing, allows community creators and managers to manually select a sensitivity label during community creation or when editing community settings. General availability is slated for May 2026.

This move extends Purview’s data governance reach to the enterprise social network, giving admins a straightforward way to classify communities, enforce access rules, and limit external sharing based on label policies.

Manual Labels Come to Community Creation

Until now, sensitivity labels for Viva Engage communities were limited. Organizations could set a default label at the network level or rely on tenant-wide policies, but there was no way for users to choose a label manually when spinning up a new community or updating an existing one. The preview changes that.

When creating a community in the Viva Engage web experience, users now see a Sensitivity dropdown. The list of available labels is controlled by admins through the Microsoft Purview compliance portal. Labels can be configured to:

  • Encrypt community content, ensuring only authorized members can read posts and files.
  • Restrict external sharing—for instance, allowing guest access only for “General” communities while blocking it for “Confidential” ones.
  • Mark the community header with visual indicators (e.g., “Confidential” tags), so everyone understands the handling requirements at a glance.

Admins can also require a label before a community is created, preventing unclassified spaces from popping up. The preview supports the web app only; Microsoft has not yet confirmed whether the mobile experience will get manual labeling before general availability.

What This Means for Your Organization

For IT Admins and Compliance Officers

This preview hands you a long-missing lever for governing Viva Engage. If your organization uses communities for project coordination, leadership updates, or departmental chatter, you can now ensure that the right protective controls travel with each community from day one.

  • Granular control: Instead of one-size-fits-all defaults, you can map sensitivity labels to specific community types. An executive town hall community can be labeled “Highly Confidential,” while a wellness group remains “General.”
  • Simplified compliance: Labels automatically apply retention policies, content encryption, and access restrictions. This reduces manual errors and helps meet regulatory obligations.
  • Better lifecycle management: When a project ends, a label can trigger a retention schedule, so content is preserved or deleted according to policy.

You’ll need to configure which sensitivity labels are available for Viva Engage in the Purview portal, then publish them via your label policies. In many cases, this requires a Microsoft 365 E5 license or the equivalent compliance add-on.

For Community Managers and End Users

When you go to create a community, you’ll notice the new label picker. It’s a small extra click, but it’s a powerful signal. The label you choose (or the default your admin set) determines who can join, whether guests are allowed, and how strictly the content is protected.

If you’re a community manager for an existing space, you can edit the community and apply a label retroactively. Before you do, though, think about the implications: changing to a more restrictive label might lock out current external members or modify sharing settings mid-stream. Best practice? Apply labels to new communities first, then retrofit older ones after a review.

For the Business at Large

Viva Engage often becomes the go-to place for spontaneous collaboration. It’s where teams share early drafts, discuss mergers, or roll out internal campaigns. Without labeling, that data sits in a governance gray zone. Manual labels close that gap, aligning Viva Engage with the sensitivity-based protections already common in Teams, SharePoint, and OneDrive.

How We Got Here

Microsoft Purview Information Protection sensitivity labels have been a cornerstone of the company’s compliance strategy for years. They started in Office 365, helping classify and protect documents and emails. Over time, labels expanded to groups, SharePoint sites, Teams, and now Power BI and other services.

Viva Engage, reborn from Yammer, became a key part of the Microsoft Viva employee experience suite. As companies adopted it for top-down communications and bottom-up communities, the need for robust governance grew louder. IT pros asked for the same labeling capabilities they had in Teams. Microsoft’s answer came first in the form of automatic labeling based on content detection—still in limited preview for some tenants. Manual labeling in the web app is the next step, offering immediate, user-driven classification without waiting for the AI to scan conversations.

The May 2026 general availability date suggests a long runway. During the preview, Microsoft will likely gather feedback, refine the admin controls, and possibly add support for auto-labeling, the mobile app, and programmatic labeling via Microsoft Graph APIs. For now, the focus is on getting the web experience right.

Getting Started with Manual Sensitivity Labels

If you want to turn this on today, here’s a practical path:

  1. Verify licensing — Make sure you have the appropriate Microsoft 365 licenses. Sensitivity labels generally require E5, Microsoft 365 E5 Compliance, or an equivalent add-on. Check your subscription under the Microsoft 365 admin center.
  2. Create or review your sensitivity labels — Head to the Microsoft Purview compliance portal (purview.microsoft.com). Under Information protection > Sensitivity labels, create or edit labels you want to use for Viva Engage. Pay special attention to:
    - Encryption settings (e.g., “None,” “Assign permissions now”).
    - Content marking (headers, footers, watermarks—though not all appear in Viva Engage).
    - Group and site settings under the label’s scope. This is where you define external sharing controls for Teams and Groups, which also govern Viva Engage communities.
  3. Publish labels — Once your labels are ready, publish them in a label policy. On the Publish labels page, choose the labels you want in Viva Engage, then decide which users and groups the policy applies to. You can start with a pilot group.
  4. Enable labels for Viva Engage — By default, sensitivity labels may not appear in Viva Engage. To enable them, you may need to run a PowerShell cmdlet (likely Set-VivaEngageCommunityConfiguration or similar—check the latest cmdlet reference) or toggle a setting in the Viva Engage admin center. Microsoft’s documentation should have the exact steps as the preview expands.
  5. Test with a pilot community — Create a test community and try applying different labels. Verify that the label’s effects (external sharing restrictions, encryption) work as expected. Ask a user without the label policy to see if they can bypass the required label.
  6. Communicate to users — Before a wider rollout, let community managers know what to expect. Provide a one-pager explaining which labels to use for common scenarios and what the visual indicators mean.
  7. Plan for existing communities — For communities created before the feature, you’ll likely want to assign labels gradually. You can do this manually, or wait for future bulk-update tools that Microsoft might deliver by GA.

Looking Ahead: May 2026 and Beyond

The sixteen-plus months until general availability hint at a significant set of enhancements. During this period, expect Microsoft to address gaps like:

  • Auto-labeling: The ability to automatically classify communities based on content patterns, similar to how SharePoint sites can be auto-labeled.
  • Mobile support: Sensitivity label enforcement in the Viva Engage mobile app, where many frontline workers participate.
  • Programmatic labeling: Microsoft Graph API endpoints that let you apply labels via scripts or third-party tools, essential for large-scale deployments.
  • Deeper integration with DLP: Data loss prevention policies that read the community’s label and block sensitive data from being shared inappropriately inside a community.

For now, the preview gives admins a chance to influence the final product. If you’re dealing with highly regulated data in Viva Engage, join the preview, test relentlessly, and feed your requirements back through the Microsoft 365 feedback portal. The decisions you make today—label taxonomy, user training, migration plans—will pay off when the feature reaches GA and becomes a non-negotiable part of your governance toolkit.

By bringing manual sensitivity labels to communities, Microsoft is treating Viva Engage less as a casual social network and more like a serious information pipeline. That’s good news for anyone trying to keep a lid on corporate data without killing the spontaneity that makes communities valuable.