Does a deleted disk is considered as a retired DBD? If so, that answers the question
no, it doesn't considered a retired DBD. Azure disks are virtual disks (literally, files) which may span one or multiple hardware disks. These disks may or may not be shared with other customers' data. When virtual disk is deleted, the physical disk is not necessary disposed, so your use case doesn't fall to retired DBD destruction policy. I think, this article gives a bit more hints: https://learn.microsoft.com/en-us/compliance/assurance/assurance-data-bearing-device-destruction, specifically:
Microsoft uses three categories of data sanitization for DBDs and assets containing data:
Clear: relates to the logical techniques that help to sanitize data in all user-addressable storage locations for protection against simple non-invasive data recovery techniques. These are techniques typically applied through the standard read and write commands to the storage device, such as by rewriting with a new value or using a menu option to reset the device to the factory state (where rewriting is not supported).
I think, this is your use case. This means that once you delete the VM disk is deleted, a "Clear" process is executed to wipe the data space previously allocated to your VM disk only. Then, cleared space can be allocated to very different customer. The link to NIST document (see response from @Bhanu Ejjagiri ) describe "Clear" process in a bit more details.
Physical disc destruction/retirement is a separate process which relies on hardware metrics such as read/write cycles, MTTF (mean time to failure) and/or other internal policies which are not related to VM disk delete processes.