Microsoft Teams: Pre-pin meeting apps for users

Originally posted by Microsoft Mar 22, 2024 Uncategorized 0 Comments

Microsoft Teams is introducing a new feature that allows admins to pre-pin and pre-install meeting apps for users. This update extends the functionality to meeting apps, streamlining the user’s experience, especially during meetings. Admins can choose the meeting apps to pre-pin and pre-install, and no specific actions are required to prepare for this feature update. The rollout will begin in early April 2024 and is expected to complete by mid-April 2024 worldwide.

Microsoft Teams is now enhancing app setup policies, allowing admins to pre-pin and pre-install meeting apps for users. Earlier, the pre-pinning and pre-installation were limited to personal apps and message extensions. This update extends the functionality to meeting apps. Admins can set up policies to install and pin meeting apps to provide users quick and easy access to their necessary meeting tools within Microsoft Teams.

This message is associated with Microsoft 365 Roadmap ID 131169

When this will happen: 

Worldwide: We will begin rolling out early April 2024 and expect to complete by mid-April 2024.

GCC, GCC High, DoD: We will begin rolling out late April 2024 and expect to complete by late May 2024.

How this will affect your organization:

This new feature enhances the customization of Microsoft Teams for users by highlighting the most important meeting apps for them. Admins can choose the meeting apps to pre- pin and pre-install, streamlining the user’s experience, especially during meetings. The pinned apps will appear in the meeting app flyout and the meetings tabs next to chat.

View image in new tab

What you need to do to prepare:

This feature update does not affect any existing policies or permissions. No specific actions are required. You can review the existing app setup policies and consider the meeting apps that could be beneficial to pre-pin and pre-install for your users. 

You may want to notify your users about this change and update any relevant documentation as appropriate.

Message ID: MC748380