Common errors raised by the Stat Email OAuth Test Connect. (4369451)

Common errors raised by the Stat Email OAuth Test Connect.

After configuring the Stat Email Settings OAuth 2.0, different error messages may pop up as a result of performing Test Connect for either IMAP, POP, and SMTP. Some of the most common errors are: 

User is not authenticated.

401 Unauthorized.

Error while generating Auth Code.

Can't reach this page.

 

These errors are caused by incorrect values entered into the Email Settings Details fields.

Resolution:
Since the values required in these fields come from the provider and the App Registration configured, it is important to review the Azure configuration.

It is also good to know and understand what is going on behind the scenes at the Azure App registration and Office 365 Admin Center.
For security reasons, each company has its own Azure subscription and uses the related endpoint authorization (long number series as an access token).
Even if it is not secure and just as an example, we configured and use the "common" endpoints and tokens to cover a broad open scenario of Implicit grants and Hybrid flows.
 

Below are the minimum API Permissions required by Stat Email Settings (Scope).

Note: If you click on each of the permissions, Azure explains in detail each one's functionality.
Some actions may be disabled due to your permissions. To request access, contact the application owner(s) or your administrator. 

In the Office 365 Admin Center, the administrator has created the user with its mailbox.

Selecting the user used in Stat, the administrator gives the user the necessary Licenses (E3 or E5), the Role, and the Email settings (SMTP, POP, and IMAP).

The meaning of Prompt. 

If all these minimum values described above are entered correctly into Stat, you should achieve a successful test connection.