Back to latest version
Comparing Sep 24, 2025 latest (Dec 8, 2025) Swap

MC1158908 - (Update)Support for Events from email in Outlook is changing—Schema.org markup required for reliable calendar extraction

Message Center

Metadata at latest

Last Updated

Dec 8, 2025

Published Sep 24, 2025

Service

Microsoft 365 suite

Tag

Major change
Updated message
Feature update
User impact
Admin impact
Retirement

Act by

Jan 30, 2026

Metadata changes

Title
Support for Events from email in Outlook is changing—Schema.org markup required for reliable calendar extraction(Update)Support for Events from email in Outlook is changing—Schema.org markup required for reliable calendar extraction
Tags
Admin impact, Feature update, Retirement, User impactAdmin impact, Feature update, Retirement, Updated message, User impact
Action required by
Dec 15, 2025Jan 30, 2026

Body changes

removed textadded text

Updated December 8, 2025: We have updated the content and timeline. Thank you for your patience. 

Introduction

Outlook’s Events from email feature helps users stay organized by automatically adding reservations such as flights, hotels, rental cars, and deliveries to their calendars.  To improve reliability and ensure this feature continues to work smoothly, we strongly encourage all providers to adopt Schema.org markup in their transactional emails. This change aligns with industry standards and improves accuracy, consistency, and long-term support.

Until now, Outlook has relied on legacy extraction to support this feature. However:

  • Legacy extraction is fragile, and once templates fail, they cannot be fixed.
  • We are receiving increasing reports of incorrect or missing events.
  • It is technically impossible to make further improvements to the old stack.
  • By January 2026,Without migration to Schema.org, the oldquality and reliability of event extraction stack will no longer be supported.continue to degrade over time.

Screenshot of Settings > Calendar > Events from email

user settings

When this will happen:

Legacy extraction willWe encourage providers to transition to Schema.org as early as possible, as continued reliance on legacy support is not sustainable. Organizations that do not migrate may experience a gradual decline in the accuracy, reliability, and consistency of automatically generated events. These issues cannot be retiredfixed on January 31, 2026. After this date,the legacy stack, the only emails usinglong-term solution is migration to Schema.org markup will be supported for automatic event extraction.standards.

How this affects your organization:

Who is affected:

  • Organizations whose users rely on Outlook’s Events from email feature.
  • Partners and providers who send transactional emails (e.g., airlines, hotels, travel agencies, delivery services).

What will happen:

  • Emails that continue to rely on legacy extraction will stop generating events after January 2026.may experience increasing failures, missing events, and incorrect calendar entries over time.
  • Emails using Schema.orgSchema.org markup will continue to generate calendar events automatically.
  • Partners using Schema.orgSchema.org markup report up to 30% higher engagement and more reliable event extraction.

What you can do to prepare:

  • Identify providers (e.g., airlines, hotels,your Corporate travel agencies, and delivery partners)partner(s) that sendare sending booking confirmation emails to your users.employees and reach out to them for adopting Schema.org support
  • Work with thoseTo determine whether a provider is using Legacy or Schema.org, you can safely assume most providers to adopt Schema.org markup for supported scenarios.are still on Legacy- our data shows that 94% of providers remain on legacy extraction.
  • If you’d likeTo get more assistance on onboarding a provider to schema.org,Schema.org, please reach out to [email protected] along with your provider details.details/contacts and the domains from which these mails are sent, so they can be whitelisted. A detailed onboarding & testing process will be shared. 
  • Communicate this change to helpdesk staff.

Compliance considerations

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