Azure errors
Note: The command prompts were omitted. These log excerpts appear during operations such as
connect move,connect copy, orconnect listwhen working with Azure Blob Storage endpoints.
Connection errors
Section titled “Connection errors”Dial tcp - i/o timeout
Section titled “Dial tcp - i/o timeout”2024/12/20 14:34:41 INFO License valid to: 2026-04-13 18:06:282024/12/20 14:34:41 INFO Licensed for: Ultimate2024/12/20 14:34:41 INFO Testing connection to az://mycontainer2024/12/20 14:34:41 ERROR Error while testing connection: dial tcp account.blob.core.windows.net:443: i/o timeoutAzure client was unable to establish a TCP connection to the Azure Blob Storage endpoint within the allowed timeout period.
Possible causes:
- Azure Blob Storage endpoint is down or unreachable
- network issues (different subnets, no route, or disconnected network)
- a firewall (on the client, target, or intermediate network) is blocking connections
- timeout is too short
- DNS resolution issues preventing connection to Azure endpoint
Dial tcp - connection refused
Section titled “Dial tcp - connection refused”2024/12/31 09:15:26 INFO License valid to: 2026-04-13 18:06:282024/12/31 09:15:26 INFO Licensed for: Ultimate2024/12/31 09:15:26 INFO Testing connection to az://mycontainer2024/12/31 09:15:26 ERROR Error while testing connection: dial tcp account.blob.core.windows.net:443: connect: connection refusedAzure client was unable to establish a TCP connection to the Azure Blob Storage endpoint as the connection was actively refused.
Possible causes:
- Azure Blob Storage endpoint is not running or is misconfigured
- firewall is blocking the target port (typically 443 for HTTPS)
- proxy configuration issues
- network restrictions preventing access to Azure services
Authentication errors
Section titled “Authentication errors”Invalid Azure URL format - account key authentication requires account:key@container/path
Section titled “Invalid Azure URL format - account key authentication requires account:key@container/path”2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:282024/12/31 08:54:52 INFO Licensed for: Ultimate2024/12/31 08:54:52 ERROR invalid Azure source 'az://account@container/path': invalid Azure URL format - account key authentication requires account:key@container/path formatAzure client encountered a connection string with an invalid format for account key authentication.
Possible causes:
- connection string format is incorrect for account key authentication
Correct format: az://account:key@container/path
Failed to create DefaultAzureCredential
Section titled “Failed to create DefaultAzureCredential”2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:282024/12/31 08:54:52 INFO Licensed for: Ultimate2024/12/31 08:54:52 ERROR failed to create DefaultAzureCredential: <azure error details>Azure client attempted to use DefaultAzureCredential (Application Default Credentials) but failed.
Possible causes:
- Azure SDK is unable to automatically detect credentials
- environment is not properly configured for Azure authentication
- missing Azure CLI configuration
Storage account name required for DefaultAzureCredential
Section titled “Storage account name required for DefaultAzureCredential”2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:282024/12/31 08:54:52 ERROR storage account name required for DefaultAzureCredential. Please set AZURE_STORAGE_ACCOUNT environment variable or use account:key@container formatAzure client attempted to use DefaultAzureCredential but could not determine the storage account name.
Possible causes:
AZURE_STORAGE_ACCOUNTenvironment variable is not set- Azure CLI is not configured
- using DefaultAzureCredential without specifying storage account
Failed to get Azure client - invalid credentials
Section titled “Failed to get Azure client - invalid credentials”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Licensed for: Ultimate2024/12/31 13:15:57 INFO Testing connection to az://mycontainer2024/12/31 13:15:58 ERROR Error while testing connection: <azure error code>Azure client attempted to connect to Azure Blob Storage but was unable to authenticate successfully.
Possible causes:
- account key or connection string is incorrect
- credentials have expired or been revoked
- service principal does not have sufficient permissions for the requested operation
- container or account name is incorrect
- insufficient Azure role assignments
Container/Bucket errors
Section titled “Container/Bucket errors”Error while testing connection - container not found
Section titled “Error while testing connection - container not found”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Testing connection to az://mycontainer2024/12/31 13:15:58 ERROR Error while testing connection: container not foundAzure client attempted to access a container that does not exist in the specified Azure storage account.
Possible causes:
- container name is misspelled or incorrect
- container exists in a different Azure subscription or resource group
- container was recently deleted
- incorrect storage account or subscription
Error while testing connection - access denied
Section titled “Error while testing connection - access denied”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Testing connection to az://mycontainer2024/12/31 13:15:58 ERROR Error while testing connection: access deniedAzure client attempted to access a container but does not have sufficient permissions.
Possible causes:
- service principal or managed identity does not have sufficient permissions
- IAM policy does not grant access to the service principal
- container exists in a different Azure subscription or resource group
- insufficient Azure role assignments
- RBAC (Role-Based Access Control) configuration issues
Error listing files
Section titled “Error listing files”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Listing az://mycontainer/2024/12/31 13:15:58 ERROR Error listing files: <azure error code>Azure client encountered an error while trying to list files in a container.
Possible causes:
- container does not exist
- insufficient permissions to list blobs in the container
- network connectivity issues
- SAS token has expired or is invalid
Object/Blob errors
Section titled “Object/Blob errors”Failed to get Azure object details
Section titled “Failed to get Azure object details”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Getting file from az://mycontainer/file.txt2024/12/31 13:15:58 ERROR failed to get Azure object details: <azure error code>Azure client attempted to get metadata for a blob but failed.
Possible causes:
- blob does not exist
- insufficient permissions to access blob metadata
- SAS token has expired or is invalid
Failed to iterate blobs
Section titled “Failed to iterate blobs”2024/12/31 13:15:57 INFO Listing az://mycontainer/2024/12/31 13:15:58 ERROR failed to list blobs: <azure error code>Azure client encountered an error while iterating through blobs in a container.
Possible causes:
- network connectivity issues during listing
- container does not exist
- insufficient permissions
- SAS token has expired or is invalid
Failed to list blobs page
Section titled “Failed to list blobs page”2024/12/31 13:15:57 INFO Listing az://mycontainer/2024/12/31 13:15:58 ERROR failed to list blobs page: <azure error code>Azure client encountered an error while retrieving a page of blobs.
Possible causes:
- network connectivity issues
- page token expired or is invalid
- service throttling or temporary unavailability
Other errors
Section titled “Other errors”Azure Blob Storage does not support concurrent copy
Section titled “Azure Blob Storage does not support concurrent copy”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Copying az://src-container/file.txt az://dst-container/file.txt2024/12/31 13:15:58 ERROR Azure Blob Storage does not support concurrent copyAzure client attempted a concurrent copy operation which is not supported by Azure Blob Storage.
Possible causes:
- attempting to copy between two Azure endpoints using concurrent mode
- Azure Blob Storage does not support random access writes required for concurrent copying
Solution: The tool will automatically fall back to sequential copying for Azure-to-Azure transfers.
Failed to create destination folder
Section titled “Failed to create destination folder”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Getting files from az://mycontainer/file.txt2024/12/31 13:15:58 ERROR failed to create destination folder: no such file or directoryAzure client attempted to download a file but the local destination directory does not exist.
Possible causes:
- local destination directory does not exist
- path to destination directory does not exist
- insufficient permissions to create the directory
Failed to open source file
Section titled “Failed to open source file”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Sending files to az://mycontainer/2024/12/31 13:15:58 ERROR failed to open source file: no such file or directoryAzure client attempted to upload a file but the local source file does not exist.
Possible causes:
- local source file does not exist
- file path is incorrect
- insufficient permissions to read the file
Failed to get source file info
Section titled “Failed to get source file info”2024/12/31 13:15:57 INFO License valid to: 2026-04-13 18:06:282024/12/31 13:15:57 INFO Getting file from az://mycontainer/file.txt2024/12/31 13:15:58 ERROR Failed to get file info: <azure error code>Azure client attempted to get information about a local source file but failed.
Possible causes:
- file does not exist
- insufficient permissions to read file metadata
- file is locked or in use by another process
Failed to match file regex
Section titled “Failed to match file regex”2024/12/31 13:15:57 INFO Listing az://mycontainer/2024/12/31 13:15:58 ERROR Error while matching file regex: error parsing regexpAzure client encountered an error while trying to match files using a regular expression.
Possible causes:
- regex pattern is invalid or malformed
- regex syntax is not supported (RE2 regex is required)
- special characters in regex are not properly escaped
Error while checking container
Section titled “Error while checking container”2024/12/31 13:15:57 INFO Sending files to az://mycontainer/2024/12/31 13:15:58 ERROR Error while checking container: <azure error code>Azure client encountered an error while checking if a container exists.
Possible causes:
- container does not exist
- insufficient permissions
- network connectivity issues
Error while getting az object details
Section titled “Error while getting az object details”2024/12/31 13:15:57 INFO Getting file from az://mycontainer/file.txt2024/12/31 13:15:58 ERROR Error while getting az object details: <azure error code>Azure client encountered an error while retrieving object details from Azure Blob Storage.
Possible causes:
- blob does not exist
- insufficient permissions to access blob
- SAS token has expired or is invalid
Error while getting az session
Section titled “Error while getting az session”2024/12/31 13:15:57 INFO Getting file from az://mycontainer/file.txt2024/12/31 13:15:58 ERROR Error while getting az session: <azure error code>Azure client encountered an error while establishing a session with Azure Blob Storage.
Possible causes:
- authentication failed
- network connectivity issues
- service throttling or temporary unavailability
Error while closing src file
Section titled “Error while closing src file”2024/12/31 13:15:57 INFO Sending files to az://mycontainer/2024/12/31 13:15:58 ERROR Error while closing src file: <azure error code>Azure client encountered an error while closing the source file after upload.
Possible causes:
- file was deleted or moved during transfer
- insufficient permissions
- file is locked by another process
Error while closing dst file
Section titled “Error while closing dst file”2024/12/31 13:15:57 INFO Getting file from az://mycontainer/file.txt2024/12/31 13:15:58 ERROR Error while closing dst file: <azure error code>Azure client encountered an error while closing the destination file after download.
Possible causes:
- insufficient permissions to write to the file
- disk is full
- file is locked by another process
Failed to create destination file
Section titled “Failed to create destination file”2024/12/31 13:15:57 INFO Getting file from az://mycontainer/file.txt2024/12/31 13:15:58 ERROR failed to create destination file: <azure error code>Azure client attempted to create a local destination file but failed.
Possible causes:
- local destination directory does not exist
- insufficient permissions to create the file
- disk is full
- file already exists and cannot be overwritten
URI format errors
Section titled “URI format errors”Invalid Azure source format
Section titled “Invalid Azure source format”2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:282024/12/31 08:54:52 ERROR invalid Azure source 'az://invalid': <azure error details>Azure client encountered an invalid connection string format for Azure Blob Storage.
Possible causes:
- connection string format is incorrect
- missing required components (account, container, path)
Correct formats:
az://container/path(using DefaultAzureCredential)az://account:key@container/path(using account key)az://sas:https://account.blob.core.windows.net/container?sv=...&sig=.../path(using SAS)
Invalid Azure destination format
Section titled “Invalid Azure destination format”2024/12/31 08:54:52 INFO License valid to: 2026-04-13 18:06:282024/12/31 08:54:52 ERROR invalid Azure destination 'az://invalid': <azure error details>Azure client encountered an invalid connection string format for Azure Blob Storage.
Possible causes:
- connection string format is incorrect
- missing required components (account, container, path)
Correct formats:
az://container/path(using DefaultAzureCredential)az://account:key@container/path(using account key)az://sas:https://account.blob.core.windows.net/container?sv=...&sig=.../path(using SAS)