How to Configure Teams Meeting Collaborative Annotation Policies in PowerShell Using CsTeamsMeetingPolicy

Collaborative annotations in Microsoft Teams allow meeting attendees to draw, highlight, type text, and add sticky notes directly on top of shared desktop or application screens during active calls. Powered by Microsoft Whiteboard components integrated into the meeting canvas, annotations provide valuable real-time ideation for design reviews, architectural walkthroughs, and educational workshops. However, in heavily regulated, legal, or large enterprise environments, uncontrolled on-screen markup can introduce compliance risks, distraction, or visual disruptions. Using the Microsoft Teams PowerShell module, administrators can manage the AllowAnnotations parameter within CsTeamsMeetingPolicy to enforce precise governance across their organisation.

Governance and Security Architecture of Teams Annotations

Collaborative annotations operate within the meeting sharing stream. When a presenter shares their screen and activates annotations, Teams launches a transparent Whiteboard overlay over the presenter’s display. All participants permitted by policy can interact with the markup toolbar simultaneously, with their cursor movements and initials visible to everyone in attendance.

From an administrative perspective, annotation capabilities are governed at two levels:

• Tenant-Level Whiteboard Integration: The tenant must have Microsoft Whiteboard enabled under Microsoft 365 Admin Center settings, as annotation snapshots and interaction data rely on Whiteboard infrastructure.
• Per-User Meeting Policy: The AllowAnnotations attribute in CsTeamsMeetingPolicy controls whether a meeting organiser can initiate collaborative annotations or whether participants assigned that policy can access markup tools.

By default, AllowAnnotations is set to $true in the global meeting policy. Applying targeted custom policies allows administrators to restrict annotations exclusively to vetted departments (such as engineering or creative teams) while disabling them for external webinars and executive briefings.

Connecting to the Microsoft Teams PowerShell Module

To audit and modify meeting policies, open an elevated PowerShell window and import the MicrosoftTeams module. Authenticate using an account assigned the Teams Administrator or Global Administrator role:

Import-Module MicrosoftTeams
Connect-MicrosoftTeams

Ensure you are running modern versions of the module (version 5.0.0 or higher) to ensure complete compatibility with meeting policy parameters.

Auditing Existing Collaborative Annotation Settings

Before implementing configuration changes, audit the current state of collaborative annotations across the default Global (Org-wide) policy:

Get-CsTeamsMeetingPolicy -Identity Global | Select-Object Identity, AllowAnnotations, AllowUserToJoinExternalMeeting, AllowScreenSharing

To inspect all meeting policies defined within the tenant and compare their annotation configurations side by side, run:

Get-CsTeamsMeetingPolicy | Select-Object Identity, Description, AllowAnnotations | Format-Table -AutoSize

If AllowAnnotations displays True, users assigned that policy can enable annotation toolbars during their scheduled and ad-hoc meetings.

Disabling Collaborative Annotations Globally

In enterprise settings requiring strict information barriers or where meeting screen recordings must remain pristine without ad-hoc user markup, you can disable annotations org-wide by updating the Global policy:

Set-CsTeamsMeetingPolicy -Identity Global -AllowAnnotations $false

Verify that the Global policy reflects the updated state:

Get-CsTeamsMeetingPolicy -Identity Global | Select-Object Identity, AllowAnnotations

When set to $false, the pen and annotation icon is removed from the presenter’s top meeting toolbar, preventing any attendee from initiating on-screen markup.

Creating and Assigning a Scoped Annotation Policy

Rather than disabling the feature entirely, best practice often dictates restricting annotations to specific functional units, such as Product Development or Training teams. Create a tailored policy with annotations explicitly enabled:

New-CsTeamsMeetingPolicy -Identity "DesignCollaborativeMeetingPolicy" `
    -Description "Permits interactive collaborative annotations and Whiteboard overlays during meetings" `
    -AllowAnnotations $true

To grant these capabilities to a single user, execute Grant-CsTeamsMeetingPolicy:

Grant-CsTeamsMeetingPolicy -Identity "[email protected]" -PolicyName "DesignCollaborativeMeetingPolicy"

For department-wide deployment, administrators can target users dynamically via Microsoft Entra ID (Azure AD) security groups or distribution lists:

$GroupId = (Get-AzureADGroup -SearchString "Engineering Team").ObjectId
New-CsGroupPolicyAssignment -GroupId $GroupId `
    -PolicyType TeamsMeetingPolicy `
    -PolicyName "DesignCollaborativeMeetingPolicy" `
    -Rank 1

Validating Policy Propagation and Troubleshooting

Like all Microsoft Teams policy modifications, changes made via CsTeamsMeetingPolicy can take between 15 minutes and several hours to replicate fully across Teams microservices and desktop clients. To verify that an individual user has received the designated policy assignment, execute:

Get-CsUserPolicyAssignment -Identity "[email protected]" -PolicyType TeamsMeetingPolicy

If a user assigned an enabled annotation policy reports that the annotation icon remains greyed out during screen sharing, verify the following prerequisites:

• Window vs Desktop Sharing: Annotations require full desktop screen sharing; sharing an individual application window does not support the multi-layer Whiteboard canvas overlay.
• Client Type: Collaborative annotations are fully supported in the Teams desktop client on Windows and macOS. Presenters using the web client or mobile versions cannot initiate annotations, though mobile participants can view live markup.
• Hardware Acceleration: Ensure GPU hardware acceleration is enabled in Teams desktop settings, as low-memory virtual desktop infrastructure (VDI) clients may suppress the transparent rendering overlay.