Hi Ykzhang,
(Wow, didn't expected a so-quick answer on my question, so big thx!)
We already use SCCM internally to install VMware Tools, so this is working as expected since years. Thing is that we will need to slowly move away from SCCM, as per new Microsoft strategy to move their customers from SCCM to Intune cloud-only solution, as fast as possible.
So VMware drivers in MS driver store : big thumbs up :heart:, but the tools will still be missing (no drag/drop between host and guest, auto screen resize,...), so it would be up to the user to install them manually : if a single-MSI file could be available will all your VM tools in it (worst case : passing arguments to the MSI installer to install a subset of the tools should not be that hard...), that would allow your customers to upload the MSI to Intune for automatic VMtools deployment to any machine that is detected as a VM.
This brings the huge benefit for a user, to download himself the Win10 ISO from Microsoft website, directly use it to install the OS inside the VM, enroll the VM to Intune using his domain creds at OOBE phase, and VM drivers and tools will automatically be deployed using MS store/Intune.
If you ask why don't we use SCCM to perform the same : the Intune enrolled machines will most likely no longer be on-prem domain-joined, but only workplace-joined through Azure AD and ADFS.