(Update)Support for Events from email in Outlook is changing—Schema.org markup required for reliable calendar extraction
Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Action date
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw- Seen 8 Dec 2025
January 2026, January 31, 2026
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 removedWhat changed
Between archive captures, newest first- 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 - Act by
15 Dec 2025→ 30 Jan 2026 - Tags
Feature update, User impact, Admin impact, Retirement→ Updated message, Feature update, User impact, Admin impact, Retirement
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 … It is technically impossible to make further improvements to the old stack.
By January 2026,Without migration to Schema.org, theoldquality and reliability of event extractionstack will no longer be supported.will continue to degrade over time. Screenshot of Settings > Calendar > Events from email When this will happen:Legacy extraction will be retiredWe encourage providers to transition to Schema.org as early as possible, as continued reliance onJanuary 31, 2026. After this date, only emails using Schema.org markup willlegacy 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 besupported for automatic event extraction.fixed on the legacy stack, the only long-term solution is migration to Schema.org standards. How this affects your organization: Who is affected: Organizations whose users rely … (e.g., airlines, hotels, travel agencies, delivery services). What will happen: Emails that continue to rely on legacy extractionwill stop generating events after January 2026.may experience increasing failures, missing events, and incorrect calendar entries over time. Emails using Schema.org markup will continue to generate calendar events automatically. Partners … and more reliable event extraction. What you can do to prepare: Identifyproviders (e.g., airlines, hotels,your Corporate travelagencies, and delivery partners) that sendpartner(s) that are sending booking confirmation emails to yourusers. Work with thoseemployees and reach out to them for adopting Schema.org support To determine whether a provider is using Legacy or Schema.org, you can safely assume most providersto adopt Schema.org markup for supported scenarios. If you’d likeare still on Legacy- our data shows that 94% of providers remain on legacy extraction. To get more assistance on onboarding a provider toschema.org,Schema.org, please reach out to[email protected] along with your providerdetails.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, …- Title
- · first version seen
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
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.