Azure App Server underlying Windows version and TLS1.3

Jan Vávra 421 Reputation points
2024-09-26T11:32:23.6833333+00:00

We need to make an HttpClient request from an App Service running on Windows to a remote endpoint that, starting from May 2025, will only support TLS 1.3 in the production environment. If the underlying Windows Server version is 2022, everything works fine.

We have an App Service Plan (P1v3) that runs on Windows Server 2022, but we also have another instance of type P1mv3 running on Windows Server 2016, where TLS 1.3 is not supported.

Is there any guideline on how to request or enforce a specific Windows Server version?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
0 comments No comments
{count} votes

Answer accepted by question author
  1. Bryan Trach 17,832 Reputation points Microsoft Employee Moderator
    2024-09-26T23:45:55.8+00:00

    @Jan Vávra You are correct that we are still rolling out 2022 to all instances. You can always try scaling your App Service up to P2v3 as this should force you onto a new instance. Then scale back down to P1v3 and see what type of instance you have been placed on.

    Realistically though, the entire stamp is probably running 2016 so I'm not sure you'll see a difference with scaling to force a new instance.

    In that case, you can try creating new App Service plans until you receive one with a 2022 instance. From there, redeploy your site.

    In regard to timelines as to when 2022 will be on all instances, we do not have anything to share at this time. It is actively being worked on and there should be more to share later this year (check back around the Microsoft Ignite conference).


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.