Resolve AzCopy TLS Errors When Copying to Azure Blob Storage
Question details
Resolve an AzCopy SSL/TLS error when copying data from a UNC path to Azure Blob Storage.

- Product
- Microsoft AzCopy and Azure Blob Storage
- Device & OS
- not provided
- Scenario
- A user runs AzCopy in PowerShell to transfer data from a UNC path to Azure Blob Storage.
- Observed behavior
- AzCopy reports that it could not create an SSL/TLS secure channel. Removing the log parameter does not resolve the error.
Have the AzCopy command and full error message available, and check whether the destination uses Microsoft Entra ID or a SAS token for authentication. Remove tokens, credentials, and other sensitive information before sharing diagnostic details.
Check the AzCopy version, authentication, and TLS connection
Use these checks to identify whether the transfer uses a supported AzCopy setup and whether the connection can reach Azure Storage securely.
In PowerShell, run `azcopy --version` and compare the result with Microsoft's current AzCopy documentation. Update to a supported version if necessary.
If using Microsoft Entra ID with AzCopy v10, run `azcopy login` and complete the sign-in prompts. Confirm that the identity has the required Azure Blob data permissions; if using a SAS URL instead, check its permissions and expiration.
In PowerShell, inspect the `azcopy copy` command, including the quoted UNC source path and Azure Blob destination URL. Retry the transfer after correcting any version or authentication issue.
Ask your network administrator to check the connection to the Azure Storage endpoint, including proxy settings, trusted certificates, and TLS support. Do not disable certificate validation to bypass the error.

Request specialized AzCopy troubleshooting
Use the Azure Storage AzCopy GitHub repository if the secure-channel error persists after the initial checks.
Use WPS Office for Documents and Spreadsheets
WPS Office is a free, lightweight alternative for everyday office work, with a familiar interface and support for common Microsoft Office formats to make migration easier. It does not resolve AzCopy or Azure Storage TLS errors.

Frequently Asked Questions
How do I check which version of AzCopy is installed?
Run `azcopy --version` in PowerShell, then compare the result with Microsoft's current AzCopy documentation.
Do I always need to run azcopy login?
No. For AzCopy v10, `azcopy login` is used for supported Microsoft Entra ID sign-in scenarios. A transfer using a valid SAS URL can use the SAS token instead.
Will removing the log parameter fix a TLS error?
Not necessarily. In this case, removing it did not resolve the error. Check the AzCopy version, authentication, and the secure connection to the Azure Storage endpoint.
What should I include in an AzCopy GitHub issue?
Include the AzCopy version, sanitized transfer command, full error, relevant logs, and checks already performed. Remove SAS tokens, keys, credentials, and sensitive paths before posting.




