Container/Path created by copy when 0 files transferred

[SimonTiz]

v10.20.0
Windows (10)

in Powershell
$AzCopyExe = "path-to-my/AzCopy.10.20.0.exe"
$SAS = '....' #good SAS
$target = "https://mystorageAcc.blob.core.windows.net/dodgy/Not.Exist"
n.b. target container ('dodgy') does NOT exist,, storage account is (Date Lake Storage Gen2 )

. "$AzCopyExe" cp "$target$SAS" "$($target)$SAS"

return is that 0 transfers occurred (well source/target doesn't exist)
HOWEVER it does create said 'dodgy' container, (though not the file), even though surely it should be doing nothing !

Late Note: the container name must be all lower case for this to occur ?!!!

[SimonTiz]

P.S. Possible RFC as you can also (intentionally) create a container using AzCopy by 'make' action, I feel you ought to be able to effectively undo any action you can do; but as far as I can tell no AzCopy facility is provided to remove a container. Am presuming this is intentional but seems lop-sided.

[nakulkar-msft]

azcopy should create a container only if the source is valid and we have atleast one file to transefer