Working with an Office365 Email Account

Microsoft Office365 mail servers now require TLS version 1.2 or above, which may require additional settings. If you experience authentication issues, try the following:

  • Verify that the authenticated SMTP submission (also known as SMTP AUTH) is enabled on the licensed mailbox that GENESIS is using to connect to Microsoft 365 or Office 365.

    1. Run the following command after you replace <EmailAddress> with the actual email address used by GENESIS:

      Get-CASMailbox -Identity <EmailAddress> | Format-List

      SmtpClientAuthenticationDisabled

    2. 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

  • Disable Multi-Factor Authentication (MFA) on the licensed mailbox that's being used:

    1. In the Microsoft 365 admin center, in the left navigation menu, choose Users > Active users.
    2. On the Active users page, choose Multi-Factor Authentication.
    3. On the multi-factor authentication page, select the user and disable the Multi-Factor Authentication status.

  • Disable the Azure Security Defaults.

    1. Sign in to the Azure portal as a Security administrator, Conditional Access administrator, or Global administrator.
    2. Browse to Azure Active Directory > Properties.
    3. Select Manage security defaults.
    4. Set the Enable security defaults toggle to No, and then click Save.
    Disabling the security defaults represents a security risk, so use it with caution.

  • Exclude the email account from the Conditional Access policy that blocks Legacy Authentication:

    1. Sign in to the Azure portal as a Security administrator, Conditional Access administrator, or Global administrator.
    2. Browse to Azure Active Directory > Security > Conditional Access.
    3. In the policy that blocks Legacy Authentication, exclude the mailbox being used under Users and Groups > Exclude, and then click 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 later. 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. For more details, contact the Support Center.