Create a text file with the useragent strings and process each string e.g. through a loop to add or remove items in an allow or block list.

Set-CASMailbox “mailbox” -EwsBlockList @{Add=”Outlook-iOS/*”,”Outlook-Android/*”}

Please help me on it thanks

Hi .. not EWS will be ending, but just Basic Authentication. So you will have to use Modern Authentication to access data like OAuth2 for Microsoft Graph.

Thanks for such a good article.
Just had query on situaltion i am facing right now where i want use EWS for an Outlook365 email account , but came to know the Microsoft will be ending EWS from office365 starting Oct’20.

So what are the alternatives i can think of using EWS from an outlook email account?
is there a way i can create a separate outlook account (with company controlled and domain name) which have access to EWS ??

Based on your diagram, Outlook for Android and iOS will connect to API, then reach on-prem exchange server.
So, would like to ask,
for Exchange 2010 on-prem servers, Outlook for Android and iOS will connect to API, then reach on-prem Exchange server. Am I right?
Also, the API that we been talking about, is it the EWS?
Please correct me if I am wrong.

Hope to get reply from you soon.

Regards,
Zabek

@Mike, not sure why you’re making such a fuss about this in January 2018. Microsoft announced back in September 2017 that you can now use Duo, RSA, or Trusona for native MFA through Azure AD, however it requires an Azure AD P2 license.

This was Duo’s announcement at the time:
https://duo.com/blog/announcing-duos-native-mfa-for-microsofts-azure-active-directory

The only way to know for sure is to ask them.

If I understand correctly, Exchange Online EWS logs are not available to Office 365 customers, even through support tickets?

I’m not trying to debate you, I’m trying to make my questions clear since we seem not to be able to communicate.

Obviously your strength lies in the Microsoft ecosystem. For companies that prefer *not* to require multiple different types of 2fa solutions (a third party SSO/MFA provider such as Ping, Duo, or Okta – all leading vendors in their own right with far more user friendly and flexible MFA solutions as far as my last tests go when compared to Microsoft) this is a huge deal.

This does pit security against usability in a fundamentally flawed way. Either you lose functionality or you are required to teach your user population how and when to choose between 2 different MFA solutions. Or you switch all of your users over to Microsoft’s proprietary solution and accept the fact that Microsoft will never play nicely with third parties.