# Label meetings and calendar items - URL: https://m365playbooks.com/playbooks/label-meetings-and-calendar-items/ - Topic: Sensitivity labels (Program) - Product: Purview, SharePoint, Teams, Exchange - Stage: Deploy - Last reviewed: October 15, 2026 - Version: 1 - Written by: Sev Derghazarian ## 1. Purpose Some of the most sensitive information an organization has is never written down: it is said in board meetings, HR cases, negotiations and incident calls. Labelling meetings lets the organizer set protection once, on the invite, and have Outlook and Teams enforce it: who waits in the lobby, who can present, whether the meeting is recorded, and whether chat can be copied. Protection then depends on the label, not on each organizer remembering the right meeting options every time. ## 2. Overview Meeting protection set by the label on the invite: lobby, presenters, recording, watermarks and chat copying, enforced in Outlook and Teams. - Effort: About 10 to 15 person-days - Duration: 4 to 8 weeks - Complexity: Medium - Who's in the room: Purview admin, Teams admin, Exchange admin, communications lead, executive assistants and other organizers of sensitive meetings - Licensing: Labels for scheduled meetings need Microsoft 365 E5, Microsoft Purview Suite, Microsoft 365 E5 Information Protection and Governance, or Office 365 E5. Teams meeting options in labels (lobby, presenters, recording, watermarks, end-to-end encryption) also need Teams Premium; for end-to-end encryption only the organizer needs it. - Risk of not doing it: Sensitive meetings rely on each organizer remembering the right options; one forgotten lobby setting or automatic recording can expose what was never meant to leave the room. ## 3. Key activities ### Prerequisites 1. **Confirm licences for organizers** Labels on calendar items need an E5-level licence. The Teams meeting options a label can enforce (lobby, presenters, recording, video watermarks, end-to-end encryption, chat copying) need Teams Premium, and without it you can't configure all of those options. For end-to-end encryption, only the organizer needs Teams Premium; attendees don't. Start with the people who organize sensitive meetings, not everyone. Keep the licensed group aligned with the label policy scope, so nobody sees meeting options they can't use. Who: Purview admin with the Teams admin. Produces: Licensed organizers for the pilot. 2. **Check Outlook and Teams versions** Calendar labels need Outlook on the web or built-in labelling in Microsoft 365 Apps at the versions in Microsoft's minimum versions table, and Teams needs recent desktop or mobile clients or the web app on Edge or Chrome. When someone joins on an older client, the meeting options from the label can't be enforced for them. Meeting labels also work only with Exchange Online mailboxes. Who: Microsoft 365 Apps admin with the Teams admin. Produces: Confirmed versions, with gaps listed. 3. **Extend the label scopes** To use a label for meetings, it needs the Meetings scope together with the Files and Emails scopes; Microsoft notes all three are needed because they depend on each other. Plan this as a change to existing labels, published in the usual way, and allow up to 24 hours for it to reach apps. Who: Purview admin. Produces: Chosen labels with the Meetings scope added. ### Decisions 4. **Decision: Which labels carry meeting settings?** Add meeting settings to the labels people already know rather than creating meeting-only labels. Typically, Confidential limits who bypasses the lobby and who can present, and Highly Confidential adds no recording, a video watermark, end-to-end encryption and no copying of meeting chat, captions and transcripts. The label locks these options in Teams, and Microsoft notes a label can enforce end-to-end encryption, watermarks and automatic recording even when the admin policy has them turned off. Options: Create separate labels just for meetings; Add meeting settings to the top two existing labels; Add meeting settings to every label. Recommended default: Add meeting settings to the top two existing labels. Who: Taxonomy owner with the Teams admin. Produces: Meeting settings for each chosen label. 5. **Decision: Default and mandatory labels for meetings?** Label policies have their own meeting settings, independent of the email settings: a default label for meetings and mandatory labelling for meetings. In Outlook the default applies to new calendar events and to existing unlabelled ones when they are updated; in Teams it isn't applied when an existing unlabelled meeting is updated. Mandatory labelling for every meeting interrupts organizers for routine catch-ups, so most organizations start with a default that carries no meeting restrictions. Options: No default, labelling optional; A default with no meeting restrictions, labelling optional; Mandatory labelling for every meeting. Recommended default: A default with no meeting restrictions, labelling optional. Who: Taxonomy owner. Produces: Recorded meeting settings in the label policy. 6. **Decision: Inherit labels from files shared to meetings?** A policy setting lets a meeting take its label from files shared to it. It catches the meeting about a Highly Confidential document that the organizer forgot to label, but it can also surprise people when a meeting becomes more restricted partway through planning. Try it in the pilot before deciding. Options: Leave it off; Turn it on after the pilot. Recommended default: Turn it on after the pilot. Who: Taxonomy owner. Produces: A decision after the pilot. 7. **Decision: Protect channel meetings through the team's label?** For channel meetings, the meeting label comes from the team: you associate a meeting label with the container label, and every channel meeting and chat in teams with that label inherits it, without users being able to change it. This is set by editing an existing label for groups and sites. It suits teams that already carry a Highly Confidential container label. Options: Don't associate a meeting label; Associate a meeting label with the most sensitive container labels. Recommended default: Associate a meeting label with the most sensitive container labels. Who: Taxonomy owner. Produces: A decision per container label. ### Pilot configuration 8. **Publish to sensitive-meeting organizers** Publish the updated labels and policy settings to a pilot of the people who run sensitive meetings: executive assistants, HR, legal, and the incident response lead. Brief them on what each label does to a meeting before they first see it. Executive assistants usually schedule on behalf of others, so check how labels appear when they create meetings for their executives, and make sure both the assistant and the executive know which label to use for which meeting type. Who: Purview admin with the communications lead. Produces: Meeting labels live for the pilot. 9. **Test the edges** Test a labelled invite to an external guest (they see headers and footers; those whose client can't open an encrypted invite are sent to Outlook on the web or the encryption portal), a recurring series (labels apply to the series, not individual occurrences, and existing exceptions aren't labelled), changing a label during a meeting (recording, encryption and watermark settings change only after the organizer ends and restarts it), and Meet Now, which doesn't enforce the label's settings. Shared mailbox calendars can't be labelled at all. Write what you find into the organizer guide in plain terms, so organizers know the limits before they rely on the label. Who: Teams admin with pilot organizers. Produces: A tested-scenarios list and guidance for organizers. ### Production configuration 10. **Widen to all organizers in waves** Extend the policy to more organizers, starting with departments that run regular confidential meetings. Give every wave a one-page guide on which label to choose for which meeting and what attendees will notice. Use the pilot's experience to write the examples: the kinds of meetings people actually run, matched to labels. Organizers choose faster from real examples than from definitions. Who: Purview admin. Produces: Meeting labels available to all licensed organizers. 11. **Watch the labelling of meeting artifacts** A policy setting that applies the meeting label to recordings, transcripts and notes is in preview. Track it, test it when you are ready, and until then remind organizers that the label protects the meeting itself, not every file it produces. Who: Purview admin. Produces: A decision date for labelling meeting artifacts. 12. **Make it enforceable** The label locks the meeting options in Teams and can enforce end-to-end encryption, watermarks and recording settings even where the admin policy has them off, so organizers can't forget or undo them. The label can't stop people sharing the meeting link or taking screen captures, and Meet Now doesn't enforce it, so those remain risks to cover in guidance. _Partly enforced. The gaps are a risk until a mechanism covers them._ ## 4. Pilot to production **Rollout approach:** By risk tier (Pilot size: 20 to 50 organizers of sensitive meetings). The value is concentrated in a small number of high-risk meetings. Starting with the people who organize board, HR, legal and incident meetings protects what matters first and tests the settings with users who care about them. 1. **Brief the pilot organizers** (Change: Inform) Explain what each label does to a meeting and what attendees, including guests, will see. Move on when: Organizers can say which label suits which meeting. 2. **Run labelled meetings for three weeks** (Change: Explain) Organizers label real sensitive meetings and report anything unexpected. Collect what attendees noticed as well as what organizers did: lobby waits, missing recordings and watermarks are the usual surprises. Move on when: No unresolved issue stops a meeting from running. 3. **Adjust settings and guidance** (Change: Explain) Tune the meeting settings per label and decide on inheritance from shared files. Move on when: Pilot feedback is closed or scheduled. 4. **Extend to the next risk tier** (Change: Explain) Add departments that run regular confidential meetings. Brief each department's assistants and managers with the organizer guide a week before labels reach them. Move on when: Each wave settles without a rise in support requests. 5. **Make it routine** (Change: Sustain) Add meeting labels to the labelling guide and to onboarding for assistants and managers. Move on when: Guidance covers meetings and is part of onboarding. ## 5. Common challenges - **If you** Treat the label as the only protection. What tends to happen: People assume a labelled meeting can't leak, but the label can't stop link sharing or screen captures.. A better approach: Tell organizers plainly what the label does and doesn't do, and keep the most sensitive discussions to invited, identified attendees. - **If you** Label meetings for everyone at once. What tends to happen: Routine meetings pick up restrictions nobody expected, and organizers stop labelling.. A better approach: Start with organizers of sensitive meetings and keep the default free of meeting restrictions. - **If you** Forget older clients. What tends to happen: Attendees on old Teams or Outlook versions join without the label's settings being enforced.. A better approach: Check versions before the pilot and close the gaps before widening. - **If you** Label a recurring series and assume every occurrence is covered. What tends to happen: Existing exceptions in the series stay unlabelled.. A better approach: Label the series before exceptions are created, and check existing series when you roll out. - **If you** Change the label once the meeting has started. What tends to happen: Recording and watermark settings don't change until the meeting is restarted, so attendees see the old behaviour.. A better approach: Set the label on the invite; if it must change, end and restart the meeting. - **If you** Schedule sensitive meetings from a shared mailbox calendar. What tends to happen: The meeting can't be labelled at all, because shared mailbox calendars don't support labels.. A better approach: Have organizers schedule sensitive meetings from their own calendar, or delegate access rather than use a shared mailbox. ## 6. Checkpoints **Pilot:** - [ ] Do pilot organizers have the licences their labels need? - [ ] Do chosen labels have the Files, Emails and Meetings scopes? - [ ] Have external guests, recurring series and Meet Now been tested? - [ ] Do executive assistants know how labels behave when they schedule on behalf of others? **Production:** - [ ] Can every licensed organizer apply meeting labels? - [ ] Are channel meetings in sensitive teams covered through their container labels? - [ ] Does the labelling guide say what meeting labels do and don't protect? - [ ] Is there a decision date for labelling recordings and transcripts? - [ ] Have assistants and managers in each wave received the organizer guide before labels reached them? ## 7. Success measures Capture a baseline before you start, or you won't be able to show the change. - Sensitive meetings carrying a label (Where you see it: Spot checks with executive assistants; Good direction: Up) - Meetings recorded against the label's intent (Where you see it: Organizer reports; Good direction: Down) - Support requests about meeting labels (Where you see it: Service desk; Good direction: Down) **Ready-to-use text: Organizer guide: which label for which meeting** > General: everyday meetings; no restrictions. Confidential: meetings about non-public plans; only people from our organization skip the lobby and only you present. Highly Confidential: board, HR cases, legal and incidents; no recording, a watermark on shared video, and chat can't be copied. A label can't stop someone sharing the link or taking a screenshot, so invite only the people who need to be there. **Ready-to-use text: Note for attendees on labelled meetings** > This meeting is labelled [label]. You may wait in the lobby, recording may be turned off, and you may see a watermark on shared content. These settings come from the label, so the organizer can't change them during the meeting. **Ready-to-use text: Pilot feedback questions** > 1. Which label did you use for which meetings? 2. Did any setting stop the meeting from working as you needed? 3. What did attendees, including guests, ask about? 4. Was any meeting harder to label than it should be? ## 8. Additional reading **Plan:** - [Microsoft Teams Premium overview for admins](https://learn.microsoft.com/en-us/microsoftteams/enhanced-teams-experience) - [Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](https://learn.microsoft.com/en-us/microsoftteams/meeting-templates-sensitivity-labels-policies) - [Microsoft Purview service description](https://learn.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-purview-service-description) **Configure:** - [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/en-us/purview/sensitivity-labels-meetings) - [Manage end-to-end encryption for Microsoft Teams meetings and one-to-one calls](https://learn.microsoft.com/en-us/microsoftteams/end-to-end-encrypted-meetings) - [Minimum versions for sensitivity labels in Microsoft 365 Apps](https://learn.microsoft.com/en-us/purview/sensitivity-labels-versions) ## Changelog - Version 1, 2026-10-15, Sev Derghazarian: First version. Facts checked against Microsoft Learn on 2026-10-15.