Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 11:37 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Shorter meeting URLs

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
381953

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 4 Dec 2025 mid-May 2025, late May 2025, early July 2025, mid-July 2025, early August 2025, late October 2025 → January 2026, end of January 2026, February 2026, end of February 2026
  • Seen 10 Sep 2025 mid-August 2025 → late October 2025
  • Seen 28 Feb 2025 mid-April 2025, late April 2025, early June 2025, late June 2025 → mid-May 2025, late May 2025, early July 2025, mid-July 2025, early August 2025, mid-August 2025
  • Seen 10 Jan 2025 early April 2025 → mid-April 2025, early June 2025, late June 2025
  • Seen 3 Dec 2024 mid-January 2025, late January 2025, mid-March 2025 → late February 2025
  • Seen 19 Sep 2024 early November 2024, mid-November 2024, late November 2024, early December 2024 → late January 2025, mid-February 2025, mid-March 2025, early April 2025, late April 2025
  • Seen 5 Jul 2024 early August 2024, mid-August 2024, late August 2024, mid-September 2024, late September 2024 → early November 2024, mid-November 2024, late November 2024, early December 2024, mid-January 2025
  • Seen 17 May 2024 early June 2024, mid-June 2024, late June 2024, early July 2024 → early August 2024, mid-August 2024, late August 2024, mid-September 2024, late September 2024
  • Seen 25 Apr 2024 early May 2024, mid-May 2024 → late June 2024

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
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: In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire.  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.

What changed

Between archive captures, newest first
  1. Only details this page does not show changed.

  2. … the tenant, the links to the meetings scheduled by them automatically expire.  Every meeting link expires in MeetNow meetings expire 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. creation. Learn more about expiration timelines for different types of meetings. With the … in the documentation: 60 days after meeting ends for scheduled meetings and 8 hours60 days after creation for Meet Now.MeetNow meetings. Once this expiry period is over, in case someone clicks the link …

  3. Updated December 4, 2025: We have updatedJanuary 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 timeline. Thank you for your patience.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 … expect to complete by end of January 2026 (previously late May 2025). 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 (GCC High, DoD):  We will begin rolling out February 2026 …

  4. Updated September 10,December 4, 2025: We have updated the timeline. Thank you for your patience. Please … in this phase. General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025January 2026 (previously mid-April)mid-May 2025) and expect to complete by late May 2025end of January 2026 (previously late April).May 2025). Only Meet Now use cases (except Meet Now in chats and channels) … There will be no impact on the scheduled meetings in this phase. Rollout for scheduled meetings and channel Meet Now will be started in early July 2025 and expected to be completed by mid-July 2025.   General Availability (GCC High, DoD):  We will begin rolling out early August 2025 February 2026 (previously early June)August 2025) and expect to complete by late October 2025end of February 2026 (previously mid-August).late October 2025). How this will affect your organization: The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode> …

  5. Updated February 28,September 10, 2025: We have updated the rollout timeline below. timeline. Thank you for your patience. Please note that information about meeting link … out early August 2025 (previously early June) and expect to complete by mid-Augustlate October 2025 (previously late June).mid-August). How this will affect your organization: The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode> …

  6. Updated January 10,February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Please note that information about meeting link expiry changes related to this … 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 mid-Aprilmid-May 2025 (previously mid-February)mid-April) and expect to complete by late AprilMay 2025 (previously late March).April). 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. Rollout for scheduled meetings and channel Meet Now will be started in early July 2025 and expected to be completed by mid-July 2025. General Availability (GCC High, DoD):   We will begin rolling out early JuneAugust 2025 (previously mid-April)early June) and expect to complete by late June mid-August 2025 (previously late April).June). How this will affect your organization: The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode> …

  7. Updated December 2, 2024:January 10, 2025: We have updated the rollout timeline below. Thank you for your patience.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 … Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web).  This message is associated with Microsoft 365 Roadmap ID 381953. When this … (previously late January). General Availability (Worldwide, GCC): We will begin rolling out mid-Februarymid-April 2025 (previously mid-February) and expect to complete by late FebruaryApril 2025 (previously late March). General Availability (GCC High, DoD): We will begin rolling out early AprilJune 2025 (previously early December) mid-April) and expect to complete by late AprilJune 2025 (previously mid-January).late April). How this will affect your organization: Longer URLsThe 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: In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire.  Every meeting link expires in 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. 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 8 hours after creation for Meet Now. 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 the rolloutshort meeting URL release will continue working as it previously was (user will be able to work.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 URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode>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 … 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 …

  8. Updated September 18,December 2, 2024: We have updated the rollout timeline below. Thank you for your … 381953. When this will happen: Targeted Release: We will begin rolling out mid-Januarymid-February 2025 (previously early November) mid-January) and expect to complete by late JanuaryFebruary 2025 (previously mid-November).late January). General Availability (Worldwide, GCC): We will begin rolling out mid-February 2025 (previously mid-November)mid-February) and expect to complete by mid-Marchlate February 2025 (previously late November).March). General Availability (GCC High, DoD): We will begin rolling out early April …

  9. Updated July 5,September 18, 2024: We have updated the rollout timeline below. Thank you for your … 381953. When this will happen: Targeted Release: We will begin rolling out early November 2024 mid-January 2025 (previously early August)November) and expect to complete by mid-November 2024late January 2025 (previously mid-August).mid-November). General Availability (Worldwide, GCC): We will begin rolling out mid-November 2024mid-February 2025 (previously mid-August)mid-November) and expect to complete by late November 2024 mid-March 2025 (previously late August).November). General Availability (GCC High, DoD): We will begin rolling out early December 2024April 2025 (previously mid-September)early December) and expect to complete by mid-Januarylate April 2025 (previously late September).mid-January). How this will affect your organization: Longer URLs for meetings scheduled before …

  10. Updated May 17,July 5, 2024: We have updated the rollout timeline below. Thank you for your … When this will happen: Targeted Release: We will begin rolling out early AugustNovember 2024 (previously early June)August) and expect to complete by mid-Augustmid-November 2024 (previously mid-June).mid-August). General Availability (Worldwide, GCC): We will begin rolling out mid-Augustmid-November 2024 (previously mid-June)mid-August) and expect to complete by late AugustNovember 2024 (previously late June).August). General Availability (GCC High, DoD): We will begin rolling out mid-Septemberearly December 2024 (previously late June) mid-September) and expect to complete by late September 2024 mid-January 2025 (previously early July).late September). How this will affect your organization: Longer URLs for meetings scheduled before …

  11. Updated April 25,May 17, 2024: We have updated the rollout timeline below. Thank you for your … When this will happen: Targeted Release: We will begin rolling out early JuneAugust 2024 (previously early May)June) and expect to complete by mid-Junemid-August 2024 (previously mid-May).mid-June). General Availability (Worldwide, GCC): We will begin rolling out mid-Junemid-August 2024 (previously mid-May)mid-June) and expect to complete by late JuneAugust 2024 (previously earlylate June). General Availability (GCC High, DoD): We will begin rolling out mid-Junemid-September 2024 (previously late June) and expect to complete by late September 2024 (previously early July 2024.July). How this will affect your organization: Longer URLs for meetings scheduled before …

    • Tags Feature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact

    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. … When this will happen: Targeted Release: We will begin rolling out early MayJune 2024 (previously early May) and expect to complete by mid-May 2024.mid-June 2024 (previously mid-May). General Availability (Worldwide, GCC): We will begin rolling out mid-Maymid-June 2024 (previously mid-May) and expect to complete by earlylate June 2024.2024 (previously early June). General Availability (GCC High, DoD): We will begin rolling out mid-June 2024 …

  12. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 11:37 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current