Unable to deploy Exchange Active accounts to iOS devicesSolved

It does have to do with Microsoft deprecating BasicAuth and moving to Modern Authentication. Effective from Oct 1st 2022, Msft started disabling BasicAuth for specific protocols including EAS. You can however re-enable BasicAuth for EAS from the M365 admin centre until the end of Dec 2022. Checkout this article for details about the steps:

https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-deprecation-in-exchange-online-september/ba-p/3609437

On a side note, Microsoft suggests moving to Outlook for iOS and Android devices when connecting to Exchange Online. You can use Hexnode’s app configuration feature to remotely deploy the necessary configurations for the Outlook app using XML files.

Thanks! Re-enabled the BasicAuth protocol and the EAS seems to be working fine now. I have one more doubt though. Since Microsoft recommends using Oauth 2.0 as part of phasing out their BasicAuth protocol, how is Hexnode adapting to this? Will enabling OAUTH in Hexnode’s Exchange Active policy use Oauth 2.0 or Oauth 1.0 for authenticating?

We need to use EAS for our team since we use the native Mail, Contacts and Calendars apps on our iPhones and iPads. I understand that we could use the Outlook app for each of those but that’s not what we desire primarily.

Hi @wilma. Thank you for reaching out on Hexnode Connect!

For iOS 14 and iPadOS 14 devices, Exchange accounts configured for OAuth will automatically use Microsoft’s OAuth 2.0 authentication service. After updating to the latest iOS version, simply remove and add back the Exchange account. This should automatically switch it to using OAuth 2.0.

Feel free to reach out to us if you’ve any further queries.

Cheers!
Chris Wheeler
Hexnode UEM