title: Intermittent SSL/TLS error using Azure SDK in Azure Website
body: <p>I have an ASP.NET MVC website running .NET 4.5 in an Azure Website and I keep getting this error trying to retrieve or upload assets into Azure Blob Storage using the Azure SDK (version 4.3.0).</p>
  
  <blockquote>
    <p>The request was aborted: Could not create SSL/TLS secure channel.  </p>
    
    <p>Microsoft.WindowsAzure.Storage.StorageException: The request was<br>
    aborted: Could not create SSL/TLS secure channel. ---><br>
    System.Net.WebException: The request was aborted: Could not create<br>
    SSL/TLS secure channel.    at System.Net.HttpWebRequest.GetResponse()<br>
    at<br>
    Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync[T]  (RESTCommand`1
    cmd, IRetryPolicy policy, OperationContext operationContext)    ---<br>
    End of inner exception stack trace ---    at<br>
    Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteSync[T](RESTCommand`1<br>
    cmd, IRetryPolicy policy, OperationContext operationContext)    at<br>
    Microsoft.WindowsAzure.Storage.Blob.CloudBlobClient.GetBlobReferenceFromServer(StorageUri<br>
    blobUri, AccessCondition accessCondition, BlobRequestOptions options,<br>
    OperationContext operationContext)    at<br>
    Microsoft.WindowsAzure.Storage.Blob.CloudBlobClient.GetBlobReferenceFromServer(Uri<br>
    blobUri, AccessCondition accessCondition, BlobRequestOptions options,<br>
    OperationContext operationContext)</p>
  </blockquote>
  
  <p>The error doesn't occur every time, but once it starts happening it happens continuously. Only when I scale the Azure website up or down to reset the site does the error stop. It will go a few hours or a few days and then it will come back again.</p>
  
  <p>It seems like this started happening around the time of the Poodle vulnerability and sites shut down their support for SSL3. It seems like from the research I've done that this error could be if the Azure SDK is trying to connect to Azure Blob storage over SSL3. Since it works fine for a time, I wonder if some library in my app is setting the ServicePointManager.SecurityProtocol to SSL3, which is a global setting which Azure is then using from that point on causing the error. Any idea to determine if that is what is happening or how to find that code that is setting the fallback to SSL3?</p>