Configure minimum required version of Transport Layer Security (TLS) for a storage account
Communication between a client application and an Azure Storage account is encrypted using Transport Layer Security (TLS). TLS is a standard cryptographic protocol that ensures privacy and data integrity between clients and services over the Internet. For more information about TLS, see Transport Layer Security.
Azure Storage currently supports three versions of the TLS protocol: 1.0, 1.1, and 1.2. TLS 1.2 is the most secure version of TLS. Azure Storage uses TLS 1.2 on public HTTPs endpoints, but TLS 1.0 and TLS 1.1 are still supported for backward compatibility.
By default, Azure Storage accounts permit clients to send and receive data with the oldest version of TLS, TLS 1.0, and above. To enforce stricter security measures, you can configure your storage account to require that clients send and receive data with a newer version of TLS. If a storage account requires a minimum version of TLS, then any requests made with an earlier version will fail.
This article describes how to configure a storage account to require that clients send requests with a minimum version of TLS. For information about how to specify a particular version of TLS when sending a request from a client application, see Configure Transport Layer Security (TLS) for a client application.
Detect the TLS version used by client applications
When you enforce a minimum TLS version for your storage account, you risk rejecting requests from clients that are sending data with an earlier version of TLS. To understand how configuring the minimum TLS version may affect client applications, Microsoft recommends that you enable logging for your Azure Storage account and analyze the logs after an interval of time to determine what versions of TLS client applications are using.
To log requests to your Azure Storage account and determine the TLS version used by the client, you can use Azure Storage logging in Azure Monitor (preview). For more information, see Monitor Azure Storage.
Azure Storage logging in Azure Monitor supports using log queries to analyze log data. To query logs, you can use an Azure Log Analytics workspace. To learn more about log queries, see Tutorial: Get started with Log Analytics queries.
To log Azure Storage data with Azure Monitor and analyze it with Azure Log Analytics, you must first create a diagnostic setting that indicates what types of requests and for which storage services you want to log data. To create a diagnostic setting in the Azure portal, follow these steps:
Enroll in the Azure Storage logging in Azure Monitor preview.
Create a new Log Analytics workspace in the subscription that contains your Azure Storage account. After you configure logging for your storage account, the logs will be available in the Log Analytics workspace. For more information, see Create a Log Analytics workspace in the Azure portal.
Navigate to your storage account in the Azure portal.
In the Monitoring section, select Diagnostic settings (preview).
Select the Azure Storage service for which you want to log requests. For example, choose Blob to log requests to Blob storage.
Select Add diagnostic setting.
Provide a name for the diagnostic setting.
Under Category details, in the log section, choose which types of requests to log. You can log read, write, and delete requests. For example, choosing StorageRead and StorageWrite will log read and write requests to the selected service.
Under Destination details, select Send to Log Analytics. Select your subscription and the Log Analytics workspace you created earlier, as shown in the following image.
After you create the diagnostic setting, requests to the storage account are subsequently logged according to that setting. For more information, see Create diagnostic setting to collect resource logs and metrics in Azure.
For a reference of fields available in Azure Storage logs in Azure Monitor, see Resource logs (preview).
Query logged requests by TLS version
Azure Storage logs in Azure Monitor include the TLS version used to send a request to a storage account. Use the TlsVersion property to check the TLS version of a logged request.
To retrieve logs for the last 7 days and determine how many requests were made against Blob storage with each version of TLS, open your Log Analytics workspace. Next, paste the following query into a new log query and run it. Remember to replace the placeholder values in brackets with your own values:
StorageBlobLogs | where TimeGenerated > ago(7d) and AccountName == "<account-name>" | summarize count() by TlsVersion
The results show the count of the number of requests made with each version of TLS:
Query logged requests by caller IP address and user agent header
Azure Storage logs in Azure Monitor also include the caller IP address and user agent header to help you to evaluate which client applications accessed the storage account. You can analyze these values to decide whether client applications must be updated to use a newer version of TLS, or whether it's acceptable to fail a client's request if it is not sent with the minimum TLS version.
To retrieve logs for the last 7 days and determine which clients made requests with a version of TLS prior to TLS 1.2, paste the following query into a new log query and run it. Remember to replace the placeholder values in brackets with your own values:
StorageBlobLogs | where TimeGenerated > ago(7d) and AccountName == "<account-name>" and TlsVersion != "TLS 1.2" | project TlsVersion, CallerIpAddress, UserAgentHeader
Configure the minimum TLS version for an account
To configure the minimum TLS version for a storage account, use the Azure portal or Azure CLI to set the minimumTlsVersion version for the account. This property is available for all storage accounts that are created with the Azure Resource Manager deployment model. For more information, see Storage account overview.
To configure the minimum TLS version for a storage account with the Azure portal, follow these steps:
Navigate to your storage account in the Azure portal.
Select the Configuration setting.
Under Minimum TLS version, use the drop-down to select the minimum version of TLS required to access data in this storage account, as shown in the following image.
After you update the minimum TLS version for the storage account, it may take up to 30 seconds before the change is fully propagated.
Check the minimum required TLS version for an account
To determine the minimum required TLS version that is configured for a storage account, check the Azure Resource Manager minimumTlsVersion property. To check this property for a large number storage accounts at once, use the Azure Resource Graph Explorer.
The minimumTlsVersion property is not set by default and does not return a value until you explicitly set it. The storage account defaults to permitting requests sent with TLS version 1.0 or greater if the property value is null.
Check the minimum required TLS version for a single storage account
To check the minimum required TLS version for a single storage account using Azure CLI, call the az resource show command and query for the minimumTlsVersion property:
az resource show \ --name <storage-account> \ --resource-group <resource-group> \ --resource-type Microsoft.Storage/storageAccounts \ --query properties.minimumTlsVersion \ --output tsv
Check the minimum required TLS version for a set of storage accounts
To check the minimum required TLS version across a set of storage accounts with optimal performance, you can use the Azure Resource Graph Explorer in the Azure portal. To learn more about using the Resource Graph Explorer, see Quickstart: Run your first Resource Graph query using Azure Resource Graph Explorer.
Running the following query in the Resource Graph Explorer returns a list of storage accounts and displays the minimum TLS version for each account:
resources | where type =~ 'Microsoft.Storage/storageAccounts' | extend minimumTlsVersion = parse_json(properties).minimumTlsVersion | project subscriptionId, resourceGroup, name, minimumTlsVersion
Test the minimum TLS version from a client
To test that the minimum required TLS version for a storage account forbids calls made with an earlier version, you can configure a client to use an earlier version of TLS. For more information about configuring a client to use a specific version of TLS, see Configure Transport Layer Security (TLS) for a client application.
When a client accesses a storage account using a TLS version that does not meet the minimum TLS version configured for the account, Azure Storage returns error code 400 error (Bad Request) and a message indicating that the TLS version that was used is not permitted for making requests against this storage account.