Hi guys, anyone have problems connecting to an email external source based on office365?

This is not related to M-Files. Microsoft has implemented new restrictions on their mail platform. You must switch from using IMAP to Microsoft Exchange Online. This requires information on your Tenant ID, Client ID and Client Secret. Those are not always easy to get hold on if you are not also Admin on the Microsoft account.

Microsoft did sent out warnings back in August, I believe. It could have escaped your attention...

The configuration instructions for using Microsoft Exchange Online as the service type can be found in the user guide: https://www.m-files.com/user-guide/latest/eng/connecting_to_a_new_mail_source.html This support was added in M-Files April ’21 Update (21.4.10123.9).

The configuration instructions for using Microsoft Exchange Online as the service type can be found in the user guide: https://www.m-files.com/user-guide/latest/eng/connecting_to_a_new_mail_source.html This support was added in M-Files April ’21 Update (21.4.10123.9).

Jonas thank you very much for your information, we just change to Microsoft Exchange and apply the configuration as is discribed on the configurations instrutions, problem is after we apply the configurations in M-Files Admin the console just crash!! 

Any sugestion ?

Thnak you.

One thing you could check is to make sure the server is using TLS 1.2 when trying to connect to Microsoft services, this support article has more information: Azure AD TLS 1.0 and 1.1 Error It shouldn't crash M-Files Admin but just to rule that one out as a possible cause.

If that doesn't help, I recommend raising this with our technical support. You may find additional information in the Windows application log on the server: if there are any error messages related to the crash, please include them in your message to the support team.

Exactly the same for me.

When i try to apply the configuration each time the console crash

We had this issue too where mmc.exe stopped working and M-Files Admin then closes. This was occurring when trying to set up the configuration on the Windows Server 2016 machine where M-Files was installed.
The fix was to set up the connection from a user's M-Files Admin. The user being a system admin with full control of vault. 
This was documented here: M-Files Admin crashes on Windows Server 2016 when adding a new email source (WORKAROUND EXISTS) (site.com)

For our user we did then need to enable TLS 1.2 with the powershell script M-Files provided before it finally worked. For this script I think you can follow Joonas's link ^

Hope this helps! Rainer Thomas João Rodrigues

Thank you Dillon !

Thank you we will try it, that way,
But first we will try the new release of M-Files from 19-oct that says it is fix it.
Cheers.