![]() Maybe your user name or password are wrong, or your account is currently disabled.” “ MailStore was unable to log in to the server.) or DOMAIN\username in the user name field.” If the password is correct, try specifying your UPN Logon (e.g. These issues appear in the status reports as well. User synchronization and archiving profiles are not executed properly.The following issues/error messages can appear: Also affected are MSPs using the MailStore Service Provider Edition who are providing support to customers who are still using Microsoft 365 / Exchange Online via basic authentication. This is because Microsoft has begun disabling this form of authentication once and for all. Possible Error MessagesĪt the moment, Microsoft 365 customers still using basic authentication may be receiving various error messages in MailStore Server. The fix applies to both MailStore Server and the MailStore Service Provider Edition. If you’ve not yet switched to modern authentication and are getting error messages in MailStore, we’ll explain in this article how to fix the problem. So, going forward, you won’t have to miss out on the benefits of independent, third-party archiving. ![]() ![]() Needless to say, our software does remain fully compatible with Microsoft 365 and, in fact, has supported modern authentication since Version 13. If you recall, we discussed this issue with you back in 2020. On 1 October, Microsoft began disabling basic authentication for Microsoft 365 customers once and for all from now on, support will be provided for modern authentication only. Some of our customers who are using Microsoft 365 / Exchange Online are currently receiving different error messages, all of which, however, have the same cause. Authentication failed (EWS)” Microsoft Disables Basic Authentication for Microsoft 365 Customers Definitively ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |