Forum Discussion

EmyLoanzon's avatar
EmyLoanzon
Iron Contributor
Sep 20, 2017
Solved

iOS 11 issue?

Microsoft made an urgent announcement in the Office 365 admin web to not install iOS 11 because it will disrupt sending and receiving emails if you are accessing Exchange email from the iOS 11 mail app, Outlook.com, O365, and Exchange 2016.

https://support.microsoft.com/en-us/help/4043473/you-can-t-send-or-reply-from-outlook-com-office-365-or-exchange-2016-i

Some of our users already installed iOS 11 and they are still able to send and receive emails.

Are there specific Outlook email features that would not work with iOS 11?

When will this restriction be rescinded?

Thanks!

 

 

  • Yes, this is confirmed in the Apple support article I linked to previously, which has been updated to say this been fixed in the iOS 11.0.1 update, which is now available. 

10 Replies

  • Cian Allner's avatar
    Cian Allner
    Silver Contributor

    Outlook for iOS is fine and not affected by these compatibility issues as I understand it.  This is only when using the native email app with an Office 365 mailbox, as well as the other scenarios you have mentioned.  This is where you might see an error message that says "Cannot Send Mail. The message was rejected by the server".

     

    A fix is being worked on asap, as is also confirmed here - https://support.apple.com/en-us/HT208136 - "Apple is working closely with Microsoft to resolve the issue and will release a fix soon in an upcoming software update".

    • EmyLoanzon's avatar
      EmyLoanzon
      Iron Contributor

      The employees who upgraded to iOS 11 are using the Apple native mail app connecting to their Office 365 Exchange Online accounts. They  are able to send and receive emails.

       

      Very confusing announcement.

      • Cian Allner's avatar
        Cian Allner
        Silver Contributor

        That's interesting.  Now you mention it, I have seen other reports that not everyone is affected by this, so your mileage may vary.  With Apple and Microsoft confirming the issue, it's must be a thing but we will have to wait for additional guidance before we have any more particulars.  Confusing indeed!

         

Resources