OAuth support for O365 with Application permissions (C# .NET)

I would like to access an Office 365 mailbox using OAuth Application permissions.

Error Details:

ae_5_1_0002 no login failed
Picture1.png (101.5 KB)

Aspose.email Version:

Picture2.png (26.5 KB)

Sample Code:

if (Utility.AreStringsEqual(protocol, “Imap”))

            ImapClient = new ImapClient(_host, _port, _userName, _password);
            //ImapClient.SecurityOptions = SecurityOptions.SSLImplicit;
            //ImapClient.SecurityOptions = SecurityOptions.Auto;
            ImapClient.SecurityOptions = SecurityOptions.SSLAuto;

            ImapMessageInfoCollection list = ImapClient.ListMessages();



Please read the following detail to login into Office 365 account using Modern Authentication. Hope this helps you.

How To Enable or disable modern authentication

To use modern authentication, make sure that it is enabled. Modern authentication is enabled by default in Exchange Online. For tenants created before August 1, 2017, modern authentication is turned off by default.
In the Microsoft 365 admin center at https://admin.microsoft.com, go Settings > Org Settings > Modern Authentication. In the Modern authentication flyout that appears, you can identify the protocols that no longer require Basic authentication.
For new Office 365 tenants in Azure, Basic Authentication is disabled by default for all applications. In this case, the text will be displayed in this section.

Your organization has security defaults enabled, which means modern authentication to Exchange Online is required, and basic authentication connections are blocked. You must turn off security defaults in the Azure portal before you can change any settings here.

You can enable Basic Auth support for tenant from the Azure portal (Azure Active Directory → Properties → Manage Security defaults → Enable Security defaults = No ).
For more information, see the documentation on Enable or disable modern authentication for Outlook in Exchange Online | Microsoft Learn

How To use modern authentication with EwsClient

To use modern authentication with EwsClient the following is required:

  1. App registration with Azure Active Directory.
  2. Adding code to get an authentication token from a token server.
  3. Using the token to authenticate.

Note: There are two types of permissions that can be used to access EWS. Choose a specific type of permission, depending on the app you are creating:

  • Delegated permissions are used by apps that have a signed-in user present. For these apps, either the user or an administrator consents to the permissions that the app requests. In other words, when you connect to the service, a dialog window will appear to enter username and password. App can never have more privileges than the signed-in user.
  • Application permissions are used by apps that run without a signed-in user present, for example, apps that run as background services or daemons. Only an administrator can consent to application permissions.

Refer to Microsoft documentation for more information: Authenticate an EWS application by using OAuth | Microsoft Learn

App registration with Azure Active Directory

The registration procedure depends on the type of permission selected. To register your app, refer to the Microsoft documentation:

You can download full code example to use modern authentication with IMAP and SMTP clients from here: EWSModernAuthenticationImapSmtp.zip (3.9 KB)

You can also download full code examples to use different permission types of modern authentication with EWS client from here:
With Application authentication - EWSModernAuthenticationApp.zip (3.4 KB)
With Delegated authentication - EWSModernAuthenticationDelegated.zip (3.6 KB)

A post was split to a new topic: OAuth2 support for O365 with Application permissions

Thank you for your reply. Please find the attached file bellow for error details :

image.png (162.8 KB)


EWSModernAuthenticationApp.zip (4.4 MB)


We have logged this problem in our issue tracking system as EMAILNET-40727. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.


It seems that the issue you are facing is caused by incorrect App settings. On our servers, everything works without errors.

Unfortunately, we cannot investigate the cause without having access to the App registrations on Azure Active Directory admin center. We suggest that please check the App settings.