Scheduler support for TLS 1.2
Hi,
Our technical team has raised an issue and confirmed with MS that Scheduler currently only supports TLS 1.0.
Please add support for TLS 1.2. We are trying to use scheduler to initiate Azure Functions running in an ASE in a private VNET. We had planned to have an API receive these triggers from scheduler. We are unwilling to enable TLS 1.0 support on our Azure Application Gateway (AAG) so Scheduler is unable to communicate with the API we planned to create.
Thanks, Matt
Matt Dawson
shared this idea
5 comments
-
Scott Waye
commented
Seems like this is working now
-
Andrew Turner
commented
As per: https://twitter.com/AzureSupport/status/920850309697753090
This is critical for us, appreciate Scheduler supporting TLS1.2 which we need to meet PCI compliance.
-
Anonymous
commented
This is a requirement for us to proceed with our PCI compliance requirements and SSL security enhancements.
-
Scott Waye
commented
This problem is now a big deal for us because new customers will not accept Azure without an "A" pass on the ciphers from nmap/WebInspect
-
Anonymous
commented
We have an industry mandate to not use TLS 1.0 or 1.1, but we want to use Azure Scheduler and would appreciate Microsoft adding support for TLS 1.2 into Azure Scheduler.