Sign up for Office 365
Learn more about Office 365
Update 4/23/2012: Microsoft has completed deployment of a solution that eliminates the need for manual server reconfiguration of the affected devices when your Office 365 server location changes. We continue to work with device manufacturers to help them resolve their Exchange ActiveSync protocol implementation issues.
Update 3/5/2012: In order to mitigate issues with some mobile device implementations of redirection, Microsoft is currently deploying an interim solution that should eliminate the need for manual server reconfiguration of the affected devices when your Office 365 server location changes. We estimate that the fix will be fully deployed worldwide by April 30th, 2012. Look for the announcement on the blog when the fix is fully deployed with instructions for reconfiguring affected devices. In the meantime, we continue to work with device manufacturers to help them resolve their Exchange ActiveSync protocol implementation issues.
More complete information is now available in this article on the EHLO blog that explains how mobile devices connect to Exchange Online (Office 365) service and how the connectivity may be impacted if the device does not support certain Exchange ActiveSync (EAS) protocol requirements: http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx
1 out of 4 people found this post helpful.
Hi, I have issue described here. My Android 2.3.5 build-in client has stopped working with my account using ActveSync on 22.01.2012. I've tried tricks described here: m.outlook.com, Username in format: contoso.com\tony@contoso.com, in format: \tony@contoso.com. Nothing has helped. What am I missing? Please help.
This issue is much worse that described above. This is effective every Android, IPhone, and Blackberry in our company. m.outlook.com doesn't fix the issue for any of the phones we have tested it on. Instead we have to use the host name in the url for Outlook Web Access. The problem there is that that host name seems to change every few days.
We went with a managed solution (Office 365) to reduce the we have to deal with only to have a change pushed out with no notice that affects all of our mobile email users. There should have been an email detailing the issues before it was pushed out, and when there were so many issues, they should not have pushed it out.
A small number my ass. It's a huge number of phones. Please don't try to sweep this under the rug Microsoft. Right now you have to use your hostname and it changes quite frequently so your email/calendar will routinely break on every mobile device in your organization. This is completely unacceptable.
Hi
Can anybody please direct me to the OWA settings in my 365 account as I am experiencing the problems listed below as are a number of my colleagues.
Hi - Specifically which characters to use from the OWA hostname? hostname.outlook.com/owa or just hostname.outlook.com or...
Cheers
Rob
Please solve this asap, suddenly 30% of our users are unable to connect using activesync on their Android phones. We tried all sorts host names without success so far.
Changing the server details to m.outlook.com on both my iphone4S and ipad2 fixed the sync problem first time. All emails, contacts calendar events, etc updated on each device within a few minutes and everything is working fine.
I did notice when checking the 'settings' for each account that the server name changed automatically from m.outlook.com to something else which I presume has something to do with auto-discovery, but as I said, all working just fine.
What is the status on this issue? Is Microsoft doing anything to solve this?
neither server-address pod.51013.outlook.com, or m.outlook.com works.Do you call all Android users " a small subset of mobile devices"? I suggest that you check your statistics concerning the sales of mobile devices. Everyone does not run MS WIN or Apple OS..........yet!
Give us some new info, this clearly does not work. MS made the change, they should fix this mess.
Same problems for us on all our android 2.3.5 phones, the server says the phone is not compatible with the server security features. Our server is also pod.51013.outlook.com, they worked find till about the 23rd Jan 2012.
Unfortunately, this is a bug in the Android software, mine is 2.3.5. Please help by pushing this issue to the Android community. I do, however resent the Microsoft policy to answer by no answer when they regard themselves as "innocent"
Fixed the problem by using the following server address: "hostname.outlook.com" by getting the hostname from the OWA address bar. Don't copy anything after outlook.com from OWA. It worked immediately for me. I'm using a Sprint Samsung Epic 4G Touch with the EL29 build.
Touchdown for Exchange worked without a hitch using the server: "pod51010.outlook.com" but the native Android Exchange needed the alternative server address above.
ii88tek's solution has just worked on my S2 running 2.3.5 - although I'm sure I had already tried that combination earlier in the week so I suspect something has changed, again.
I suspect Microsoft have made a server change, it's working alright on my Samsung Galaxy S2 now, did not a few days ago with the same settings.
This affects all the NON WINDOWS Phone. So it is not Small Sub-set.
You can get around it by typing server address m.outlook.com and wait about 5 - 10 minutes and then your phone will start getting email back. However, issue is with how iPhone and Android ActiveSync work with redirections. m.outlook.com will redirect your request to the server where your mailbox is residing at that point in the time. It will also update your settings on your phone to that server address. So Mail setting will change to snXXprdXXX.outlook.com permanently.
then after few days, when Microsoft performs maintenance, it will move your mailbox to the different server and your ActiveSYNC will break again.
So question is,
1. How seriously Microsoft is working to resolve it? This is a huge issue for large organization.
2. Active SYNC is Microsoft's Technology, does not they provide guidelines for Companies, who use it, to design application as per their specification?
Microsoft, this is serious issue. Escalate it to your Royalty paying client to update the ActiveSync apps they build. It will be super awesome, if Microsoft can check if the server fails at forst try forward the request to m.outlook.com to check if the server name is valid. Something like that.
In anyway, we need it get resolved ASAP. iPhone is a huge in the market and its paint to deal with these requests.
Thank you
Ranjodh