note: below are azure cli commands

az ad user list

az ad user create --display-name
                  --password
                  --user-principal-name
                  [--force-change-password-next-sign-in {false, true}]
                  [--immutable-id]
                  [--mail-nickname]

First, list all storage accounts. Thereof, we are interested in the scope, namely what comes after "id" elements.
az storage account list | grep id
you'll get something as:

/subscriptions/<subscription>/resourceGroups/<resource-group>/providers/Microsoft.Storage/storageAccounts/<storage-account>/blobServices/default/containers/<container>
Having identified the scope, and knowing your container name you can now:

az role assignment create \ --role "Owner" \ --assignee <your-id> \ --scope "/subscriptions/<subscription>/resourceGroups/<resource-group>/providers/Microsoft.Storage/storageAccounts/<storage-account>/blobServices/default/containers/<container>"

After having assigned the roles for access appropriately, you need to install azcopy on the machine where you'll copy from.
azcopy login --tenant-id=<AAD-tenant-id>

az copy "[path-to-file]" "https://[account].blob.core.windows.net/[container]/[path/to/container-directory]"

az copy "[path-to-file]" "https://[account].blob.core.windows.net/[container]/[path/to/container-directory]" --recursive=true

After creating your container registry, you can spawn an admin user and (2) passwords. This practice is not avised unless temporarily for pushing your image. You should deactivate your admin credentials in the end. Alternatively, you can assign pull/push roles to an azure server principal.

read -sp "Continer Registry Admin Credentials: " SP_PASSWD && echo && docker login <registryname>.azurecr.io --username <admin-usr> --password $SP_PASSWD
docer images
docker tag <your-image-id> <registryname>.azurecr.io/<tag>
docker push <registryname>.azurecr.io/<tag>```