Microsoft has begun rolling out a redesigned meeting toolbar for Teams desktop users that, for the first time, lets participants pin, unpin, and reorder on-screen controls. The update, which reached general availability in July 2026, also relocates the Raise Hand feature into the Reactions menu and separates the Leave button to a dedicated spot on the right.

The Meeting Toolbar Just Became Your Personal Workspace

The centerpiece of this release is user-driven toolbar customization. Instead of a one-size-fits-all strip of icons, Teams now lets you decide which controls stay visible, which get tucked away, and in what order they appear. Microsoft announced the change on its Microsoft 365 Roadmap under ID 560321, noting that the design is meant to make meetings faster and more intuitive—even if it feels unfamiliar at first.

Four concrete changes arrive with this rollout:

  • Pin: Keep frequently used controls like mute, camera, chat, or share permanently accessible.
  • Unpin: Hide commands you rarely need, reducing visual clutter and the chance of mis-clicks.
  • Reorder: Drag and drop supported controls into a sequence that matches your muscle memory.
  • Relocated functions: Raise Hand moves into the Reactions menu, while Leave is visually isolated on the far right.

The result is a toolbar that adapts to your role. A presenter might pin screen sharing, participant management, and meeting notes front and center. An attendee who mostly listens could emphasize audio and chat. A moderator might prioritize reactions and breakout rooms.

The feature is rolling out now to the Teams desktop client on Windows and macOS. According to Microsoft’s roadmap, it covers Worldwide Standard Multi-Tenant environments as well as GCC, GCC High, and Department of Defense cloud instances. Web, mobile, VDI, and Teams Rooms are not included in this release.

A New Home for Raise Hand — and a Question of Speed

Grouping Raise Hand under Reactions is the most immediately noticeable change. Microsoft says the move reduces accidental clicks, and logically, both functions represent nonverbal participation. However, Raise Hand is more than an emoji: it places you in a queue, signals a want to speak, and often governs orderly discussion in large meetings or classrooms.

Placing it behind an extra click could slow down participation in fast-paced sessions. Users who rely on the hand icon daily—teachers, public-sector workers, event facilitators—may need time to rebuild the reflex. On the other hand, clearing the main toolbar of a sometimes-sensitive button may prevent awkward accidental raises during presentations.

For now, the design does not allow you to pin Raise Hand back out of the Reactions menu. If that becomes a significant friction point, Microsoft has the framework to let users override the default grouping in a future update.

Leave Gets Its Own Space (Finally)

Separating the Leave button to the right edge of the toolbar is a small but high-impact design choice. An accidental reaction is embarrassing; an accidental exit can drop you out of a meeting entirely, cut audio, and disrupt the session—especially painful for presenters or organizers.

By isolating the Leave command, Teams follows a well-established UI principle: destructive actions should not live among frequently used controls. The right-aligned position also creates a clear endpoint visually, making the toolbar easier to parse at a glance. Organizers still see the “End Meeting” option under the same menu, and Microsoft must ensure that the distinction between leaving and ending the call for everyone remains unmistakable.

How to Set Up Your Toolbar: A Practical Guide

Customization only helps if your layout matches your actual routine. Resist the urge to pin everything; instead, build a toolbar around the actions you take in nearly every meeting.

Step-by-step setup

  1. Identify your core commands. For most, this includes microphone, camera, chat, and participants. Presenters should add screen sharing and meeting notes. Trainers may want breakout rooms or Q&A.
  2. Pin time-critical controls. Anything you need within a second—like mute when you’re about to speak—deserves a permanent spot.
  3. Unpin specialty items. Controls for recording, transcription, or apps that you use once a month can live in the overflow menu.
  4. Group related actions. Keep communication controls together, presentation tools in one cluster, and engagement features (now under Reactions) in another.
  5. Test in a low-stakes call. Resize the window, share content, and toggle side panels to see if your layout holds up.
  6. Stick with it. Muscle memory takes time; avoid rearranging icons weekly.

Sample layouts

Typical attendee: Pin Microphone, Camera, Chat, Participants, and Reactions (which now contains Raise Hand). Unpin advanced sharing, notes, or breakout rooms.

Presenter or facilitator: Pin Microphone, Share Content, Participants, Chat, View Options, and Meeting Notes. Keep Reactions and Leave where they are, but ensure sharing is the first icon you can reach when screen space tightens.

If you ever lose a command, look for the overflow indicator (often a “…” or “More” icon). Unpinned tools aren’t gone—they’re just one click away.

What IT Departments Need to Know

This is not a behind-the-scenes change. Users will see a different toolbar the moment the update lands, and support teams should prepare.

Rollout timing

The feature reached general availability in July 2026, but staggered deployment means some tenants see it earlier than others. Environments on Targeted Release can test now. Commercial clouds, GCC, GCC High, and DoD are all included, though exact timing may differ by instance.

Training users

Don’t overcomplicate it. A short internal post with a screenshot highlighting three things is enough:

  • You can now pin, unpin, and reorder meeting controls.
  • Raise Hand moved to the Reactions menu.
  • Leave is now on the right, separated from other buttons.

Encourage users to experiment, but avoid mandating a single layout unless there’s a specific operational need. Personalization is the point.

Help-desk considerations

Custom toolbars mean technicians can no longer say “click the fourth icon.” Support scripts should use control names, not positions. Screen sharing during a support call becomes more important when a user can’t find a button they unpinned. Consider updating internal knowledge base articles and accessibility guides.

Testing checklist for early adopters

  • Do customized layouts persist after restarting Teams or switching accounts?
  • How does the toolbar behave when you shrink the meeting window? Which pinned controls get hidden first?
  • Can keyboard-only users navigate the new Reactions menu and reordered controls?
  • Do controls appear and disappear logically when joining meetings with different roles (attendee vs. presenter)?
  • Does Leave always show the correct option (Leave vs. End Meeting) based on your role?

What’s Next: Syncing, Mobile, and Admin Controls

The current release is desktop-only and does not yet synchronize preferences across devices. Whether your layout roams with your account or stays local to each machine is a key question for hybrid workers. Microsoft has not confirmed cloud syncing, but it’s a logical next step.

Platform expansion is also worth watching. Mobile devices and the web client will likely need their own adaptation of customization, given screen real estate differences. Admin-level policy controls, such as suggested layouts for call-center staff or trainers, could appear in future Microsoft 365 roadmap entries.

The immediate metric of success will be whether users spend less time hunting for controls—without a spike in support tickets about missing buttons or confusion over Raise Hand. If the toolbar feels dependable across meetings and devices, this becomes a quiet but meaningful productivity upgrade for the hundreds of millions who live in Teams every day.