TLS configuration now fixed to block 1.0

We recently announced that all Azure App Service and Azure Functions apps could [update TLS configuration](https://azure.github.io/AppService/2018/04/17/App-Service-and-Functions-hosted-apps-can-now-update-TLS-versions!.html). However, after deployment, an [edge case scenario](https://azure.github.io/AppService/2018/05/02/Breaking-change-for-SNI-SSL-hostnames-on-Azure-App-Service.html) was identified involving SNI-SSL. This scenario led to SSL-analysing tools, such as [SSL Labs](https://www.ssllabs.com/ssltest/analyze.html), showing that TLS 1.0 was still accepted, while higher versions were selected. We have now completed the deployment, which solves the issue for SSI-SSL. Reporting tools should correctly indicate that lower versions of TLS (mainly TLS 1.0) are blocked. For more details on this update and how to apply TLS configuration to your app, see the [team blog](https://azure.github.io/AppService/2018/06/13/TLS-Configuration-now-fixed-to-block-1.0.html). * App Service * Azure functions * Compliance * [ App Service](https://azure.microsoft.com/en-gb/products/app-service/) * [ Azure functions](https://azure.microsoft.com/en-gb/products/functions/)