Microsoft Office365 mail servers now require TLS version 1.2 or above which may require additional settings. If you experience authentication issues, there are a few things you should check:
1. Verify that authenticated SMTP submission (also known as SMTP AUTH) is enabled on the licensed mailbox that the ICONICS application is using to connect to Microsoft 365 or Office 365. You can use Exchange Online PowerShell:
Run the following command after you replace <EmailAddress> with the actual email address used by ICONICS products:
Get-CASMailbox -Identity <EmailAddress> | Format-List
SmtpClientAuthenticationDisabled
If the value is True, replace <EmailAddress> with your email address again and run the following command to enable it:
Set-CASMailbox -Identity <EmailAddress> -SmtpClientAuthenticationDisabled $false
2. Disable Multi-Factor Authentication (MFA) on the licensed mailbox that's being used:
In the Microsoft 365 admin center, in the left navigation menu, choose Users > Active users.
On the Active users page, choose Multi-Factor Authentication.
On the multi-factor authentication page, select the user and disable the Multi-Factor Authentication status.
3. Disable the Azure Security Defaults by toggling the Enable Security Defaults to No:
Note: Disabling the security defaults represents a security risk so use it with caution.
Sign in to the Azure portal as a Security administrator, Conditional Access administrator, or Global administrator.
Browse to Azure Active Directory > Properties.
Select Manage security defaults.
Set the Enable security defaults toggle to No.
Select Save.
4. Exclude the email account from the Conditional Access policy that blocks Legacy Authentication:
Sign in to the Azure portal as a Security administrator, Conditional Access administrator, or Global administrator.
Browse to Azure Active Directory > Security > Conditional Access.
In the policy that blocks Legacy Authentication, exclude the mailbox being used under Users and Groups > Exclude.
Select Save.
Applications that rely on TLS 1.2 strong encryption may also experience connectivity failures after a Windows upgrade. This could be caused by an old version of .NETFramework (you need at least 4.8. or above). Either upgrade .NETFramework to the latest version, or find possible workarounds here.
If these steps do not help, you will need some changes in the registry settings. In that case please contact our technical support for more details.