According to a tweet from Outlook boss Javier Soltero last night, a future version of Exchange will support these authentication methods for on-premises deployments. The Outlook clients, which use Active Sync in their own particular way to communicate with Exchange, are a good example of software that follows a fast development cycle.
The same is true for the multitudinous Android vendors, each of whom has their own take on what a perfect email client should behave.
Beyond on premises installations of Exchange, the various personal and enterprise hosted services from Microsoft also utilize EAS, including and Office 365.
In addition to support on Windows Phone, EAS client support is included on Android, This version of EAS communicated over Web-based Distributed Authoring and Versioning (Web DAV) to Exchange 2000 servers syncing Email, contacts, and calendar and allowed users to select a folder list to sync but this was only for email folders (not contacts or calendars).
Microsoft could never control how EAS licensees wrote code in their email clients to communicate with Exchange, so they have concentrated on bullet-proofing the server in the recent past so that any egregious client code can’t cause problems for Exchange.
I think Microsoft has done a good job here because the chorus of concerns that used to accompany new releases of i OS and Android has calmed to a whimper.