Protect your organizations against QR code phishing with Defender for Office 365

Updating the relevant M365 Defender docs with how existing EOP/Defender tools interact with QR code-based links would be greatly appreciated. As of now, there's no way to understand how/if things like the Tenant Allow/Block list, transport rules, anti-phishing policies, and more interact (or even if they can interact) with QR code-based links following the functionality rollout described here. Any other relevant technical details appear to still be limited to just this blog post rather than present anywhere in the authoritative service documentation. Generally the behavior around QR code based link analysis and how it fits into the M365 Defender toolset from an administrator's perspective is still something of a black box, leaving a gap in understanding of the protections/controls to one's tenant.