Forum Discussion
Outlook <-> Exchange Protocols
MAPI is an established, well-used protocol for the Windows client.
OK - understood - but to quote the documentation:
"Protocol consolidation: Today, each Outlook client platform utilizes a different data sync protocol, which hinders the ability to innovate and deploy new features quickly across all Outlook clients. The native Microsoft sync technology that Outlook for iOS and Android is adopting has been in use by the native Windows 10 mail client for a number of years, and in the future, will be used by Outlook for Mac."
Following that logic, getting all versions of Outlook to a universally used protocol would help foster innovation and make feature parity easier to develop. Plus I am sure the Exchange team would love to only have to support a single connection method.
Clearly the desktop team has decided not to follow this path - just wondering if there was a reason why (technically) or if it just wasn't something they felt like taking on right now.
iragsdale Not every scenario/feature is supported in every data sync protocol or client.
Ross Smith IV so is it Microsoft's position that these sorts of feature enhancements will not be available or supported using third-party clients?
Daniel Ochoa Exchange ActiveSync is still a licensed protocol for use by OEMs and others. I don't recall seeing any deprecation announcements. Outlook will continue to invest in its own protocol to provide enhancements, some of which are simply not possible with what exists in ActiveSync today (e.g., ActiveSync doesn't support permission models, which is why it cannot provide shared/delegate mailbox/calendar access).
- So with Activesync deprecated and no new functionality being added for it what will 3rd party clients do to support some of the newer features being added into this native sync technology? An example is being unable to sync the "Other" category for a contact which is unsupported by AS but is supported via this new sync protocol that Outlook mobile uses.
Thanks for the detailed explanation. Just wanted to check whether new communication protocol "Hx" is supported by Intune email profile deployment. Also, can this protocol be used by Windows native Mail client?I'm familiar with what I wrote. :)
Today, we support 5 different data sync protocols (EAS, EWS, REST, MAPI/HTTP, native sync technology), or 6 if you include the deprecated RPC/HTTP protocol.
The first three (likewise for RPC/HTTP) are available for third-parties to consume, which means development on those stacks has to be well thought out as changes have a broad impact across the ecosystem (just like changes in RPC was hard due to RPC being used by everything in the Windows stack).
MAPI/HTTP and the native sync technology are proprietary protocols that are only available to Outlook (and are owned by Exchange/Outlook). There are many features that exist in Outlook desktop, that today, don't exist in the other platforms (e.g., sensitive labeling). By consolidating Mac and mobile clients to a single data sync protocol, we will be able to innovate faster and bring desired features to those platforms. Likewise, we'll continue innovating in Outlook desktop and MAPI (which is a well-established protocol for Outlook desktop, spanning a 20 year history).
