HeyHey16K We are planning to cover this in the 4th blog in the series in detail, are the affected Hybrid devices enrolled via Autopilot and do you enable BitLocker during autopilot? There is a scenario where the device is not present in AAD (i.e. has not synced via AD connect yet) but is in AD that the key will only be backed up there when encryption is enabled during Autopilot, if this is the case you should see an error in the BitLocker-API event logs during that timeframe. You can try rotating the keys from the console to recreate the key and add it into AAD.
If this happening for existing HAADJ machines that have a BitLocker policy deployed after they have been deployed then investigating the BitLocker-API event log would be required to understand why the key has not been stored in AAD.