One could say...
That this is all part of the cunning (or not so cunning) plan to get a boost in the market share for Windows Phones.
But I won't.
It is just a normal day when a critical service goes TITSUP.
Microsoft Exchange mobile users on Android and iOS users have been unable to access the service on their mobile devices due to a planned shift away from its Exchange Active Sync (EAS) protocol. The issue first appeared yesterday and is still affecting users. One customer got in touch to say: "Exchange Mobile device access …
> My reaction too for the Office 365 service provided by Namesco for Demon subdomains emails.
Because you did it wrong, sorry.
I had two separate subdomains to set up - the first, mine, went OK as I followed the instructions but I swore a lot because it was an indirected indirection web UI front for another web UI and I hate the new look for email on office 365 because MS can't make up their minds what to show me but now thankfully I am getting the proper old-style OWA webmail UI without the stupid multiple side window "friendly" crap.
The second setup went slightly awry because the "select primary email" does different things depending on where you do it. More swearing but completed correctly.
TLDR Nothing wrong with the instructions, I just hate the way MS buggered about with known interfaces to "improve" things.
Maybe it's really in response to an earlier reported problem that they cannot fix.
Question: is this why ActiveSync links for mobile devices that use Exchange calendaring always cost extra? Does this mean we are finally moving to a complete open standard where we can actually see what goes on inside? If so, hurray.
Microsoft Exchange mobile users on Android and iOS users have been unable to access emails on their phones due to a planned shift away from its Exchange Active Sync (EAS) protocol.
Perhaps this is true for those with MS-hosted Exchange or Office 365? My own EAS access is working just fine to my company's private MS Exchange clusters. The article is really badly vague on who is actually affected.
What do you mean "now". I've successfully been side-stepping exchange my IT career by employing open standards based protocols and infrastructure instead. Easy.
My business' email is working perfectly on all operating systems and devices*.
* Well except Outlook. Outlook doesn't do IMAP properly but I don't care about that.
The activesync protocol was created by microsoft and its they that demand a license fee for its use, if they were truly concerned about open access they could open up their existing protocol.
Similarly they could support existing open protocols for the various types of data (caldav, carddav, imap etc) instead of creating their own new protocols that do the same thing. By doing the latter they can create an impression of openness, while actually ensuring that competing clients will take time to catch up.
The other protocols you mention require a lot more data between the phone and the server to keep the phone up to date. Exchange Activesync can update the phone with changes or new emails with just one polling request evey 30 minutes at times when nothing happens on the server.
Biting the hand that feeds IT © 1998–2019