Who is this article for?

Users who are having trouble sending emails through 365.

Local Admin permissions are required.

Due to a requirement change in Microsoft 365, older versions of the app may not be able to send emails successfully. This article explains why the issue occurs and how to resolve it.

1. Issue
2. Solution
3. Further reading

1. Issue

When trying to send an email, you may find that the action cannot be completed. This is often reflected in the server Application Event Viewer with the following error:

This affects instances that are using Microsoft 365 as their SMTP provider.

It has been reported to our development team and they have found that a recent Microsoft update on a Microsoft 365 TLS component is causing this issue.

A fix has been put in place in Ideagen Quality Management v7.1.6.0.

2. Solution

You will need to enable strong cryptography on the application server to resolve the issue without an upgrade.

To enable this:

1. Open the Registry Editor.
2. Navigate to: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727].
3. Check that SchUseStrongCrypto and SystemDefaultTlsVersions registry keys exist.
4. Repeat for: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319].

5. If they are missing, right-clicking the screen.
6. Select New.
7. Choose DWORD (32-bit) Value.

8. Right-click each key.
9. Select Rename.
10. Name the entries SchUseStrongCrypto and SystemDefaultTlsVersions respectively.
11. Right-click each key.
12. Select Modify.
13. Change the Value to 1 to enable the key.
14. Select Hexadecimal (Under Base).

If this doesn't resolve the issue, request an upgrade to the latest version.

3. Further reading

• How to enable TLS 1.2 on the site servers and remote site systems | Microsoft Learn