Require HTTPS for Azure Storage REST requests by enabling Secure transfer required. With this setting enabled, Azure rejects REST requests sent over HTTP. It is enabled by default for new storage accounts.
Check application dependencies
Before changing an existing account, review the applications, scripts and integrations that use it. Plan to replace any HTTP endpoints with HTTPS and test those clients first. Use an account you are authorized to configure and follow your normal change process.
This guide covers Blob, Data Lake, Queue and Table storage REST traffic. If the account also hosts Azure Files, review Microsoft’s separate SMB and NFS encryption guidance before changing settings.
Enable secure transfer
- Sign in to Azure portal and open the storage account.
- Under Settings, select Configuration.
- Set Secure transfer required to Enabled.
- Select Save, then reopen Configuration to confirm the saved value.
Verify the rollout
Run an approved read or write through each affected application’s HTTPS endpoint. Confirm the expected operation succeeds and review client errors. If a client fails, check its endpoint scheme, credentials and network access before changing the protection setting.
For a controlled enforcement test, use a nonproduction account and a disposable request without credentials or sensitive payloads. An HTTP request should be rejected; never send a token or account key over HTTP to test this.
Review Minimum TLS version separately: requiring HTTPS and setting a minimum TLS version are distinct controls.

