Every mainstream vendor with a US presence does this on their ZDR/MAM AI endpoints. This also includes AWS and Azure. It's explained directly in the AWS ZDR docs, and it falls under the "synchronous" scanning pipeline in Azure with full MAM.
At least with AWS they're clear that this is the only type of proactive scanning they do on their ZDR AI endpoints. With Azure it's actually unclear exactly how much more falls into the synchronous scanning pipeline, though I may be missing some docs.
The way this was explained to me is although there is no legal requirement to do this, vendors are concerned that AI processing constitutes "actual knowledge" of the content unlike a lot of traditional cloud-based workloads, which would expose them to legal liability. Seems like a weird argument in a ZDR context, but anyway, there's also a public optics element too I'm sure.
I'm personally hopeful that as an industry we can move towards E2EE and attested secure enclave pipelines to remove the "actual knowledge" argument. NEAR AI and Tinfoil are the only publicly available providers in this area but I would be excited to hear about more advancements in this area because I personally think that these NCMEC integrated "ZDR" systems are major privacy violations and deceptive marketing.