FYI: the instructions for using the azureDisk volume type  to attach manually created  managed disks in Azure for AKS clusters deployed across availability zones does not work.
The az create disk command lacks a --zone parameter.
Even then, the azureDisk volume type (provided by the azure storage CSI driver) does not dynamically create topology.disk.csi.azure.com/zone=eastus-1 style nodeSelector labels so the mount fails with non-matching zone errors.
However, using the dynamic storage provisioning mode does work . The quickstart instructions should probably be updated to reflect that, or else the helm charts updated to allow setting a nodeSelector to match the volume's zone.