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

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, the old extraction stack will no longer be supported.

Screenshot of Settings > Calendar > Events from email

When this will happen:

Legacy extraction will be retired on January 31, 2026. After this date, only emails using Schema.org markup will be 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 rely on legacy extraction will stop generating events after January 2026.
• Emails using Schema.org markup will continue to generate calendar events automatically.
• Partners using Schema.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, travel agencies, and delivery partners) that send confirmation emails to your users.
• Work with those providers to adopt Schema.org markup for supported scenarios.
• If you’d like assistance onboarding a provider to schema.org, please reach out to [email protected] along with your provider details. 
• Communicate this change to helpdesk staff.

Compliance considerations

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