Storage is retiring support for TLS 1.0 and 1.1 starting Feb 3, 2026. IF i dont migrate then what will happen, my client will not able to read/write operation in azure st

Mohsin Khan 85 Reputation points
2026-01-14T21:02:41.4933333+00:00

I have received a notification from MS regarding the upgrade of TLS 1.0 or TLS 1.1 to TLS 1.2. I want to know if i dont do before 3rd Feb 2026 then what will happen or MS will auto upgrade.

If yes, then can i switch it back to TLS 1.1 or TLS 1.0?

Quick help is appericated

Azure Storage
Azure Storage
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
0 comments No comments
{count} votes

Answer accepted by question author
  1. Andreas Baumgarten 130.7K Reputation points MVP Volunteer Moderator
    2026-01-14T21:13:25.4733333+00:00

    Hi @Mohsin Khan ,

    if you don't change the TLS to version 1.2 for the Storage Account the clients will not be able to send or receive data to or from the Storage Account.

    You have to change the TLS version to 1.2 yourself. MS won't do this for you.

    After 3rd of February 2026 it will not be possible to switch back to TLS 1.1 or 1.0.

    Configure the minimum TLS version for a storage account

    Before you are changing the TLS settings for the Storage Account you can check which TLS version the clients are currently using: Detect the TLS version used by client applications


    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards

    Andreas Baumgarten


2 additional answers

Sort by: Most helpful
  1. Thanmayi Godithi 6,245 Reputation points Microsoft External Staff Moderator
    2026-01-14T21:47:34.81+00:00

    Hi @Mohsin Khan,

    Thank you for your follow-up question.

    Unfortunately, it will not be possible to retain or extend support for TLS 1.0 or TLS 1.1 beyond February 3, 2026, even by raising a Microsoft support case.

    The retirement of TLS 1.0 and TLS 1.1 for Azure Storage is a platform-wide, security-mandated change, and no exemptions, extensions, or temporary grace periods are available. Once the enforcement date is reached, Azure Storage will only accept connections using TLS 1.2 or later.

    This means:

    Microsoft Support cannot enable TLS 1.0/1.1 for individual subscriptions or storage accounts.

    There is no option to retain older TLS versions for an additional month or two.

    Any client still using TLS 1.0 or TLS 1.1 will fail to connect after the deadline.

    To avoid service disruption, we strongly recommend updating all client applications and services to use TLS 1.2 or higher before February 3, 2026. You may also choose to enforce TLS 1.2 on your storage account now to identify and remediate any incompatible clients in advance.

    Please let us know if you need any further assistance.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments No comments

  2. Marcin Policht 77,665 Reputation points MVP Volunteer Moderator
    2026-01-14T21:13:57.5633333+00:00

    In short, after February 3, 2026, Azure Storage will no longer accept connections that try to negotiate TLS 1.0 or TLS 1.1. Nothing breaks in the Azure service itself, but any application, service, SDK, script or integration that still uses TLS 1.0 or 1.1 are bound to fail. Those connections will not be able to read data, write data, upload, download or authenticate. From your perspective it will look like your storage account is unavailable, even though it is running normally.

    There is no "rollback" option. Once the backend stops accepting TLS 1.0 and TLS 1.1, you cannot switch your account or your client back to older TLS versions.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin


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.