MC772556 - Microsoft Teams: Shorter meeting URLs

Service

Microsoft Teams

Last Updated

Apr 25, 2024

Published Apr 8, 2024

Tag

Updated message
Feature update
User impact
Admin impact

Platforms

Android
Desktop
iOS
Mac
TeamsAndSurfaceDevices
Web

Summary

Microsoft Teams is shortening meeting URLs for easier sharing across all platforms. The rollout starts in early Juen 2024 and will be completed by early July 2024. Existing URLs will still work; new URLs will have a simplified syntax. Organizations should check integrations that use URL parameters and update documentation. No admin action is required.

More information

Updated April 25, 2024: We have updated the rollout timeline below. Thank you for your patience.

We are reducing the length of Microsoft Teams meeting URLs for easier sharing. This rollout applies to all Microsoft Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web). 

This message is associated with Microsoft 365 Roadmap ID 381953.

When this will happen:

Targeted Release: We will begin rolling out early June 2024 (previously early May) and expect to complete by mid-June 2024 (previously mid-May).

General Availability (Worldwide, GCC): We will begin rolling out mid-June 2024 (previously mid-May) and expect to complete by late June 2024 (previously early June).

General Availability (GCC High, DoD): We will begin rolling out mid-June 2024 and expect to complete by early July 2024.

How this will affect your organization:

Longer URLs for meetings scheduled before the rollout will continue to work. The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode>

What you need to do to prepare:

You may want to check if you have any integrations that use parameters from URL. After the rollout, the URL will only contain the meeting ID. Parameters such as tenant ID, organizer ID, conversation ID and message ID will not be in the URL.

This rollout will happen automatically by the specified date with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.