unexpected startup failure with Mesh - Q4B + Intune2

Question

We are able to log into Mesh using a conditional access bypass group for select users. This is not a scalable solution because we need to properly manage conditional access. So we got 2x Meta Q4B licenses, and Intune Plan 2, and were able to mark devices as compliant in Azure. However on both Quest 2 and Quest 3 headsets we repeatedly get "unexpected startup failure" messages with Mesh. Is anyone else out there using Meta Q4B and/or Intune Plan 2 to manage Quest headsets? Has anyone else had issues with Mesh recently? The app has 72 ratings, and 2 out of 5 stars, and the first several reviews complained about login errors and issues. When we go back to our conditional bypass group, Mesh works, but otherwise (with Q4B / Intune 2) it crashes. We need to manage these headsets.

michelle_maislen · Answer

Greetings Wes_Tomer&nbsp;- Mesh is aware of this issue and is in the process of building support for Conditional Access which we expect to release by the end of this calendar year (2024). We recognize that this blocks the majority of Mesh enterprise usage on Quest devices and creating a CA bypass group is the only current workaround. Thanks for your patience.&nbsp;

Forum Discussion

unexpected startup failure with Mesh - Q4B + Intune2