MAPI
Concept
MAPI (Messaging Application Programming Interface) is a proprietary Microsoft messaging API and data model underlying Exchange and Outlook, whose legacy data structures still shape Exchange development.
Description
MAPI, short for Messaging Application Programming Interface, is a proprietary Microsoft messaging API and data model that underlies Exchange and Outlook. Its legacy data structures still influence how developers work with Exchange data today, even when they use newer interfaces to reach it. The term is used both for the programming interface itself and for the way mailbox content is modeled beneath it.
According to the Microsoft Learn reference, MAPI is the Microsoft Outlook Messaging API and provides the messaging architecture for Outlook 2013 and Outlook 2016. It supplies interfaces, functions and data types that developers use to build Outlook messaging applications. Applications and transports use MAPI to work with email data, to create messages and the folders that hold them, and to receive notifications when MAPI-related data changes. The reference page applies only to Outlook 2013 and Outlook 2016 and does not list individual interfaces, functions or code examples.
The Microsoft Learn reference is organized into four parts: a getting-started overview, sample applications, concept guides for understanding and programming with MAPI, and the reference for its programming elements. For developers who are new to the area, the page points to a separate article on selecting the right API or technology for developing Outlook solutions. That guidance reflects a common decision: MAPI is one option among several, and the choice depends on the type of solution being built.
In practice, MAPI matters most when existing code has to be moved to newer technologies. The M365.FM episode "Migrate Exchange Web Services to Microsoft Graph with Glen Scales [MVP]" touches on this. The episode notes that some workflows need special attention when moving from Exchange Web Services to Microsoft Graph, especially those involving archive mailboxes or public folders. It also says that creating mail from raw MIME with MAPI extended properties can require rethinking a workflow, because that approach does not carry over unchanged. Advanced delta semantics are listed as another difference between EWS and Graph that may require rework of parts of the code.
The episode presents these points as a table of migration challenges: archive mailbox access and some mailbox import and export workflows require special attention, public folder scenarios need engagement with Microsoft for dependencies, and advanced delta semantics differ between the two APIs. MAPI extended properties appear in this list because they are one of the places where the older data model leaks into application code, so teams that depend on them have to review those parts of a migration separately.
For administrators and developers, the practical consequence is that knowledge of MAPI remains relevant for reading older Exchange and Outlook code, for understanding how messages, folders and notifications are structured, and for assessing the effort of a move to Microsoft Graph. Because the available sources describe MAPI mainly in the context of Outlook 2013 and Outlook 2016 and in the context of EWS-to-Graph migration, anyone planning work should confirm current support and requirements in the official documentation for the specific scenario.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|---|
| Wikipedia | MAPI – Wikipedia en.wikipedia.org |
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What is MAPI? (AI)
MAPI (Messaging Application Programming Interface) is a proprietary Microsoft messaging API and data model underlying Exchange and Outlook. Microsoft Learn describes it as providing the messaging architecture for Outlook 2013 and Outlook 2016.
What can applications do with MAPI? (AI)
Applications and transports use MAPI to work with email data, to create messages and the folders that hold them, and to receive notifications when MAPI-related data changes.
Why does MAPI come up in Exchange Web Services to Microsoft Graph migrations? (AI)
The episode "Migrate Exchange Web Services to Microsoft Graph with Glen Scales [MVP]" says that creating mail from raw MIME with MAPI extended properties can require rethinking workflows when moving to Graph.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Sources
- MAPI – Wikipedia en.wikipedia.org
- Outlook MAPI Reference – Microsoft Learn learn.microsoft.com
Maintained by Mirko Peters (Microsoft MVP) · Last updated: