You can configure it with the sslversion option. This will include TLS 1.2 on basically any recent system. Net Framework 4.6.1 not defaulting to TLS 1. Yes, rest-client should support any TLS version that the Ruby OpenSSL library supports. On the server, how do we make sure that the. Make sure that applications and PowerShell (that use Microsoft Graph) and Azure AD PowerShell scripts are hosted and run on a platform that supports TLS 1.2. NET Framework installation to support TLS 1.2. This was not required in our case: ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 Everything has been working fine until recently, when they disabled TLS 1.0 on all the sandbox (test) instances. Enable TLS 1.2 for applications and services that communicate with Azure AD. If a connection that uses SslProtocols.None to pick a suitable TLS version fails, the client will retry with TLSv1.2 enabled explicitly. But calling REST API might have a different behavior although we have not noticed that. In general, The WCF framework automatically chooses the highest protocol available up to TLS 1.2 unless you explicitly configure a protocol version. Make sure to check all these registry settingsĬomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v9Ĭomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002Ĭomputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS1.2\Server