Another quick note after further testing, if you try to use this to deploy things like the Visual C++ Redistributable for Visual Studio 2015, the version detection does not appear to work properly. We are attempting to use the registry key validation per the MSDN article best practices for installer deployment, but the version recorded in the registry isn't evaluated properly by the Intune client because the vc++ registry key stores the vesion value with the "v" character at the beginning. I think the Intune client should be able to handle this version notation properly as it is a common way of recording versions.
See logs below:
<![LOG[[Win32App] Got reg value path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x64, name: Version, value: v14.15.26706.00]LOG]!><time="15:17:17.9269191" date="10-19-2018" component="IntuneManagementExtension" context="" type="1" thread="5" file="">
<![LOG[[Win32App] Failed to parse Version with actualValue: v14.15.26706.00, DetectionValue: 14.15.26706.00]LOG]!><time="15:17:17.9274783" date="10-19-2018" component="IntuneManagementExtension" context="" type="3" thread="5" file="">