I just tested the command in question with the azure-cli from PIP and it works there. This suggests that it is indeed a packaging bug on our side.