Back to latest version

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

Message Center

Metadata at Sep 24, 2025

Published

Sep 24, 2025

Service

Microsoft 365 suite

Tag

Major change
Feature update
User impact
Admin impact
Retirement

Act by

Dec 15, 2025

Metadata changes

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

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.
  • Without migration to Schema.org,By January 2026, the quality and reliability of eventold extraction stack will continue to degrade over time.no longer be supported.

Screenshot of Settings > Calendar > Events from email

user settings

When this will happen:

We encourage providers to transition to Schema.org as early as possible, as continued reliance Legacy extraction will be retired 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 cannotJanuary 31, 2026. After this date, only emails using Schema.org markup will be fixed on the legacy stack, the only long-term solution is migration to Schema.org standards.supported for automatic event extraction.

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 may experience increasing failures, missing events, and incorrect calendar entries over time.will stop generating events after January 2026.
  • 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 your Corporateproviders (e.g., airlines, hotels, travel partner(s)agencies, and delivery partners) that are sending bookingsend confirmation emails to your employees and reach outusers.
  • Work with those providers to themadopt Schema.org markup for adopting Schema.org support
  • To determine whether a provider is using Legacy or Schema.org, you can safely assume most providers are still on Legacy- our data shows that 94% of providers remain on legacy extraction.supported scenarios.
  • To get moreIf you’d like assistance on onboarding a provider to Schema.org,schema.org, please reach out to [email protected] along with your provider details/contacts and the domains from which these mails are sent, so they can be whitelisted. A detailed onboarding & testing process will be shared.details. 
  • Communicate this change to helpdesk staff.

Compliance considerations

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