Microsoft Outlook for iOS still down and out for many after 'service change'
Many iOS users continue to experience sign-in issues and unexpected sign-outs with Microsoft Outlook more than 24 hours after the problems began, despite Microsoft rolling back a recent service change. The company reported service recovery following the rollback, but its status page still shows 'service degradation' and users report ongoing problems. Only the iOS version of Outlook appears affected, raising concerns about the stability of Microsoft's cloud services. Microsoft has not responded to requests for comment on the discrepancy between its outage resolution claim and user reports.
Full article excerpt tap to expand
SaaS 8 Microsoft Outlook for iOS still down and out for many after 'service change' 8 Sign-in failures, unexpected sign-outs... just another day for users Richard Speed Tue 28 Apr 2026 // 10:32 UTC Users of Microsoft Outlook on iOS are continuing to experience outages more than 24 hours after glitches first surfaced, despite Microsoft's assurances it rolled back the configuration change and restored services. Artemis II astronaut: 'I have two Microsoft Outlooks, and neither one of those are working' READ MORE Users began complaining about access on Monday morning at 0845 UTC, and, just after midday (UTC), Microsoft confirmed: "We've discovered some users may experience intermittent sign‑in failures, including 'too many requests' errors, or unexpected sign‑outs." Affected iOS users were unable to access their email after being locked out due to too many failed password attempts. Some users thought they were victims of hacking, others were just confused and frustrated. The good news was that it appeared only the iOS version was affected. The bad news was that Microsoft couldn't fix it quickly. A few hours after Microsoft confirmed the malfunction came the inevitable: "We've identified a recent service change that is potentially contributing to impact." Cue a rollback to see if the problem went away. Sure enough, a few hours later, Microsoft posted, "System telemetry indicates that the service is recovering following the configuration roll back." <a href="https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2afDLxYyW2Jxtp0t7utwnHgAAAgA&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0" target="_blank"> <img src="https://pubads.g.doubleclick.net/gampad/ad?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2afDLxYyW2Jxtp0t7utwnHgAAAgA&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0" alt=""> </a> So, 10 points to Microsoft's engineers for fixing the problem, but minus 10,000 points for deploying a change that broke things in the first place. In fact, even those 10 points are at risk as users are continuing to complain this morning that things aren't back to normal. <a href="https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44afDLxYyW2Jxtp0t7utwnHgAAAgA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0" target="_blank"> <img src="https://pubads.g.doubleclick.net/gampad/ad?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44afDLxYyW2Jxtp0t7utwnHgAAAgA&t=ct%3Dns%26unitnum%3D426raptor%3Dfalcon%26pos%3Dmid%26test%3D0" alt=""> </a> <a href="https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33afDLxYyW2Jxtp0t7utwnHgAAAgA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0" target="_blank"> <img src="https://pubads.g.doubleclick.net/gampad/ad?co=1&iu=/6978/reg_offprem/saas&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33afDLxYyW2Jxtp0t7utwnHgAAAgA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0" alt="">…
This excerpt is published under fair use for community discussion. Read the full article at The Register.
Discussion
0 commentsMore from The Register
