Microsoft Roadmap, messagecenter and blogs updates from 29-01-2026

Updated January 28, 2026: We have updated timelines for enforcement. The scope of the change remains unchanged. Thank you for your patience.

We’re updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.

[When this will happen:]

Rollout will begin in February 2026 (previously October 2025) and complete by April 2026 (previously November 2025).

[How this affects your organization:]

This update changes the string format of specific properties returned by Exchange Online cmdlets. For example, the Database property in the output of Get-Mailbox will change from:

Database : APCP153DG038-db080

to:

Database : APCP153.PROD.OUTLOOK.COM/7ad9dea1-26b7-4088-ad73-708c219faff6

This change applies only to Exchange Online. On-premises Exchange environments are not affected.

We do not expect organizations to have dependencies on these output formats. These values are informational only and not intended for admin control or automation. No changes to user workflows, admin configurations, or help desk processes are expected.

[What you can do to prepare:]

No action is required. There are no settings or controls to manage this change. If you have scripts that parse these property values, we recommend reviewing them to ensure compatibility.

The complete list of cmdlets impacted is as follows: 

The affected properties for each Output Type are as follows:

Updated January 28, 2026: Note: The February rollout will begin with the Desktop and Web platforms. The Mobile rollout will start later. We will update the timelines when they are available.

Coming soon for Microsoft Copilot in Teams: Intelligent meeting recap will be able to incorporate content shared on screen into the AI-based summary provided after the meeting, providing a richer and more comprehensive recap of the meeting. Intelligent meeting recap will capture details shown when a participant shares their screen, ensuring those unspoken insights become part of the meeting recap.

This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.

This feature requires a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 490052.

[When this will happen:]

Targeted Release: Rollout begins in early February 2026 and completes by mid-February 2026.

General Availability (Worldwide): Rollout begins in mid-February 2026 and completes by late February 2026. 

[How this will affect your organization:]

Copilot users will receive intelligent recap summaries that incorporate shared-screen content, preserving every detail and its context.

This feature will be available by default with no admin controls.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.

Learn more: Intelligent recap for Teams calls, meetings, and events – Microsoft Teams | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated January 28, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

The Rate My Call survey is a feedback screen that the Teams client will occasionally present to users after their Teams call or meeting has completed. Currently, the rating presents 1-5 stars on the first page and a list of potential issues (called problem tokens) on the second page.

We will be rolling out a new streamlined feedback experience for Teams on Windows, Mac, and Web that presents the feedback on a single screen with a thumbs up / thumbs down rating system and problem tokens for the user to select, plus an area to provide details. In testing, we found higher feedback returns with this new design, and clearer insights into call quality issues.

Screenshot 1: New Rate My Call User Interface

[When this will happen:]

• General Availability/Targeted Release: Rollout begins mid-February 2026 (previously late January), completes by late February 2026 (previously late January).

Who is affected: Users of Microsoft Teams on Windows desktop, Mac, and Web clients

What will happen:

• Users will see a new Rate My Call screen after calls and meetings
• The new screen includes:
  • Thumbs up / thumbs down rating
  • Optional problem tokens
  • Optional free-text field for additional details
• Feedback Rating values in Call Quality Dashboard (CQD) will change:
  • 5: Thumbs up / Good
  • 1: Thumbs down / Had issues
  • 0: Survey shown but not submitted
  • Null: Survey not shown
• Problem tokens will still be recorded even if a rating (thumbs up or down) is not submitted
• Admins may notice an increase in poor feedback metrics due to the new rating method; this does not reflect a decline in service quality

• Communicate this change to helpdesk and support staff
• Update internal documentation to reflect the new feedback format
• Monitor PCR (Poor Call Rate) telemetry until it stabilizes, then set your own threshold

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Q: Will a higher PCR mean calls are worse?
A: No. The new design captures more dissatisfied users by reporting a higher willingness to report poor calls. The increase is a measurement effect, not a quality regression.

Q: What is the new PCR target or threshold for your workstreams?
A: We cannot provide a fixed PCR threshold. Your action is to monitor your own PCR telemetry until it stabilizes (both volume and value relatively flat), then set your threshold. Stabilization may take weeks and once the data converges, you can then set your own.

Updated January 28, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing new Word, Excel, and PowerPoint agents in Microsoft 365 Copilot to help users create documents, workbooks, and presentations more efficiently in Copilot Chat within the Frontier program. These agents assist with creating documents, workbooks, and presentations by using web and enterprise grounding. Each agent supports multi-turn chat, enabling user to refine content through an interactive back-and-forth conversation.

[When this will happen:]

• General Availability: We will begin rolling out on February 5, 2026 (previously January 29).

[How this affects your organization:]

If your organization is part of the Frontier program and has enabled Anthropic usage in your tenant, users will be able to access Word, Excel, and PowerPoint agents via the navigation pane in the M365 Copilot app or within the Tools menu in Copilot chat across Word, Excel and PowerPoint. Additionally, users can invoke these agents by typing “@” followed by the agent name (for example, @PowerPoint).

Who is affected:

• Copilot Chat users in the Microsoft 365 Copilot app in the Frontier Program.

What will happen:

• Users will have access to the following Copilot agents:
• Word agent: Assists with research, formatting, layout, and content refinement for documents such as strategic plans, policy documents, and technical papers.
• Excel agent: Supports data analysis, formula generation, trend identification, and summarization of insights.
• PowerPoint agent: Helps generate presentations from outlines or documents, suggests layouts, and refines visual storytelling.
• Each agent supports multi-turn chat for iterative content development.
• Users can perform high-level iterations on the generated files via chat directly in the Word, Excel, and PowerPoint agents. For more extensive or granular editing, users can open their documents in the respective applications.



• The feature will be ON by default for tenants with Copilot access, Frontier enabled, and for tenants who have opted into Anthropic usage. If Anthropic usage is disabled by the admin, the agents will not appear in the user experience. Learn more: Connect to Anthropic’s AI models | Microsoft Learn.

[What you can do to prepare:]

• No action is required at this time.
• Communicate availability to helpdesk or content teams.
• If desired, review internal documentation or training materials to reflect the new capabilities.

Learn more: Get started with Word, Excel, and PowerPoint Agents in Microsoft 365 Copilot (Frontier)

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated January 26, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re retiring the Microsoft Defender for Endpoint (MDE) Advanced Hunting API and Microsoft Defender XDR Advanced Hunting API and transitioning customers to the Microsoft Graph Security API. This update aligns our security integrations with a unified interface and schema across Microsoft Defender products. The Microsoft Graph Security API provides broader data coverage, improved consistency, and better scalability for automation and security workflows.

[When this will happen] 

• Retirement start: February 6, 2026
• Full retirement: February 1, 2027
• After February 1, 2027, the MDE and XDR APIs will no longer function.

[How this affects your organization]

Who is affected: 

• Organizations using the MDE or XDR Advanced Hunting API for automation, integration, or custom workflows.
• You are receiving this message because our reporting indicates your organization may be using these APIs.

What will happen:

• The MDE and XDR Advanced Hunting APIs will stop functioning after February 1, 2027.
• Existing scripts, automations, and workflows that rely on these APIs will fail if not updated.
• The Microsoft Graph Security API will be the supported API for accessing Microsoft security data.
• No automatic migration will occur; manual updates will be required.

[What you can do to prepare]

• Migrate all existing API workflows to the Microsoft Graph Security API by January 31, 2027.
• Update internal documentation, automation scripts, and integration endpoints to use the Microsoft Graph Security API.
• Communicate these changes to your security operations, engineering, and development teams.
• Review Microsoft documentation to plan your migration: Use the Microsoft Graph security API.
• If your organization uses custom solutions, validate that new queries and response schemas work as expected before the retirement date.

Learn more:

• Advanced hunting – Use the Microsoft Graph security API | Microsoft Graph | Microsoft Learn
• Migrate from the older APIs – Use the Microsoft Graph security API | Microsoft Graph | Microsoft Learn
• (to be retired) Advanced Hunting API – Microsoft Defender for Endpoint | Microsoft Learn
• (to be retired) Microsoft Defender XDR advanced hunting API – Microsoft Defender XDR | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Introduction

Email customization for Site Lifecycle Management (SLM) policies is now generally available. This update allows SharePoint admins to tailor notification emails sent to site owners during policy execution. Customizable emails help organizations provide clearer, contextual communication aligned with internal governance standards.

When this will happen:

General Availability (Worldwide, GCC, GCC High): This feature is now available for all SLM policies, including Inactive Sites Policy, Site Ownership Policy, and Site Attestation Policy.

How this affects your organization:

Who is affected:
SharePoint administrators managing SLM policies.

What will happen:

• Admins can customize subject line, message body, and guidance URL in SLM policy emails.



• Default system emails are used unless custom templates are configured.
• No changes are introduced to existing policy behavior.

What you can do to prepare:

No action is required if default templates meet your needs.

• Review internal messaging and governance guidelines.
• Identify preferred language for clearer site owner communication.
• Create or update custom email content in the policy configuration flow.

Learn more: Customize email notifications

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

To align with the Android platform lifecycle and ensure customers remain protected with the most up‑to‑date security capabilities, Microsoft Defender for Android will end support for devices running Android 10. After support ends, Defender on Android 10 devices will no longer receive feature updates, security fixes, or technical support. Devices running Android 11 or later will continue to be fully supported.

[When this will happen]

Support for Microsoft Defender on Android 10 devices will end on March 31, 2026.

[How this affects your organization]

You are receiving this message because our reporting indicates your organization might have devices running on Android 10.

Who is affected: Organizations with users or managed devices running Android 10 and using Microsoft Defender for Android.

What will happen:

• Existing installations of Microsoft Defender for Android on Android 10 devices will continue to function, but:
  • They will no longer receive new features.
  • They will no longer receive security updates.
  • They will no longer receive technical support.
• New installations on Android 10 devices will no longer be available after support ends.
• Devices updated to Android 11 or later will continue to receive full support.

[What you can do to prepare]

No admin action is required for this change to occur. To prepare:

• Identify Android 10 devices using your organization’s device management tools.
• Encourage users to upgrade eligible devices to Android 11 or later.
• Replace devices that cannot be upgraded, if necessary.
• Update internal documentation and support team guidance.
• Notify impacted users about the upcoming end of support.

If needed, refer to Microsoft Defender for Endpoint documentation for minimum platform requirements.

Learn more: Microsoft Defender for Endpoint on Android | Microsoft Defender | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

[Introduction]

To help organizations analyze more recent Microsoft 365 Copilot usage trends, we’re adding a new export option in the Copilot dashboard. In addition to the existing user‑week export (see MC1173208), dashboard users with company‑level access will be able to export a subset of de‑identified Copilot usage metrics aggregated by user and day. This option includes 28 days of activity data and supports more granular, short‑term insights into Copilot adoption. Exported data will usually reflect copilot activity up to 3 days before the export date; actual timing may vary 

A minimum of 50 Microsoft 365 Copilot licenses is required. This feature applies to the Viva Insights web app.

This message is associated with the Microsoft 365 Roadmap ID 547749.

• Screenshot 1 – Export data button in Copilot dashboard:



• Screenshot 2 – Copilot dashboard export options:

  

[When this will happen]

• Public preview: Early March 2026 – late March 2026
• General availability (Worldwide): Early April 2026 – late April 2026

[How this affects your organization]

Who is affected

This feature is available to Copilot dashboard users with full company-level data access, including:

• Senior leaders (as identified in Entra ID)
• Admin‑assigned company‑level users
• Delegates with company‑level access
• Global analysts and admins
• Group managers with access restricted to their own teams won’t have access to the user-day export.

What will happen

• A new export option will allow eligible users to download de-identified, row-level Copilot usage metrics aggregated by user and day, covering the most recent 28 days.
• Organizations can use this export to assess short-term usage patterns, support tactical adoption efforts, optimize licensing, and evaluate the impact of recent changes.
• Exported data will usually reflect copilot activity up to 3 days before the export date; actual timing may vary
• The export supports analysis across Copilot-enabled apps (for example, Word, Excel, Teams) and includes two additional attributes: Organization and Job function.
• Copilot activity metrics in exports run within 2 days of Copilot license assignments or removals may not reflect those license changes. Exports run after the 2‑day window will accurately reflect the impact of those license changes in copilot activity metrics under normal conditions.
• Data in previously exported files will not be automatically updated or modified after the export is generated.
• Access to the new user‑day export uses the same Viva Feature Access Management (VFAM) controls as the existing user‑week export (Viva Insights → Copilot Metrics Export). No new access controls are introduced. Existing VFAM settings for the Copilot dashboard export will remain in effect and apply to both day and week level export options after the day level export is released. Please read MC1173208 for more details.

[What you can do to prepare]

• Review and update VFAM settings for users with company‑wide access to the Copilot dashboard.
• Inform eligible users about this new export option.
• No additional admin configuration is required if export functionality is already enabled.
• Admins may disable the export feature for the tenant or specific groups at any time through VFAM.

Learn more:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn
• Microsoft Viva Feature access management | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Introduction

We’re improving how alerts show up in Microsoft Defender XDR incidents to help your SOC prioritize actionable work and keep investigations moving efficiently. Starting January 25, 2026, administrators will see the new built in alert tuning experience in the portal UI. During this initial period, the experience is visible, but the built-in tuning won’t be active yet.

The review & opt out window runs from January 25 through February 5. During this time, you can review the new settings and decide whether to keep the default experience enabled or disable it for your organization.

What’s going live on February 5, 2026

On February 5, 2026, the functionality becomes active:

• Initial rule set: The initial set of rules focuses on Microsoft Defender for Office 365 (MDO), with 12 built in rules designed for informational and low severity Defender for Office alerts. More built-in rules will be added over time, expanding coverage to additional workloads. You’ll receive advance notification so you can review upcoming additions and opt out before they take effect in your environment.
• Automated triage with AIR: For selected alerts with Automated Investigation and Response (AIR) playbooks, Defender will automatically run an immediate investigation to help determine whether SOC attention is required.
• Reopen when needed: If the investigation indicates that additional review is needed, the alert will reopen as “New” and return to your queue for analyst action.

Included in this release (MDO alert types)

The 12 built in rules in this release apply to the following alert types:

• User requested to release a quarantined message
• Email reported by user as junk
• Email reported by user as not junk
• Email reported by user as malware or phish
• Tenant Allow/Block List entry is about to expire
• Removed an entry in Tenant Allow/Block List
• Email messages removed after delivery
• Email messages from a campaign removed after delivery
• Email messages containing malicious file removed after delivery
• Email messages containing malicious URL removed after delivery
• Admin Submission Result Completed
• Admin triggered manual investigation of email

How this affects your organization

• Default experience: Built in tuning is designed so analysts can focus on alerts most likely to require action, while automated triage runs in the background for eligible alerts.
• Customer control: You remain in control – built in rules are visible in the portal and can be disabled at any time in Alert Tuning.

What you need to do to prepare

• No action is required if you want to use the default experience and benefit from more streamlined queues and faster prioritization.
• If your SOC prefers to manually review every alert without automated triage, use the opt out window (Jan 25–Feb 5) to disable built in tuning in Alert Tuning.

Multi-Tenant Management (MTO) content distribution

If you manage multiple tenants, you can manage built in alert tuning rules at scale using the MTO portal content distribution capability. Configure which built in rules are enabled/disabled in a source tenant and distribute that configuration across your managed tenants for consistent settings everywhere.

Learn more

• Public documentation: Built-in alert tuning rules 
• Announcement blog: Microsoft Defender XDR Blog

[Introduction]

We’re adding support for pay-as-you-go (PAYG) consumption for the Microsoft 365 Copilot Retrieval API. This update gives organizations a flexible way to extend Retrieval API access to users without Microsoft 365 Copilot licenses, while keeping admin control over data access and billing. Users with Copilot licenses will continue to be able to access the Retrieval API at no additional cost.

[When this will happen]

• Public Preview Release (Worldwide): We will begin rolling out in Preview in late January 2026 and expect to complete by early February 2026.
• General Availability (Worldwide): We will begin rolling out in GA in late February 2026 and expect to complete by early March 2026.

[How this affects your organization]

Who is affected:

• Admins managing Microsoft 365 Copilot services and billing
• Tenants using or planning to use the Copilot Retrieval API

What will happen:

• A new PAYG option for the Copilot Retrieval API becomes available in the Microsoft 365 admin center under Copilot → Billing & usage → Pay-as-you-go.
• When enabled by an admin, non-Copilot licensed users can use the Retrieval API to access these tenant-level Microsoft 365 data sources:
  • SharePoint
  • Copilot connectors
• User-level data sources (for example, OneDrive) will remain unavailable to non-Copilot licensed users.
• A minimum of one Microsoft 365 Copilot license must be active in the tenant to enable the PAYG feature.
• The feature is off by default and requires explicit admin configuration.

[What you can do to prepare]

• Ensure your tenant has at least one Microsoft 365 Copilot license.
• Decide whether to enable PAYG for:
  • Specific groups (recommended), or
  • All non-Copilot licensed users.
• Review and update any internal documentation related to Copilot usage or data access controls.
• If needed, communicate the change to your helpdesk or impacted user groups.
• Configure the feature in the Microsoft 365 admin center under Copilot → Billing & usage → Pay-as-you-go.

Learn more: Overview of the Microsoft 365 Copilot Retrieval API | Extensibility | Microsoft 365 Copilot | Microsoft Learn

[Compliance considerations]

[Introduction]

We’re updating the SharePoint Maps web part to use Azure Maps as its data provider. This migration modernizes the mapping experience, improves reliability, and aligns SharePoint with Microsoft’s long-term mapping platform strategy. Most existing functionality will continue to work as expected.

[When this will happen:]

General Availability (Worldwide, GCC): Rollout will begin in early March 2026 and complete by mid-April 2026.

[How this affects your organization:]

Who is affected:

• Organizations using the SharePoint Maps web part (formerly Bing Maps) on modern SharePoint pages.
• Admins responsible for allowlists, network security, or governance of SharePoint sites.

What will happen:

• The Bing Maps web part will be renamed to Maps.
• Azure Maps services are currently available except in China. 
• Place and Address search will continue to work.
• Business Entity search (searching for organizations or points of interest by name) will no longer be supported.
• Autosuggestions will no longer support Chinese, Japanese, or Korean.
• Bird’s eye and Street view modes will be removed, with automatic fallback to Road view.
• No admin toggle is provided; migration occurs automatically.

[What you can do to prepare:]

• Add atlas.microsoft.com to your organization’s allowlist if applicable.
• Confirm network access, firewall, and proxy configurations allow traffic to this domain.
• Review SharePoint pages that use the Maps web part.
• Communicate this change to site owners or helpdesk staff.
• Update internal documentation if needed.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

• Microsoft Office is used
• Scan Cab is used to check for update compliance
• The January 2026 Scan Cab was deployed before 2:30 PM PT on January 27, 2026.

• Updated Scan Cab: Download the new Scan Cab here
• CVE-2026-21509: Microsoft Office Security Feature Bypass Vulnerability
• Security Update for Microsoft Office 2016 (KB5002713)
• Announcing a smaller WSUS Scan Cab – Microsoft Tech Community: Learn more about WSUS and the Scan Cab process
• Using WUA to Scan for Updates Offline – Win32 apps | Microsoft Docs: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update
• WSUS and the Catalog Site | Microsoft Docs: The Catalog Site used by WSUS to import updates and drivers

We've released updates to the following update channel for Microsoft 365 Apps:

• Current Channel

[When this will happen:]

We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting January 27th, 2026 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download this latest update and begin deployment.

[What you need to do to prepare:]

To get more details about this update view the following release notes:

• Current Channel

• Agents: Agents created in Copilot Studio and Microsoft 365 Copilot Agent Builder.
• Apps: Apps created in Power Apps and Microsoft 365 Copilot App Builder agent.
• Flows: Agent flows from Microsoft Copilot Studio, cloud flows from Power Automate, and workflows from Microsoft 365 Copilot Workflows agent.
• Environments: All environments in your tenant.
• Environment groups: All environment groups in your tenant.

• Environment groups support: Filter and organize inventory by environment group membership
• Power Platform for Admins V2 connector: Query inventory data directly from Power Automate workflows

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.