MC772556 - Microsoft Teams: Shorter meeting URLs

Message Center

Summary

Microsoft Teams is rolling out shorter meeting URLs starting early 2025, improving link usability and security by removing extra parameters. New links expire 60 days after meeting end or creation. Old links remain valid. No admin action is needed, but users should update integrations and inform organizers about expired links.

Last Updated

Apr 30, 2026

Published Apr 8, 2024

View version history

Service

Microsoft Teams

Tag

Updated message
Feature update
User impact
Admin impact

Platforms

Android
Desktop
iOS
Mac
TeamsAndSurfaceDevices
Web

More information

Updated January 20, 2026: We’ve updated how Teams meeting join links appear in meeting invites. As part of the broader rollout of the new, shorter meeting URL format, meeting invites now display the full join link directly instead of a labeled “Join the meeting now” hyperlink. This improves link consistency, reliability across clients and email applications, and makes copying and sharing the link easier. This update does not change meeting functionality or attendee experience. Existing Teams and Outlook clients continue to support the new link format.

Please note that information about meeting link expiry changes related to this rollout has been added.

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 mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase.

General Availability (Worldwide, GCC): We will begin rolling out January 2026 (previously mid-May 2025) and expect to complete by end of January 2026 (previously late May 2025).  

General Availability (GCC High, DoD):  We will begin rolling out February 2026 (previously early August 2025) and expect to complete by end of February 2026 (previously late October 2025).

How this will affect your organization:

The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode>

To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks.

Here are some details about how meeting links work and when they expire:

  1. In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire.
  2.  MeetNow meetings expire 60 days after creation. Learn more about expiration timelines for different types of meetings.

With the Short Meeting URL release, expiration limit will be applied to all newly created links.

Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 60 days after creation for MeetNow meetings. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting.

Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits).

The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that’s why the new behavior is a step in the right direction that we must take. It’s not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there.

Recommendations in case the meeting link has expired:

For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch.

For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link.

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.

You may inform meeting organizers from your tenant who use expired meeting links, or you may want to make a tenant-wide announcement about this change.

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.

Version history

14 versions tracked

Updated 13 times since Apr 8, 2024. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Apr 30, 2026 · 05:56 PMLatest · v14

    Changed: End date

  2. Jan 28, 2026 · 09:08 PMv13

    Changed: Body

  3. Jan 22, 2026 · 05:11 PMv12

    Changed: Body

  4. Dec 4, 2025 · 05:59 PMv11

    Changed: Body, End date

  5. Sep 10, 2025 · 07:02 PMv10

    Changed: Body, End date

  6. Feb 28, 2025 · 03:16 PMv9

    Changed: Body, End date

  7. Jan 10, 2025 · 05:31 PMv8

    Changed: Body

  8. Dec 3, 2024 · 10:21 PMv7

    Changed: Body, End date

  9. Sep 19, 2024 · 12:15 AMv6

    Changed: Body

  10. Jul 5, 2024 · 05:39 PMv5

    Changed: Body, End date

  11. May 17, 2024 · 08:30 PMv4

    Changed: Body, End date

  12. Apr 25, 2024 · 11:35 PMv3

    Changed: No tracked field changed

  13. Apr 25, 2024 · 11:35 PMv2

    Changed: Body, Tags

  14. Apr 8, 2024 · 11:34 PMOriginal · v1

    Changed: Initial version