TLS version issue is being raised while connecting to AzureAD using the Azure Functions

Question

I have deployed an Azure function app, While using the command Connect-AzureAD in one of the function is throwing the error "You are using TLS version 1.0, 1.1 and/or 3DES cipher which are deprecated to improve the security posture of Azure AD"

• Though the function App
• has minimum tls version of 1.2
• the .NET framework is 4.8.x

the other services like storage account etc. associated with the function app were using minimum TLS version of 1.2.

Function App details

Function runtime: Powershell

runtime version: 3.8.2.0

Any help regarding this issue would be helpful

Answer 1

@MayankBargali-MSFT - If I have to make changes suggested above, I see following issues -

1. Code will be hard wired to use TLSv12, which is not the best solution. I assume you are suggesting this as temporary measure?
2. Via Kudu interface I could figure out that Windows Server 2016 is being used as platform OS here, also .NET framework version is 4.8, I looked up all the corresponding Microsoft documentation for both these platforms and as per documentation both of them use TLS v12 or higher as default protocol. So technically I should have never encountered this problem. Could you please confirm that this is result of some provisioning/infrastructure defect on Azure side? If yes, please share the corresponding ticket so that I can track it.
3. Now coming back to your suggestion, I'll have to push a patch in production. But before we go that route, IMO this deprecation should be be rolled back till underlying issue is fixed from Azure side. A lot of bandwidth goes in pushing patches to production, please confirm if that can be done.
4. Please note that, even if I have to convince internally for the patch, the response to these questions (#1, #2) would help me. So requesting you to shade some light on same.