Office 365 Connection Failure/TLS 1.2 Fix

Issue and Diagnostic Signs

Office 365 connected system fails connection test as well as any workflows that output or look-up to it.

Examples of common error messages associated with this issue found in the ProvGIG.log include:

2022-07-19 11:43:16,626 [ajp-nio-8009-exec-7] - [Ofc365][PowerShellJNI][JNI]: *** (1658245392): <<<<< rc = OK:Exception:System.Management.Automation.RuntimeException:One or more errors occurred.

----------

2022-07-18 15:52:27,334 [ajp-nio-8009-exec-5] - [Ofc365][PowerShellJNI][JNI]: *** (1658173663): <<<<< rc = OK:Exception:System.Management.Automation.CommandNotFoundException:The term 'Get-ManagementRoleAssignment' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

----------

2022-07-18 15:52:27,803 [ajp-nio-8009-exec-5] - [Ofc365][PowerShellJNI][JNI]: *** (1658173663): <<<<< rc = OK:Exception:System.Management.Automation.RuntimeException:Cannot bind argument to parameter 'Name' because it is null.

Cause

Due to a security/regulatory push from Microsoft, TLS v1 and 1.1 are being deprecated in favor of TLS 1.2 in Azure AD. This is causing customers' O365 portal to disable support as well, causing the connection issue.

Fix

To restore connectivity the following registry keys must be applied by the customer to their GIG servers and restart the Tomcat service:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
"SystemDefaultTlsVersions"=dword:00000001

Retry test-connection with the connected system and re-run any failed workflows that need to be if the fix is successful.