Missing cypher suites for TLS1.3 in azure function environment

Ib Sandstrøm 0 Reputation points
2024-07-01T18:39:18.2533333+00:00

I am trying to make a timer triggeres function, that must access a website with TLS1.3 as only TLS option. Same website has 3 cipher suites that can be used and no preference:
TLS_AES_128_GCM_SHA256
TLS_AES_256_GCM_SHA384
TLS_CHACHA20_POLY1305_SHA256

When i access the Kudu debug console, and run powershell command Get-TlsCipherSuite, i get the list of awailable cypher suites in the VM that is running my function, and neither of the 3 mentioned above are present.

In Azure Function documentation i can see that for inbound traffic the azure function website can use TLS1.3 and has two of the mentioned cypher suites available:
TLS_AES_256_GCM_SHA384 (TLS 1.3 only)

TLS_AES_128_GCM_SHA256 (TLS 1.3 only)
So why are these cypher suites not available in the list for outbound use?
and will you update the VM for Azure Functions to include these TLS1.3 cypher suites anytime soon?

Thank you for any help offered.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,607 questions
{count} votes